!!! info "What is this?"
    The Social Subsystem describes how people in a Smartup organize, collaborate, and make decisions together. It replaces hierarchical management and fragmented teams with a decentralized system of shared ownership, trust-based roles, and mutual accountability. This subsystem creates the social architecture needed to build technology in a way that's fair, resilient, and aligned with the public good.

??? tip "Just give me the abstract"
    In this new design for a the Social Subsystem  redesigns how people work together by introducing democratic governance, peer support structures, and fluid identity protocols. Instead of traditional management, Smartups rely on a balance between autonomy, discipline, and mission-alignment — enforced not by authority, but by structure. Contributors operate in role-based groups, make collective decisions using the ADM Triangle, and support each other through systems like the Buddy Program. This model aims to unlock large-scale collaboration by treating contributors as citizens — not employees — in a shared mission to build public-interest technology.


## :material-cube-outline: The Architecture of a Smartup

**Definition:**  
A Smartup creates trustworthy digital tools that help people—and the communities they form—become more resilient, resourceful, and effective in advancing the SDGs.

---

**At its core, every Smartup is built like a rocket: a solid foundation, three structural pillars, and a sharp point of execution.**

![Centered image](../assets/diagrams/smartupinstitute.png){ style="display: block; margin: 0 auto; width: 200px;" }

---

### The Foundation (Our Fuel)

- **Science**  
  Every tool we create is grounded in facts, evidence, and tested knowledge. The problems we tackle are science-proven, and solutions must stand up to real-world scrutiny.  
- **Democracy**  
  Our process and decisions are open and participatory. Everyone has a voice and a vote—no gated hierarchies, no closed rooms.  
- **Collective IQ**  
  We are smarter together. All skills and ideas are pooled so we solve more, faster, and with better results than any one person or small group could alone.

---

### The Three Pillars (Our Structure)

- **Collective Ownership**  
  Everyone who joins and contributes is an equal owner. There are no founders, investors, or external shareholders—just people “in it” together.  
  --8<-- "_snippets/smartup-ownership-meaning.md"  
  --8<-- "_snippets/the-book-of-owners.md"  

- **Collective Craftsmanship**  
  All work and effort are shared—teams build, improve, and sustain everything the Smartup delivers. Value is earned by doing, not by owning capital.  

- **Collective Governance**  
  Decision-making and oversight are for everyone. Every contributor holds both rights and responsibilities for what the Smartup does and how it does it.

---

### Our Modus Operandi

- **Military Execution**  
  While we are democratic in nature, we are military in execution. When the General Forum sets a target, the Workplace hits it with precision. Clear chains of command, proven processes like the buddy system, and professional discipline ensure we don't just talk about change—we deliver it.

---

!!! info "Why a rocket?"
    A Smartup is a vehicle for change. The foundation powers us, the pillars keep us stable, and military execution cuts through obstacles. Together, these elements create an organization that can actually reach its destination: a world where digital tools serve collective human needs.

---

## :material-tree: The 4 Phases of Creation - The Habitat of a Smartup

!!! info "What is this?"
    Every Smartup grows through four clear, community-driven phases. This rhythm—from first idea to real-world launch—ensures that only validated, sustainable, and well-governed solutions reach the market. At every step, the decision to move forward belongs to the entire Smartup community.

<div class="grid cards" markdown>

- :material-stamper:{ .lg .middle } **Phase 1: Validation**  
    **The Question:** *"Does the world need this?"*  
    Entrepreneurs and early adopters rally a vibrant community around a solution, showing real traction in people and resources.  

    **Thresholds to advance:**  
    - [ ] Financial target reached  
    - [ ] Official Smartup Business Plan ready  
    - [ ] Leadership Team formed  
    - [ ] Majority community vote  

    [:material-arrow-right: Learn more](#)

- :simple-materialdesignicons:{ .lg .middle } **Phase 2: Design**  
    **The Question:** *"How can we build this sustainably and efficiently?"*  
    Contributors create blueprints through open collaboration, with rigorous scientific review before development begins.  

    **Thresholds to advance:**  
    - [ ] Financial target reached  
    - [ ] Design Blueprint delivered  
    - [ ] Science Team review passed  
    - [ ] Majority community vote  

    [:material-arrow-right: Learn more](#)

- :material-file-code:{ .lg .middle } **Phase 3: Production**  
    **The Focus:** *From thinking to building*  
    The community creates an MVP, tests with real citizens, and prepares for launch after scientific and market validation.  

    **Thresholds to advance:**  
    - [ ] Financial target reached  
    - [ ] Version 1.0 beta tested  
    - [ ] Market assessment complete  
    - [ ] Majority community vote  

    [:material-arrow-right: Learn more](#)

- :fontawesome-solid-magnifying-glass-chart:{ .lg .middle } **Phase 4: Organization**  
    **The Goal:** *Ready for the world*  
    Build the team and structure for market launch. Executive team chosen, legal framework set, always with community validation.  

    **Thresholds for launch:**  
    - [ ] Financial target reached  
    - [ ] Executive team formed  
    - [ ] Final Business Plan ready  
    - [ ] Majority community vote  

    [:material-arrow-right: Learn more](#)

</div>

!!! tip "The Common Thread"
    Notice how each phase requires four key elements:  
    1. **Financial sustainability** – Resources to continue  
    2. **Concrete deliverable** – Something tangible produced  
    3. **Expert validation** – Scientific or market review  
    4. **Democratic approval** – The community decides  

    This ensures what's being built is wanted, sound, and fully owned by the community at every step.

```mermaid
flowchart TB
    V[🔍 Validation<br/><sub>Prove demand</sub>]
    D[📐 Design<br/><sub>Create blueprint</sub>]
    P[🔨 Production<br/><sub>Build & test</sub>]
    O[🚀 Organization<br/><sub>Launch ready</sub>]
    
    V -.->|Community Vote| D
    D -.->|Community Vote| P
    P -.->|Community Vote| O
    O ==>|To Market!| M[🌍]
    
    style V stroke:#ffd23f,stroke-width:3px
    style D stroke:#ffd23f,stroke-width:3px
    style P stroke:#ffd23f,stroke-width:3px
    style O stroke:#ffd23f,stroke-width:3px
    style M stroke:#8bc34a,stroke-width:3px
```

---

!!! tip "Why these phases?"
    Each phase ensures what’s being built is wanted, sound, and fully owned by the community before advancing. Built-in checkpoints—majority votes and scientific reviews—keep momentum aligned with trust and quality at every step.

---

**Next:** See how Smartup teams, roles, and workflows make collective building a reality.

[:material-arrow-right-bold: Continue to Anatomy & Workflows](#)

---

## :material-dna: The Smartup Organism

!!! info "What is this?"
    To create real, relevant technology, a Smartup can’t just be a loose network—it needs to be a productive, living system. But if nobody has absolute power—not even a CEO—how do decisions get made and meaningful work actually happen? The answer: the Smartup is a new kind of “organism” built for collective intelligence and self-organization.

---

###  Democratic by Nature, Military in Execution

 A Smartup is a unique sociotechnical organism that combines democratic governance with military-precision execution. This hybrid design solves a fundamental challenge: how to maintain collective ownership while actually getting things done.

**The Design Principle**

**We are democratic where it matters most**: In the General Forum, every citizen has equal voice, equal vote, equal responsibility. Here we decide WHAT we build and WHY—our mission, values, and strategic direction.

**We are disciplined where speed matters**: In the Workplace, we apply military-inspired command structures and proven operational processes. Here we decide HOW we build—with clear roles, accountability, and chains of command.


!!! warning "Learning from Failed Models"
    **Pure Democracy Everywhere** = Endless debates, nothing ships  
    **Pure Hierarchy Everywhere** = Mission drift, worker alienation  
    **Our Hybrid** = Collective ownership + Professional execution

---
### Smartup Anatomy

If you could slice a Smartup open, you’d see something that looks more like a living ecosystem than a traditional corporate pyramid. Instead of strict hierarchy and top-down control, power and responsibility are distributed through a holacratic structure: **nested groups, each supporting the whole.**

> _“Holacracy is a new way of structuring and running your organization that replaces the conventional management hierarchy. Instead of top-down, power is distributed throughout, giving individuals and teams more freedom to self-manage, while staying aligned to the organization’s purpose.”_  
> — holacracy.org

In a Smartup, these circles are groups—each one crucial for the whole, each one depending on—and empowering—the next.

---

## :material-layers-triple: The Six Groups of Productivity

A Smartup is designed so that all ownership, work, and governance flow through six nested groups.  
Think of them as a set of Russian dolls: each group contains smaller subgroups, but all belong to the "mother" at the center, the General Forum.

![Centered image](../assets/diagrams/the 6 groups of productivity.png){ style="display: block; margin: 0 auto; width: 400px;" }

<div class="grid cards" markdown>

- :material-forum:{ .lg .middle } **1. General Forum**

    ---
    
    **The heart of the Smartup**
    
    All citizens (owners) gather here to discuss, propose, vote, and oversee everything. It's the public square for collective direction and accountability.
    
    **Members:** All Smartup owners  
    **Moderated by:** Leadership Team

- :material-briefcase:{ .lg .middle } **2. Workplace**

    ---
    
    **The production engine**
    
    Citizens with a work license join to build what matters. Here, talk turns into action: plans become teams, teams build real things.
    
    **Members:** All workers (colleagues)  
    **Moderated by:** Leadership Team

- :material-account-group:{ .lg .middle } **3. Teams**

    ---
    
    **Home base for specialized work**
    
    Every worker joins at least one team—design, development, business. Teams focus effort and harness specific skills toward shared goals.
    
    **Members:** Workers in same team (teammates)  
    **Moderated by:** Team Captain

- :material-card-account-details:{ .lg .middle } **4. Roles**

    ---
    
    **How you contribute**
    
    In each team, workers apply for roles that fit their talents—UX designer, developer, communicator. Roles define responsibility and access.
    
    **Members:** Workers with same role (peers)  
    **Moderated by:** Team Captain

- :material-target:{ .lg .middle } **5. Objectives**

    ---
    
    **What's to be achieved**
    
    Teams progress by accomplishing specific missions, like "Create Android app front-end." Each objective unites multiple roles.
    
    **Members:** Workers on same objective (squad)  
    **Moderated by:** Mission Leader

- :material-checkbox-marked-circle:{ .lg .middle } **6. Tasks**

    ---
    
    **Where work happens**
    
    The smallest—and most important—unit. Tasks create measurable progress. Complete task, create value, get rewarded.
    
    **Members:** Assigned workers  
    **Moderated by:** Mission Leader

</div>

!!! tip "The Nested Structure"
    Each group lives within the one above it:<br>
    - General Forum contains → Workplace<br>
    - Workplace contains → Teams  <br>
    - Teams contain → Roles<br>
    - Roles work on → Objectives<br>
    - Objectives break into → Tasks<br>
    This creates clear accountability chains while maintaining democratic oversight at the top.
---



## :material-triangle: The Metabolism - How a Smartup Lives and Breathes

!!! info "What is this?"
    If the 6 Groups show a Smartup's anatomy (structure), the metabolism shows how it actually functions—how we communicate, make decisions, and get work done through the ADM Triangle system powered by the buddy system.

When we examine a Smartup as a living organism, we need to understand not just its structure, but how it sustains itself. Just as a body needs circulation and digestion, a Smartup needs processes for communication, decision-making, and documentation. This is where we discover the ADM Triangle—the metabolic engine that powers every interaction.

### The Buddy System: Never Work Alone

At the core of our metabolism lies a simple but powerful principle borrowed from military operations: **you never work alone**. In a Smartup, every task, every decision, every action involves at least two people working in partnership.

!!! tip "Why Buddies Matter"
    The buddy system serves multiple vital functions:<br>
    - **Accountability**: Freedom with responsibility<br>
    - **Support**: Help when stuck or overwhelmed  <br>
    - **Quality**: Built-in peer review<br>
    - **Learning**: Juniors learn by observing seniors<br>
    - **Resilience**: No single point of failure<br>

**The Learning Loop**

What makes our buddy system special is that it's designed as a learning mechanism:

```mermaid
graph LR
    J[Junior Role<br/><sub>Defender/Assistant</sub>] 
    S[Senior Role<br/><sub>Attacker/Worker</sub>]
    T[Task Execution]
    L[Learning & Growth]
    
    S -->|Performs| T
    J -->|Observes & Assists| T
    T -->|Creates| L
    L -->|Promotes| J
    J -.->|Becomes| S    
```

**The 90/10 Split**: When a task is completed:
- Worker (Senior) receives 90% of the budget<br>
- Assistant (Junior) receives 10%<br>

This isn't just payment for monitoring—it's investment in developing the next generation of senior contributors.

### The ADM Triangle: Our Operating System

Building on the buddy system, every interaction in a Smartup follows the **Attacker, Defender, Midfielder** (ADM) pattern:

```mermaid
graph TD
    A[Attacker/Senior<br/><sub>Drives action forward</sub>]
    D[Defender/Junior<br/><sub>Learns while ensuring quality</sub>]
    M[Midfielder/Bot<br/><sub>Coordinates & documents</sub>]
    
    A <--> M
    D <--> M
    A -.->|Mentors| D
    
```


**How It Works in Practice**

!!! example "ADM in Action: Task Execution"
    **Scenario**: A senior developer takes on the task "Deploy emergency mesh network prototype"<br>
    1. **Senior Developer (Attacker)**: Implements solution, explains decisions<br>
    2. **Junior Developer (Defender)**: Assists, learns patterns, validates effort<br>
    3. **Bot (Midfielder)**: Logs activity, manages check-ins<br>
    The junior isn't just watching—they're actively learning deployment processes, understanding architectural decisions, and preparing to lead similar tasks in the future.

!!! quote "Learning by Doing"
    "The assistant learns how the worker solves a specific task and gains knowledge and skills. Defenders are literally learning to become seniors."


### Beyond Surveillance: A Learning Organization

!!! warning "This Isn't About Control"
    Traditional organizations use monitoring for compliance and control. In a Smartup, the buddy system creates a learning environment where:<br>
    - Juniors gain real experience with safety nets<br>
    - Seniors develop mentoring and leadership skills<br>
    - Knowledge spreads organically through the organization<br>
    - No one carries administrative burden alone<br>
    **The defender role isn't a watchdog—it's an apprenticeship. This transforms what could feel like surveillance into an opportunity for growth.**

**The Freedom to Shift: Horizontal Career Development**

What makes Smartup identity truly revolutionary is **voluntary role shifting**. Unlike traditional organizations where you're locked into your expertise, we embrace career fluidity.

!!! example "Role Shifting in Practice"
    **Marcus has been a senior backend developer for 5 years. He's excellent at it, but getting bored.**<br>
    **Traditional Organization**: Marcus is stuck. His value is tied to his seniority in backend. Moving to UX means starting over, losing status and pay.<br>
    **In a Smartup**: Marcus can:<br>
    - Continue taking senior backend tasks when he wants (90% as attacker)<br>
    - Join the UX team as a junior member<br>
    - Take on UX tasks as a defender (10%, learning from senior UX designers)<br>
    - Gradually build UX skills while maintaining backend income<br>
    - Eventually take on senior UX roles as skills develop<br>
    **Result**: Marcus expands his skillset, stays engaged, and the Smartup gains a developer who understands both backend AND user experience.

!!! tip "Why This Matters"
    **For Individuals**:
    - Never get trapped in a single role<br>
    - Learn new skills while earning<br>
    - Find renewed passion through variety<br>
    - Build cross-functional understanding<br>
    **For the Smartup**:<br>
    - Retain talented people who might otherwise leave from boredom<br>
    - Create bridges between teams through shared members<br>
    - Build resilience—more people can cover more roles<br>
    - Foster innovation through cross-pollination<br>

**The Learning Economy**

This fluid identity system creates what we call a **learning economy**:

```mermaid
graph LR
    SE[Senior Expert<br/><sub>Feeling Stagnant</sub>]
    JL[Junior Learner<br/><sub>in New Domain</sub>]
    ME[Multi-skilled Expert<br/><sub>Cross-functional</sub>]
    IV[Increased Value<br/><sub>To Individual & Smartup</sub>]
    
    SE -->|Chooses to Explore| JL
    JL -->|Learns Through Tasks| ME
    ME -->|Creates| IV
    IV -->|Enables More| SE
```

!!! quote "Breaking the Specialization Trap"
    "Traditional organizations want you to stay in your box—it's easier to manage. But humans aren't meant to do one thing forever. A Smartup embraces our natural desire to grow, learn, and evolve."

Why Identity Shifting Matters
!!! example "Identity in Action"
    Sarah is a senior developer who's curious about business development. Watch her fluid day:<br>
    **9:00 AM - General Forum**: As a CITIZEN, she votes on strategic direction, her voice equal to everyone's.<br>
    **9:30 AM - Workplace**: As a COLLEAGUE, she discusses overall progress in the OSBP.<br>
    **10:00 AM - Dev Team**: As a senior TEAM MEMBER, she guides technical architecture decisions.<br>
    **11:00 AM - Task #42**: As an ATTACKER, she codes a critical feature (earning 90% of task value).<br>
    **2:00 PM - Business Team**: As a junior TEAM MEMBER, she joins market research discussions.<br>
    **3:00 PM - Task #78**: As a DEFENDER, she assists on a competitor analysis task, learning from the senior business developer (earning 10% while learning).<br>
    **End of Day**: Sarah earned well from her senior work AND gained business skills. The Smartup gets a developer who understands market pressures.<br>

!!! tip "The Power of Context"
    By explicitly naming who we are in each space, we: <br>
    - Prevent power dynamics from poisoning collaboration<br>
    - Create psychological safety for honest communication<br>
    - Enable rapid context switching without confusion<br>
    - Build empathy by experiencing multiple perspectives<br>
    - Allow graceful transition between expert and learner modes<br>

**Making the Shift**
Switching roles in a Smartup is designed to be frictionless:

- See an interesting team? Join their public channel <br>
- Want to learn? Apply for junior roles in that team<br>
- Keep earning: Maintain senior roles in your expertise area<br>
- Grow gradually: Take on more advanced tasks as you learn<br>
- No permission needed: Your career path is yours to design<br>



---

### Identity Protocols: Who We Become in Each Space

!!! info "What is this?"
    As we move between the 6 groups, we don't just change what we do—we change who we are. These identity protocols teach us how to show up in each space for maximum collective effective$

**The Six Identities We Embody**

<div class="grid cards" markdown>

- :material-forum:{ .lg .middle } **In the General Forum**
    ---
    **We are CITIZENS**

    Equal voice, equal vote, equal responsibility. Here, the newest contributor has the same rights as the founding team. We debate, propose, and decide as equals.

    *"In this space, I am a citizen with rights and obligations"*

- :material-briefcase:{ .lg .middle } **In the Workplace**
    ---
    **We are COLLEAGUES**

    United by shared mission. We may have different skills and tasks, but we're all building toward the same vision. Collaboration over competition.

    *"In this space, I am a colleague working for our shared idea"*

- :material-account-group:{ .lg .middle } **In Teams**
    ---
    **We are TEAM MEMBERS**

    Aligned on objectives. We coordinate our diverse skills toward specific goals, supporting each other's growth and success.

    *"In this space, I am a team member working on our objectives"*

- :material-card-account-details:{ .lg .middle } **In Roles**
    ---
    **We are PEERS**

    Sharing expertise. Whether senior or junior, we're united by our craft, helping each other improve and solve technical challenges.

    *"In this space, I am a peer sharing skills and knowledge"*

- :material-target:{ .lg .middle } **In Objectives**
    ---
    **We are SQUAD MEMBERS**
    
     Aligned on objectives. We coordinate our diverse skills toward specific goals, supporting each other's growth and success.

    *"In this space, I am a team member working on our objectives"*

- :material-card-account-details:{ .lg .middle } **In Roles**
    ---
    **We are PEERS**

    Sharing expertise. Whether senior or junior, we're united by our craft, helping each other improve and solve technical challenges.

    *"In this space, I am a peer sharing skills and knowledge"*

- :material-target:{ .lg .middle } **In Objectives**
    ---
    **We are SQUAD MEMBERS**

    Present and focused. We're here now, working on this specific mission, coordinating in real-time to achieve our goal.

    *"In this space, I am a squad member present and engaged"*

- :material-checkbox-marked-circle:{ .lg .middle } **In Tasks**
    ---
    **We are ATTACKERS & DEFENDERS**

    Executing with discipline. We take on specific roles—driving work forward or ensuring quality—with clear accountability.

    *"In this space, I am actively attacking or defending this task"*

</div>

**Why Identity Shifting Matters**

!!! example "Identity in Action"
    **Sarah is a senior developer in Smartup Zero. Watch how she shifts:**
    
    **9:00 AM - General Forum**: As a CITIZEN, she votes on whether to pursue mesh networking, weighing in equally with designers and business developers.
    
    **9:30 AM - Workplace**: As a COLLEAGUE, she reviews the overall ONLIFE roadmap, offering technical insights while respecting other disciplines.
    
    **10:00 AM - Dev Team**: As a TEAM MEMBER, she coordinates with other developers on the sprint plan.
    
    **10:30 AM - Backend Role**: As a PEER, she mentors a junior backend developer struggling with mesh protocols.
    
    **11:00 AM - "Build MVP" Objective**: As a SQUAD MEMBER, she syncs with frontend and QA on today's integration.
    
    **11:30 AM - Task #42**: As an ATTACKER, she codes the mesh discovery feature while her junior DEFENDER reviews and learns.

!!! tip "The Power of Context"
    By explicitly naming who we are in each space, we:<br>
    - Prevent power dynamics from poisoning collaboration<br>
    - Create psychological safety for honest communication<br>  
    - Enable rapid context switching without confusion<br>
    - Build empathy by experiencing multiple perspectives<br>


**Learning the Dance**
New contributors often struggle with identity shifting at first. That's normal—we're conditioned by traditional organizations to maintain rigid roles. But with practice, this fluidity becomes natural and empowering.


!!! warning "Identity Discipline"
    These aren't just nice ideas—they're operational requirements. In our Matrix/Element spaces, channels are named and moderated to reinforce these identities. Bringing "boss energy" to a peer space or "individual contributor" mindset to the General Forum disrupts our collective intelligence

### The Meta-Transparency Layer: ADM Between Groups

!!! info "What is this?"
    The ADM Triangle doesn't just operate within groups—it creates a transparency cascade from the outside world all the way down to individual tasks, ensuring accountability and alignment at every level.

We've seen how the ADM Triangle works within each group. But the true power emerges when we see how it connects the groups themselves, creating what we call the **meta-transparency layer**—a complete chain of accountability from public oversight to task execution.

**The Oversight Cascade**

Each group in our 6-layer structure maintains oversight of the group below it through its own ADM Triangle:

<div class="grid cards" markdown>

- :material-earth:{ .lg .middle } **0_timeline → General Forum** <br>
    **A**: Citizens taking initiative with proposals/votes<br>
    **D**: Leadership team ensuring quality moderation<br>
    **M**: Bot documents everything to 0_timeline<br>
    *The outside world sees our governance in action*

- :material-forum:{ .lg .middle } **General Forum → Workplace**<br>
    **A**: Colleagues taking initiative with work<br>
    **D**: Leadership team ensuring OSBP compliance<br>
    **M**: Bot reports progress to General Forum<br>
    *Citizens oversee how work gets done*

- :material-briefcase:{ .lg .middle } **Workplace → Teams**<br>
    **A**: Team members taking initiative in teams<br>
    **D**: Team captains ensuring strategy/budgets<br>
    **M**: Bot reports team health to Workplace<br>
    *Colleagues oversee team formation*

- :material-account-group:{ .lg .middle } **Teams → Roles**<br>
    **A**: Peers taking initiative in skill areas<br>
    **D**: Team captain ensuring roles are filled<br>
    **M**: Bot reports role coverage to Teams<br>
    *Teams oversee skill distribution*

- :material-card-account-details:{ .lg .middle } **Roles → Objectives**<br>
    **A**: Squad members taking initiative on missions<br>
    **D**: Mission leaders ensuring coordination<br>
    **M**: Bot reports objective progress to Roles<br>
    *Peers oversee objective participation*

- :material-target:{ .lg .middle } **Objectives → Tasks**<br>
    **A**: Worker taking initiative to complete<br>
    **D**: Assistant ensuring quality/learning<br>
    **M**: Bot reports task status to Objectives<br>
    *Squads oversee task execution*

</div>

** The Complete Transparency Flow**

```mermaid
graph TD
    OT[0_timeline<br/>Outside World]
    GF[1_general_forum<br/>All Citizens]
    WP[2_workplace<br/>All Colleagues]
    TM[3_teams<br/>Team Members]
    RL[4_roles<br/>Peers]
    OB[5_objectives<br/>Squad Members]
    TS[6_tasks<br/>Worker + Assistant]
    
    OT -->|oversees| GF
    GF -->|oversees| WP
    WP -->|oversees| TM
    TM -->|oversees| RL
    RL -->|oversees| OB
    OB -->|oversees| TS
    
    TS -.->|reports up| OB
    OB -.->|reports up| RL
    RL -.->|reports up| TM
    TM -.->|reports up| WP
    WP -.->|reports up| GF
    GF -.->|reports up| OT
```

!!! example "A Complete Flow Example"
    Let's follow a decision from inception to execution:<br><br>
    **Day 1 - Citizen Initiative**:<br>
    In the General Forum, citizens (A) propose adding mesh networking to ONLIFE. Leadership team (D) facilitates discussion. Bot (M) publishes proposal to 0_timeline.<br><br>
    **Day 3 - Vote Passes**:<br>
    Colleagues in Workplace (A) volunteer to implement. Leadership team (D) ensures it fits OSBP. Bot (M) reports commitment to General Forum.<br><br>
    **Day 5 - Team Forms**:<br>
    Dev team members (A) organize around mesh networking. Team captain (D) allocates budget and strategy. Bot (M) reports team formation to Workplace.<br><br>
    **Day 7 - Roles Activate**:<br>
    Backend peers (A) define mesh protocol skills needed. Team captain (D) ensures roles are properly staffed. Bot (M) reports skill gaps to Teams.<br><br>
    **Day 10 - Objective Launches**:<br>
    Squad members (A) begin "Build Mesh Prototype" objective. Mission leader (D) coordinates resources. Bot (M) reports progress to Roles.<br><br>
    **Day 12 - Tasks Execute**:<br>
    Senior dev (A) codes mesh discovery feature. Junior dev (D) assists and learns. Bot (M) logs 4 hours work, reports completion to Objective.<br><br>
    **Result**: Complete transparency from public proposal to code commit. Every stakeholder can trace the path.

!!! tip "Why This Matters"
    Traditional organizations hide their operations behind closed doors. Our meta-transparency means:<br>
    - Public can see how decisions become reality<br>
    - Citizens can track their proposals through execution<br>
    - Workers understand why they're building what they're building<br>
    - No black boxes, no hidden agendas<br>
    - Trust through transparency at every level

!!! warning "Information Overload?"
    With transparency at every level, we risk drowning in data. That's why the bot middleware is crucial—it filters and summarizes, ensuring each level gets the right amount of detail. Citizens don't see every git commit; task workers don't get flooded with governance debates.
---

## :material-file-document-multiple: The Official Smartup Business Plan (OSBP)

!!! info "What is this?"
    The OSBP is the living, breathing constitution of a Smartup—where an entrepreneur's vision transforms into collective property through democratic participation and continuous evolution.

### From "My Idea" to "Our Mission"

Every Smartup begins with an entrepreneur who sees a solution to an SDG challenge. But unlike traditional startups where founders retain control, the OSBP is the mechanism for transferring ownership to the collective.

```mermaid
flowchart TB
    E[Entrepreneur<br/>Vision v0.1] --> C[Community<br/>Validation]
    C --> T[Teams Add<br/>Assessments]
    T --> V1[OSBP v1.0<br/>Design Phase]
    V1 --> V2[OSBP v2.0<br/>Production]
    V2 --> V3[OSBP v3.0<br/>Organization]
    V3 --> V4[OSBP v4.0<br/>Market Ready]
    
    style E fill:#ff6b6b
    style V4 fill:#8bc34a
```

### The Three Groundings

Every OSBP must establish legitimacy through three essential groundings:

<div class="grid cards" markdown>

- :material-earth:{ .lg .middle } **SDG Grounding**
    ---<br>
    Which SDGs does this address?<br>
    Why is this problem critical?<br>
    How does our solution help?<br>
    What's the measurable impact?<br>
    Links to UN frameworks<br>

- :material-flask:{ .lg .middle } **Scientific Grounding**
    ---<br>
    Evidence the solution works<br>
    Research backing approach<br>
    Technical feasibility studies<br>
    Peer-reviewed references<br>
    Testable hypotheses<br>

- :material-account-multiple:{ .lg .middle } **Democratic Grounding**
    ---<br>
    The validation test:<br>
    Current owners: X joined<br>
    Target owners: Y needed<br>
    Funding: €X of €Y goal<br>
    Teams forming: X of Y needed<br>
    **"Do enough people want this?"**<br>

</div>

!!! tip "Why Three Groundings?"
    **SDG**: Ensures we're solving real planetary problems<br>
    **Scientific**: Proves our solution can actually work<br>
    **Democratic**: Tests if enough people care to make it happen<br><br>
    Together, they prevent building solutions nobody needs.

### The Democratic Test

The democratic grounding is the entrepreneur's ultimate reality check:

!!! quote "From 'I Think' to 'We Know'"
    "I think this is a good idea and I've done my homework. Now let's find out if enough other people agree and want this as badly as I do. Not through surveys or likes, but through real commitment—joining as owners, contributing funds, volunteering skills. If we can't rally enough people in validation, we shouldn't build it."

This democratic grounding happens through:<br>
- **Crowdfunding success**: People vote with their wallets<br>
- **Team formation**: Skilled people volunteer their time<br>
- **Owner recruitment**: Citizens join the mission<br>
- **Financial thresholds**: Real money proves real demand<br>
- **Active participation**: Not just watchers but builders<br>

By the end of validation, we don't guess there's demand—we've proven it through collective action.

### OSBP Structure for Validation Phase

The OSBP sections map directly to team responsibilities:

| Section | Responsible Team | Core Questions |
|---------|-----------------|----------------|
| **1. Executive Summary** | Leadership Team | Why does the world need this? What's our vision? |
| **2. Design Blueprint** | Design Team | How will it work from user perspective? |
| **3. Development Blueprint** | Development Team | How do we build it? What's been built? |
| **4. Business & Marketing** | Business Team | How does it sustain itself? Validation budget? |
| **5. Media & Message** | Media Team | How do we communicate? What's our voice? |
| **6. R&D Roadmap** | Science Team | What research questions must we answer? |
| **7. Definition of Ready** | Operational Team | When are we ready for Design Phase? |

### The Living Document Process

!!! example "How OSBP Updates Work"
    **Day 1**: Design team improves user flow section<br>
    **Day 2**: Team captain submits changes to Workplace<br>
    **Day 2-5**: Lazy consensus period (72 hours)<br>
    - No objections from 3+ colleagues = proceed<br>
    - Objections = discussion and resolution<br>
    **Day 5-7**: General Forum notification (48 hours)<br>
    - Final chance for any owner to raise concerns<br>
    **Day 7**: Auto-published to live OSBP on 0_timeline<br>

```mermaid
flowchart LR
    TC[Team Creates<br/>Update] --> WR[Workplace<br/>Review]
    WR -->|72hr lazy consensus| GF[General Forum<br/>Notification]
    GF -->|48hr final review| PUB[Published to<br/>0_timeline]
    
    WR -->|Objections| DIS[Discussion &<br/>Resolution]
    DIS --> WR
    
    style PUB fill:#8bc34a
```

### Version Evolution

| Version | Phase | Status | Meaning |
|---------|--------|---------|----------|
| **v0.1** | Pre-validation | Entrepreneur's proposal | Individual vision seeking collective |
| **v0.2-0.9** | Validation | Team assessments added | Collective shaping and ownership |
| **v1.0** | Design entry | Validated plan | Community approved, ready to design |
| **v2.0** | Production entry | Designed solution | Blueprints complete, ready to build |
| **v3.0** | Organization entry | Built product | MVP done, ready to organize |
| **v4.0** | Market entry | Launch ready | Complete plan for sustainable operation |

### From Assessment to Leadership

The OSBP naturally identifies leaders through work:

1. **Teams collaborate** on their OSBP section
2. **Quality contributors emerge** through the writing
3. **Natural coordination** becomes visible
4. **Team elects captain** based on demonstrated ability
5. **Captains form** Leadership Team

!!! warning "Not a Static Document"
    Traditional business plans are fiction about the future. The OSBP is living documentation of our evolving reality. Every pivot, every learning, every decision gets captured in real-time.

### Access and Transparency

**Where it lives**:<br> Version controlled in Forgejo, rendered on 0_timeline<br>
**Who can read**:<br> Everyone (public)<br>
**Who can propose changes**:<br> Team members for their sections<br>
**Who approves**:<br> Lazy consensus through Workplace + Forum<br>
**Update frequency**:<br> Continuous as we learn<br>

!!! quote "The Document That Binds Us"
    "The OSBP isn't what we pitch to investors—we don't have any. It's what we promise each other and the world. It's our collective memory, our shared vision, and our operational reality all in one living document."
