<inputclass="md-option"data-md-color-media=""data-md-color-scheme="default"data-md-color-primary="amber"data-md-color-accent="lime"aria-label="Switch to dark mode"type="radio"name="__palette"id="__palette_0">
<labelclass="md-header__button md-icon"title="Switch to dark mode"for="__palette_1"hidden>
<inputclass="md-option"data-md-color-media=""data-md-color-scheme="slate"data-md-color-primary="amber"data-md-color-accent="lime"aria-label="Switch to light mode"type="radio"name="__palette"id="__palette_1">
<labelclass="md-header__button md-icon"title="Switch to light mode"for="__palette_0"hidden>
<p>The Social Subsystem describes how people in a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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.</p>
</div>
<detailsclass="tip">
<summary>Just give me the abstract</summary>
<p>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 <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr>, 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.</p>
<h2id="the-architecture-of-a-smartup"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M21 16.5c0 .38-.21.71-.53.88l-7.9 4.44c-.16.12-.36.18-.57.18s-.41-.06-.57-.18l-7.9-4.44A.99.99 0 0 1 3 16.5v-9c0-.38.21-.71.53-.88l7.9-4.44c.16-.12.36-.18.57-.18s.41.06.57.18l7.9 4.44c.32.17.53.5.53.88zM12 4.15 6.04 7.5 12 10.85l5.96-3.35zM5 15.91l6 3.38v-6.71L5 9.21zm14 0v-6.7l-6 3.37v6.71z"/></svg></span> The Architecture of a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr><aclass="headerlink"href="#the-architecture-of-a-smartup"title="Permanent link">¶</a></h2>
<p><strong>Definition:</strong><br/>
A <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> creates trustworthy digital tools that help people—and the communities they form—become more resilient, resourceful, and effective in advancing the SDGs.</p>
<hr/>
<p><strong>At its core, every <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> is built like a rocket: a solid foundation, three structural pillars, and a sharp point of execution.</strong></p>
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. </li>
<li><strong>Democracy</strong><br/>
Our process and decisions are open and participatory. Everyone has a voice and a vote—no gated hierarchies, no closed rooms. </li>
<li><strong><abbrtitle="Enhanced problem-solving capacity created by collaborative, transparent teamwork.">Collective IQ</abbr></strong><br/>
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.</li>
</ul>
<hr/>
<h3id="the-three-pillars-our-structure">The Three Pillars (Our Structure)<aclass="headerlink"href="#the-three-pillars-our-structure"title="Permanent link">¶</a></h3>
<ul>
<li>
<p><strong><abbrtitle="Equal and inclusive ownership model based on contribution, not hierarchy or investment.">Collective Ownership</abbr></strong><br/>
All work and effort are shared—teams build, improve, and sustain everything the <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> delivers. Value is earned by doing, not by owning capital. </p>
</li>
<li>
<p><strong><abbrtitle="Transparent and democratic oversight of all operations, including deliberation and voting.">Collective Governance</abbr></strong><br/>
Decision-making and oversight are for everyone. Every contributor holds both rights and responsibilities for what the <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> does and how it does it.</p>
While we are democratic in nature, we are military in execution. When the General Forum sets a target, the <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr> 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.</li>
</ul>
<hr/>
<divclass="admonition info">
<pclass="admonition-title">Why a rocket?</p>
<p>A <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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.</p>
</div>
<hr/>
<h2id="the-4-phases-of-creation-the-habitat-of-a-smartup"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M11 21v-4.26c-.47.17-.97.26-1.5.26C7 17 5 15 5 12.5c0-1.27.5-2.41 1.36-3.23C6.13 8.73 6 8.13 6 7.5 6 5 8 3 10.5 3c1.56 0 2.94.8 3.75 2h.25a5.5 5.5 0 0 1 5.5 5.5 5.5 5.5 0 0 1-5.5 5.5q-.75 0-1.5-.21V21z"/></svg></span> The 4 <abbrtitle="Four required stages: Validation, Design, Production, Organization.">Phases of Creation</abbr> - The Habitat of a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr><aclass="headerlink"href="#the-4-phases-of-creation-the-habitat-of-a-smartup"title="Permanent link">¶</a></h2>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>Every <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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 <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> community.</p>
<strong>The Question:</strong><em>"Does the world need this?"</em><br/>
Entrepreneurs and early adopters rally a vibrant community around a solution, showing real traction in people and resources. </p>
<p><strong>Thresholds to advance:</strong><br/>
- [ ] Financial target reached<br/>
- [ ] <abbrtitle="Living document recording strategy, decisions, assessments, and design. Transparent to all owners.">Official Smartup Business Plan</abbr> ready<br/>
- [ ] <abbrtitle="Strategic core of Smartup creation phases. Composed of all Team Captains and the initiating entrepreneur.">Leadership Team</abbr> formed<br/>
style M stroke:#8bc34a,stroke-width:3px</code></pre>
<hr/>
<divclass="admonition tip">
<pclass="admonition-title">Why these phases?</p>
<p>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.</p>
</div>
<hr/>
<p><strong>Next:</strong> See how <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> teams, roles, and workflows make collective building a reality.</p>
<p><ahref="#"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M4 15V9h8V4.16L19.84 12 12 19.84V15z"/></svg></span> Continue to Anatomy & Workflows</a></p>
<hr/>
<h2id="the-smartup-organism"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M4 2h2v2c0 1.44.68 2.61 1.88 3.78.86.83 2.01 1.63 3.21 2.42l-1.83 1.19C8.27 10.72 7.31 10 6.5 9.21 5.07 7.82 4 6.1 4 4zm14 0h2v2c0 2.1-1.07 3.82-2.5 5.21-1.41 1.38-3.21 2.52-4.96 3.63-1.75 1.12-3.45 2.21-4.66 3.38C6.68 17.39 6 18.56 6 20v2H4v-2c0-2.1 1.07-3.82 2.5-5.21 1.41-1.38 3.21-2.52 4.96-3.63 1.75-1.12 3.45-2.21 4.66-3.38C17.32 6.61 18 5.44 18 4zm-3.26 10.61c.99.67 1.95 1.39 2.76 2.18C18.93 16.18 20 17.9 20 20v2h-2v-2c0-1.44-.68-2.61-1.88-3.78-.86-.83-2.01-1.63-3.21-2.42zM7 3h10v1l-.06.5H7.06L7 4zm.68 3h8.64c-.24.34-.52.69-.9 1.06l-.51.44H9.07l-.49-.44c-.38-.37-.66-.72-.9-1.06m1.41 10.5h5.84l.49.44c.38.37.66.72.9 1.06H7.68c.24-.34.52-.69.9-1.06zm-2.03 3h9.88l.06.5v1H7v-1z"/></svg></span> The <abbrtitle="Metaphor for the Smartup as a multi-layered living system where roles and processes work in unison.">Smartup Organism</abbr><aclass="headerlink"href="#the-smartup-organism"title="Permanent link">¶</a></h2>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>To create real, relevant technology, a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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 <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> is a new kind of “organism” built for collective intelligence and self-organization.</p>
</div>
<hr/>
<h3id="democratic-by-nature-military-in-execution">Democratic by Nature, Military in Execution<aclass="headerlink"href="#democratic-by-nature-military-in-execution"title="Permanent link">¶</a></h3>
<p>A <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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.</p>
<p><strong>The Design Principle</strong></p>
<p><strong>We are democratic where it matters most</strong>: 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.</p>
<p><strong>We are disciplined where speed matters</strong>: In the <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr>, we apply military-inspired command structures and proven operational processes. Here we decide HOW we build—with clear roles, accountability, and chains of command.</p>
<divclass="admonition warning">
<pclass="admonition-title">Learning from Failed Models</p>
<strong>Our Hybrid</strong> = Collective ownership + Professional execution</p>
</div>
<hr/>
<h3id="smartup-anatomy"><abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> Anatomy<aclass="headerlink"href="#smartup-anatomy"title="Permanent link">¶</a></h3>
<p>If you could slice a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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: <strong>nested groups, each supporting the whole.</strong></p>
<blockquote>
<p><em>“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.”</em><br/>
— holacracy.org</p>
</blockquote>
<p>In a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr>, these circles are groups—each one crucial for the whole, each one depending on—and empowering—the next.</p>
<hr/>
<h2id="the-six-groups-of-productivity"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M12 0 3 7l1.63 1.27L12 14l7.36-5.73L21 7zm7.37 10.73L12 16.47l-7.38-5.73L3 12l9 7 9-7zm0 5L12 21.47l-7.38-5.73L3 17l9 7 9-7z"/></svg></span> The Six Groups of Productivity<aclass="headerlink"href="#the-six-groups-of-productivity"title="Permanent link">¶</a></h2>
<p>A <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> is designed so that all ownership, work, and governance flow through six nested groups.<br/>
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.</p>
<p><strong>The heart of the <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr></strong></p>
<p>All citizens (owners) gather here to discuss, propose, vote, and oversee everything. It's the public square for collective direction and accountability.</p>
<p><strong>Members:</strong> All <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> owners<br/>
<strong>Moderated by:</strong><abbrtitle="Strategic core of Smartup creation phases. Composed of all Team Captains and the initiating entrepreneur.">Leadership Team</abbr></p>
<p>Citizens with a work license join to build what matters. Here, talk turns into action: plans become teams, teams build real things.</p>
<p><strong>Members:</strong> All workers (colleagues)<br/>
<strong>Moderated by:</strong><abbrtitle="Strategic core of Smartup creation phases. Composed of all Team Captains and the initiating entrepreneur.">Leadership Team</abbr></p>
<p><strong>Home base for specialized work</strong></p>
<p>Every worker joins at least one team—design, development, business. Teams focus effort and harness specific skills toward shared goals.</p>
<p><strong>Members:</strong> Workers in same team (teammates)<br/>
<strong>Moderated by:</strong><abbrtitle="Elected leader of a Team. Manages roles, budgets, tasks, and represents the team in Leadership.">Team Captain</abbr></p>
<p>In each team, workers apply for roles that fit their talents—UX designer, developer, communicator. <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr> define responsibility and access.</p>
<p><strong>Members:</strong> Workers with same role (peers)<br/>
<strong>Moderated by:</strong><abbrtitle="Elected leader of a Team. Manages roles, budgets, tasks, and represents the team in Leadership.">Team Captain</abbr></p>
- General Forum contains → <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr><br>
- <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr> contains → Teams <br>
- Teams contain → <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr><br>
- <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr> work on → <abbrtitle="Defined missions or sprints within Teams, breaking vision into actionable missions.">Objectives</abbr><br>
- <abbrtitle="Defined missions or sprints within Teams, breaking vision into actionable missions.">Objectives</abbr> break into → Tasks<br>
This creates clear accountability chains while maintaining democratic oversight at the top.</p>
</div>
<hr/>
<h2id="the-metabolism-how-a-smartup-lives-and-breathes"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M1 21h22L12 2"/></svg></span> The Metabolism - How a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> Lives and Breathes<aclass="headerlink"href="#the-metabolism-how-a-smartup-lives-and-breathes"title="Permanent link">¶</a></h2>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>If the 6 Groups show a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr>'s anatomy (structure), the metabolism shows how it actually functions—how we communicate, make decisions, and get work done through the <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr> system powered by the buddy system.</p>
</div>
<p>When we examine a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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 <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> needs processes for communication, decision-making, and documentation. This is where we discover the <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr>—the metabolic engine that powers every interaction.</p>
<h3id="the-buddy-system-never-work-alone">The Buddy System: Never Work Alone<aclass="headerlink"href="#the-buddy-system-never-work-alone"title="Permanent link">¶</a></h3>
<p>At the core of our metabolism lies a simple but powerful principle borrowed from military operations: <strong>you never work alone</strong>. In a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr>, every task, every decision, every action involves at least two people working in partnership.</p>
<divclass="admonition tip">
<pclass="admonition-title">Why Buddies Matter</p>
<p>The buddy system serves multiple vital functions:<br>
- <strong>Accountability</strong>: Freedom with responsibility<br>
- <strong>Support</strong>: Help when stuck or overwhelmed <br>
<p><strong>The 90/10 Split</strong>: When a task is completed:
- Worker (Senior) receives 90% of the budget<br>
- Assistant (Junior) receives 10%<br></p>
<p>This isn't just payment for monitoring—it's investment in developing the next generation of senior contributors.</p>
<h3id="the-adm-triangle-our-operating-system">The <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr>: Our Operating System<aclass="headerlink"href="#the-adm-triangle-our-operating-system"title="Permanent link">¶</a></h3>
<p>Building on the buddy system, every interaction in a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> follows the <strong>Attacker, Defender, Midfielder</strong> (ADM) pattern:</p>
<pclass="admonition-title">ADM in Action: <abbrtitle="Atomic unit of productive work. Defined, assigned, logged; triggers SC payout upon completion.">Task</abbr> Execution</p>
<p><strong>Scenario</strong>: A senior developer takes on the task "Deploy emergency mesh network prototype"<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.</p>
</div>
<divclass="admonition quote">
<pclass="admonition-title">Learning by Doing</p>
<p>"The assistant learns how the worker solves a specific task and gains knowledge and skills. Defenders are literally learning to become seniors."</p>
</div>
<h3id="beyond-surveillance-a-learning-organization">Beyond Surveillance: A Learning Organization<aclass="headerlink"href="#beyond-surveillance-a-learning-organization"title="Permanent link">¶</a></h3>
<divclass="admonition warning">
<pclass="admonition-title">This Isn't About Control</p>
<p>Traditional organizations use monitoring for compliance and control. In a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr>, 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>
<strong>The defender role isn't a watchdog—it's an apprenticeship. This transforms what could feel like surveillance into an opportunity for growth.</strong></p>
<p>What makes <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> identity truly revolutionary is <strong>voluntary role shifting</strong>. Unlike traditional organizations where you're locked into your expertise, we embrace career fluidity.</p>
<divclass="admonition example">
<pclass="admonition-title">Role Shifting in Practice</p>
<p><strong>Marcus has been a senior backend developer for 5 years. He's excellent at it, but getting bored.</strong><br>
<strong>Traditional Organization</strong>: Marcus is stuck. His value is tied to his seniority in backend. Moving to UX means starting over, losing status and pay.<br>
<strong>In a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr></strong>: 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>
<strong>Result</strong>: Marcus expands his skillset, stays engaged, and the <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> gains a developer who understands both backend AND user experience.</p>
</div>
<divclass="admonition tip">
<pclass="admonition-title">Why This Matters</p>
<p><strong>For Individuals</strong>:
- 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>
<strong>For the <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr></strong>:<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></p>
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</code></pre>
<divclass="admonition quote">
<pclass="admonition-title">Breaking the Specialization Trap</p>
<p>"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 <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> embraces our natural desire to grow, learn, and evolve."</p>
</div>
<p>Why Identity Shifting Matters</p>
<divclass="admonition example">
<pclass="admonition-title">Identity in Action</p>
<p>Sarah is a senior developer who's curious about business development. Watch her fluid day:<br>
<strong>9:00 AM - General Forum</strong>: As a CITIZEN, she votes on strategic direction, her voice equal to everyone's.<br>
<strong>9:30 AM - <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr></strong>: As a COLLEAGUE, she discusses overall progress in the OSBP.<br>
<strong>10:00 AM - Dev <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr></strong>: As a senior TEAM MEMBER, she guides technical architecture decisions.<br>
<strong>11:00 AM - <abbrtitle="Atomic unit of productive work. Defined, assigned, logged; triggers SC payout upon completion.">Task</abbr> #42</strong>: As an ATTACKER, she codes a critical feature (earning 90% of task value).<br>
<strong>2:00 PM - <abbrtitle="Team responsible for business strategy, marketing, financial planning, and the Official Smartup Business Plan (OSBP).">Business Team</abbr></strong>: As a junior TEAM MEMBER, she joins market research discussions.<br>
<strong>3:00 PM - <abbrtitle="Atomic unit of productive work. Defined, assigned, logged; triggers SC payout upon completion.">Task</abbr> #78</strong>: As a DEFENDER, she assists on a competitor analysis task, learning from the senior business developer (earning 10% while learning).<br>
<strong>End of Day</strong>: Sarah earned well from her senior work AND gained business skills. The <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> gets a developer who understands market pressures.<br></p>
</div>
<divclass="admonition tip">
<pclass="admonition-title">The Power of Context</p>
<p>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></p>
Switching roles in a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> is designed to be frictionless:</p>
<li>See an interesting team? Join their public channel <br></li>
<li>Want to learn? Apply for junior roles in that team<br></li>
<li>Keep earning: Maintain senior roles in your expertise area<br></li>
<li>Grow gradually: Take on more advanced tasks as you learn<br></li>
<li>No permission needed: Your career path is yours to design<br></li>
</ul>
<hr/>
<h3id="identity-protocols-who-we-become-in-each-space">Identity Protocols: Who We Become in Each Space<aclass="headerlink"href="#identity-protocols-who-we-become-in-each-space"title="Permanent link">¶</a></h3>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>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$</p>
<p>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.</p>
<p><em>"In this space, I am a citizen with rights and obligations"</em></p>
<p>United by shared mission. We may have different skills and tasks, but we're all building toward the same vision. Collaboration over competition.</p>
<p><em>"In this space, I am a colleague working for our shared idea"</em></p>
<p><strong>Sarah is a senior developer in <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> Zero. Watch how she shifts:</strong></p>
<p><strong>9:00 AM - General Forum</strong>: As a CITIZEN, she votes on whether to pursue mesh networking, weighing in equally with designers and business developers.</p>
<p><strong>9:30 AM - <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr></strong>: As a COLLEAGUE, she reviews the overall <abbrtitle="First pilot project of Smartup Zero—decentralized emergency citizen mesh network prototype.">ONLIFE</abbr> roadmap, offering technical insights while respecting other disciplines.</p>
<p><strong>10:00 AM - Dev <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr></strong>: As a TEAM MEMBER, she coordinates with other developers on the sprint plan.</p>
<p><strong>10:30 AM - Backend Role</strong>: As a PEER, she mentors a junior backend developer struggling with mesh protocols.</p>
<p><strong>11:00 AM - "Build MVP" Objective</strong>: As a SQUAD MEMBER, she syncs with frontend and QA on today's integration.</p>
<p><strong>11:30 AM - <abbrtitle="Atomic unit of productive work. Defined, assigned, logged; triggers SC payout upon completion.">Task</abbr> #42</strong>: As an ATTACKER, she codes the mesh discovery feature while her junior DEFENDER reviews and learns.</p>
</div>
<divclass="admonition tip">
<pclass="admonition-title">The Power of Context</p>
<p>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><br/>
- Enable rapid context switching without confusion<br>
- Build empathy by experiencing multiple perspectives<br></p>
</div>
<p><strong>Learning the Dance</strong>
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.</p>
<p>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</p>
</div>
<h3id="the-meta-transparency-layer-adm-between-groups">The Meta-Transparency Layer: ADM Between Groups<aclass="headerlink"href="#the-meta-transparency-layer-adm-between-groups"title="Permanent link">¶</a></h3>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>The <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr> 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.</p>
</div>
<p>We've seen how the <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr> works within each group. But the true power emerges when we see how it connects the groups themselves, creating what we call the <strong>meta-transparency layer</strong>—a complete chain of accountability from public oversight to task execution.</p>
<p>Each group in our 6-layer structure maintains oversight of the group below it through its own <abbrtitle="Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.">ADM Triangle</abbr>:</p>
<divclass="grid cards">
<ul>
<li>
<p><spanclass="twemoji lg middle"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M17.9 17.39c-.26-.8-1.01-1.39-1.9-1.39h-1v-3a1 1 0 0 0-1-1H8v-2h2a1 1 0 0 0 1-1V7h2a2 2 0 0 0 2-2v-.41a7.984 7.984 0 0 1 2.9 12.8M11 19.93c-3.95-.49-7-3.85-7-7.93 0-.62.08-1.22.21-1.79L9 15v1a2 2 0 0 0 2 2m1-16A10 10 0 0 0 2 12a10 10 0 0 0 10 10 10 10 0 0 0 10-10A10 10 0 0 0 12 2"/></svg></span><strong><abbrtitle="The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.">0_timeline</abbr> → General Forum</strong><br>
<strong>A</strong>: Citizens taking initiative with proposals/votes<br>
<strong>D</strong>: Leadership team ensuring quality moderation<br>
<strong>M</strong>: Bot documents everything to <abbrtitle="The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.">0_timeline</abbr><br>
<em>The outside world sees our governance in action</em></p>
<strong>A</strong>: <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> members taking initiative in teams<br>
<strong>D</strong>: <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> captains ensuring strategy/budgets<br>
<strong>M</strong>: Bot reports team health to <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr><br>
<strong>A</strong>: Peers taking initiative in skill areas<br>
<strong>D</strong>: <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> captain ensuring roles are filled<br>
<strong>M</strong>: Bot reports role coverage to Teams<br>
<strong>M</strong>: Bot reports objective progress to <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr><br>
<strong>M</strong>: Bot reports task status to <abbrtitle="Defined missions or sprints within Teams, breaking vision into actionable missions.">Objectives</abbr><br>
<p>Let's follow a decision from inception to execution:<br><br>
<strong>Day 1 - Citizen Initiative</strong>:<br>
In the General Forum, citizens (A) propose adding mesh networking to <abbrtitle="First pilot project of Smartup Zero—decentralized emergency citizen mesh network prototype.">ONLIFE</abbr>. Leadership team (D) facilitates discussion. Bot (M) publishes proposal to <abbrtitle="The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.">0_timeline</abbr>.<br><br>
<strong>Day 3 - Vote Passes</strong>:<br>
Colleagues in <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr> (A) volunteer to implement. Leadership team (D) ensures it fits OSBP. Bot (M) reports commitment to General Forum.<br><br>
<strong>Day 5 - <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> Forms</strong>:<br>
Dev team members (A) organize around mesh networking. <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> captain (D) allocates budget and strategy. Bot (M) reports team formation to <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr>.<br><br>
<strong>Day 7 - <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr> Activate</strong>:<br>
Backend peers (A) define mesh protocol skills needed. <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> captain (D) ensures roles are properly staffed. Bot (M) reports skill gaps to Teams.<br><br>
<strong>Day 10 - Objective Launches</strong>:<br>
Squad members (A) begin "Build Mesh Prototype" objective. Mission leader (D) coordinates resources. Bot (M) reports progress to <abbrtitle="Functional positions within Teams (e.g., Frontend Developer). Define skillset, tasks, and compensation.">Roles</abbr>.<br><br>
<strong>Day 12 - Tasks Execute</strong>:<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>
<strong>Result</strong>: Complete transparency from public proposal to code commit. Every stakeholder can trace the path.</p>
<p>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.</p>
<h2id="the-official-smartup-business-plan-osbp"><spanclass="twemoji"><svgxmlns="http://www.w3.org/2000/svg"viewBox="0 0 24 24"><pathd="M4 4v18h16v2H4c-1.1 0-2-.9-2-2V4zm11 3h5.5L15 1.5zM8 0h8l6 6v12c0 1.11-.89 2-2 2H8a2 2 0 0 1-2-2V2c0-1.11.89-2 2-2m9 16v-2H8v2zm3-4v-2H8v2z"/></svg></span> The <abbrtitle="Living document recording strategy, decisions, assessments, and design. Transparent to all owners.">Official Smartup Business Plan</abbr> (OSBP)<aclass="headerlink"href="#the-official-smartup-business-plan-osbp"title="Permanent link">¶</a></h2>
<divclass="admonition info">
<pclass="admonition-title">What is this?</p>
<p>The OSBP is the living, breathing constitution of a <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr>—where an entrepreneur's vision transforms into collective property through democratic participation and continuous evolution.</p>
</div>
<h3id="from-my-idea-to-our-mission">From "My Idea" to "Our Mission"<aclass="headerlink"href="#from-my-idea-to-our-mission"title="Permanent link">¶</a></h3>
<p>Every <abbrtitle="A digital cooperative that builds tools for resilience and SDG advancement through trustworthy collective systems.">Smartup</abbr> 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.</p>
<p>The democratic grounding is the entrepreneur's ultimate reality check:</p>
<divclass="admonition quote">
<pclass="admonition-title">From 'I Think' to 'We Know'</p>
<p>"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."</p>
</div>
<p>This democratic grounding happens through:<br>
- <strong>Crowdfunding success</strong>: People vote with their wallets<br>
- <strong><abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> formation</strong>: Skilled people volunteer their time<br>
- <strong>Owner recruitment</strong>: Citizens join the mission<br>
- <strong>Financial thresholds</strong>: Real money proves real demand<br>
- <strong>Active participation</strong>: Not just watchers but builders<br></p>
<p>By the end of validation, we don't guess there's demand—we've proven it through collective action.</p>
<h3id="osbp-structure-for-validation-phase">OSBP Structure for Validation Phase<aclass="headerlink"href="#osbp-structure-for-validation-phase"title="Permanent link">¶</a></h3>
<p>The OSBP sections map directly to team responsibilities:</p>
<table>
<thead>
<tr>
<th>Section</th>
<th>Responsible <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr></th>
<th>Core Questions</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>1. Executive Summary</strong></td>
<td><abbrtitle="Strategic core of Smartup creation phases. Composed of all Team Captains and the initiating entrepreneur.">Leadership Team</abbr></td>
<td>Why does the world need this? What's our vision?</td>
</tr>
<tr>
<td><strong>2. Design Blueprint</strong></td>
<td><abbrtitle="Handles UX, interface, branding, prototyping, and design blueprints. Works closely with Development and Science Teams.">Design Team</abbr></td>
<td>How will it work from user perspective?</td>
</tr>
<tr>
<td><strong>3. Development Blueprint</strong></td>
<td><abbrtitle="Technical core of the Smartup. Builds and tests product or service (frontend, backend, security, QA).">Development Team</abbr></td>
<td>How do we build it? What's been built?</td>
</tr>
<tr>
<td><strong>4. Business & Marketing</strong></td>
<td><abbrtitle="Team responsible for business strategy, marketing, financial planning, and the Official Smartup Business Plan (OSBP).">Business Team</abbr></td>
<td>How does it sustain itself? Validation budget?</td>
</tr>
<tr>
<td><strong>5. Media & Message</strong></td>
<td><abbrtitle="Handles internal reporting, public relations, social media, and storytelling to keep the community informed.">Media Team</abbr></td>
<td>How do we communicate? What's our voice?</td>
</tr>
<tr>
<td><strong>6. R&D Roadmap</strong></td>
<td><abbrtitle="Provides scientific oversight, peer review, and sustainability validation. Can halt advancement if standards aren't met.">Science Team</abbr></td>
<td>What research questions must we answer?</td>
</tr>
<tr>
<td><strong>7. Definition of Ready</strong></td>
<td><abbrtitle="Manages processes between teams, incident management, compliance, documentation, and learning.">Operational Team</abbr></td>
<td>When are we ready for Design Phase?</td>
</tr>
</tbody>
</table>
<h3id="the-living-document-process">The Living Document Process<aclass="headerlink"href="#the-living-document-process"title="Permanent link">¶</a></h3>
<p><strong>Day 1</strong>: Design team improves user flow section<br>
<strong>Day 2</strong>: <abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> captain submits changes to <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr><br>
<strong>Day 2-5</strong>: Lazy consensus period (72 hours)<br>
- No objections from 3+ colleagues = proceed<br>
- Objections = discussion and resolution<br>
<strong>Day 5-7</strong>: General Forum notification (48 hours)<br>
- Final chance for any owner to raise concerns<br>
<strong>Day 7</strong>: Auto-published to live OSBP on <abbrtitle="The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.">0_timeline</abbr><br></p>
<td><abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> assessments added</td>
<td>Collective shaping and ownership</td>
</tr>
<tr>
<td><strong>v1.0</strong></td>
<td>Design entry</td>
<td>Validated plan</td>
<td>Community approved, ready to design</td>
</tr>
<tr>
<td><strong>v2.0</strong></td>
<td>Production entry</td>
<td>Designed solution</td>
<td>Blueprints complete, ready to build</td>
</tr>
<tr>
<td><strong>v3.0</strong></td>
<td>Organization entry</td>
<td>Built product</td>
<td>MVP done, ready to organize</td>
</tr>
<tr>
<td><strong>v4.0</strong></td>
<td>Market entry</td>
<td>Launch ready</td>
<td>Complete plan for sustainable operation</td>
</tr>
</tbody>
</table>
<h3id="from-assessment-to-leadership">From Assessment to Leadership<aclass="headerlink"href="#from-assessment-to-leadership"title="Permanent link">¶</a></h3>
<p>The OSBP naturally identifies leaders through work:</p>
<ol>
<li><strong>Teams collaborate</strong> on their OSBP section</li>
<li><strong>Quality contributors emerge</strong> through the writing</li>
<li><strong><abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> elects captain</strong> based on demonstrated ability</li>
<li><strong>Captains form</strong><abbrtitle="Strategic core of Smartup creation phases. Composed of all Team Captains and the initiating entrepreneur.">Leadership Team</abbr></li>
</ol>
<divclass="admonition warning">
<pclass="admonition-title">Not a Static Document</p>
<p>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.</p>
</div>
<h3id="access-and-transparency">Access and Transparency<aclass="headerlink"href="#access-and-transparency"title="Permanent link">¶</a></h3>
<p><strong>Where it lives</strong>:<br> Version controlled in Forgejo, rendered on <abbrtitle="The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.">0_timeline</abbr><br>
<strong>Who can read</strong>:<br> Everyone (public)<br>
<strong>Who can propose changes</strong>:<br><abbrtitle="Focused group of workers responsible for specific domains (e.g., Development, Design, Media, Business, Operations, Science).">Team</abbr> members for their sections<br>
<strong>Who approves</strong>:<br> Lazy consensus through <abbrtitle="The centralized collaboration platform where workers manage objectives and tasks.">Workplace</abbr> + Forum<br>
<strong>Update frequency</strong>:<br> Continuous as we learn<br></p>
<pclass="admonition-title">The Document That Binds Us</p>
<p>"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."</p>
Society Of Solutions is a global open cooperative running as an unincorporated alliance and transparently funded via <ahref="https://opencollective.com"target="_blank"rel="noopener">Open Collective</a>.
</p>
</div>
</footer>
</div>
<divclass="md-dialog"data-md-component="dialog">
<divclass="md-dialog__inner md-typeset"></div>
</div>
<scriptid="__config"type="application/json">{"base":"../..","features":["navigation.instant","navigation.sections","navigation.expand","content.hero","toggle","toc.follow","content.tooltips"],"search":"../../assets/javascripts/workers/search.d50fe291.min.js","tags":null,"translations":{"clipboard.copied":"Copied to clipboard","clipboard.copy":"Copy to clipboard","search.result.more.one":"1 more on this page","search.result.more.other":"# more on this page","search.result.none":"No matching documents","search.result.one":"1 matching document","search.result.other":"# matching documents","search.result.placeholder":"Type to start searching","search.result.term.missing":"Missing","select.version":"Select version"},"version":null}</script>
