Skip to content

The Social Subsystem — Democratic Ownership

TL;DR

The social subsystem is the first of the three structural interventions tested in the Smartup Hypothesis. It replaces hierarchical management and concentrated ownership with a system where every contributor is an equal owner, authority is earned through service (Social Karma) rather than purchased with capital, and power decays monthly to prevent hoarding.

We are testing whether this distributed governance structure measurably improves a community’s self‑understanding and coordination—Engelbart’s indicators 4 and 8—by generating telemetry on authority concentration, decision participation, and proposal diversity.

🟡 Research Status: Working Hypothesis — Currently under test in Smartup Zero.

What We Are Testing

The Smartup Hypothesis proposes that three structural changes, working together, improve Collective IQ. The social subsystem is the first of those changes.

The core proposition:

If every contributor is an equal owner, and authority is earned through demonstrated community service rather than purchased with capital, then decision‑making will become more distributed, self‑understanding will improve, and coordination friction will decrease.

This is not an assumption. It is a testable claim. Smartup Zero is designed to generate the evidence that supports or refutes it.

The Social Intervention in Detail

What we changed:

  • Every contributor becomes an equal owner (Book of Owners, not shareholders)
  • One person, one vote — regardless of money contributed
  • No founders, no investors, no external shareholders
  • Ownership is tied to participation, not capital

Why this might improve CIQ:

When power is concentrated, the group’s self‑understanding (Indicator 4) is distorted—the org chart reflects wealth, not actual function. When ownership is genuinely shared, the group can see itself more clearly because authority maps to contribution, not money.

What we changed:

  • Authority is measured through Social Karma (SK) , not Smartup Credits (SC)
  • SK is earned through peer‑recognised community service
  • SK decays 10% monthly — power cannot be hoarded indefinitely
  • Thresholds require minimum SK: 50 to propose votes, 100 to run for captain, 200 for mission leader

Why this might improve CIQ:

When authority decays, no single person can accumulate permanent power. This forces continuous contribution and keeps decision‑making distributed. Coordination (Indicator 8) should improve because resources flow based on demonstrated service, not accumulated capital or tenure.

What we changed:

  • All governance rules are published in a public constitution
  • Changes require proposal → community vote → enactment
  • Leadership roles (captains) are elected and recallable
  • The Science Team holds veto power at phase gates

Why this might improve CIQ:

When rules are transparent and changeable only through democratic process, the group develops a clear understanding of its own decision‑making structure (Indicator 4). There is no ambiguity about who decides what, or how to change it.

What This Intervention Measures

Every social mechanism in Smartup Zero is instrumented to produce telemetry. The following metrics are extracted automatically from the ledger:

CIQ Indicator Metric Data Source What Improvement Looks Like
4. Self‑Understanding Authority Concentration Index book-of-owners.csv SK distribution over time Gini coefficient decreases (flatter distribution)
4. Self‑Understanding Decision Participation Rate master-events.csv governance actions More unique actors participate in decisions
4. Self‑Understanding Proposal Origin Diversity governance-actions.csv proposer aliases Proposals come from a wider range of contributors
8. Coordination Task Assessment Distribution session_logs.csv quality labels Higher percentage of tasks rated Excellent (27‑30)
8. Coordination Leadership Turnover Rate book-of-owners.csv captain election events Captains rotate as designed, no permanent incumbents

These metrics are pre‑registered in RFC‑004: Scientific Measurement. We cannot change what we measure after seeing the data.

The Six Groups of Productivity

To make governance, work, and ownership transparent and measurable, SmartupOS organises all activity into six nested groups. Each group maps to a specific structural layer, and each generates distinct telemetry.

Centered image

  • 1. General Forum

    The democratic core. All owners gather here to discuss, propose, vote, and oversee. Every voice is equal, every vote counts as one.

    Members: All Smartup owners (citizens)
    Telemetry: Vote participation, proposal diversity, deliberation depth

  • 2. Workplace

    The production layer. Owners with a work license coordinate execution. Here, democratic decisions become concrete action.

    Members: All workers (colleagues)
    Telemetry: Task throughput, cross‑team collaboration rate

  • 3. Teams

    Specialised units. Design, development, business, media, science, operational. Each team focuses effort on a specific domain.

    Members: Workers in the same team
    Telemetry: Team velocity, role coverage, skill distribution

  • 4. Roles

    How people contribute. Workers apply for roles matching their skills—attacker (senior), defender (junior), mission leader, captain.

    Members: Workers with the same role (peers)
    Telemetry: Role application rates, skill gap identification

  • 5. Objectives

    What needs to be achieved. Teams progress by completing specific, measurable objectives tied to the mission.

    Members: Workers on the same objective (squad)
    Telemetry: Objective completion rate, milestone achievement

  • 6. Tasks

    Where work happens. The smallest unit of productivity. Each task is a measurable contribution with a budget, an attacker, and a defender.

    Members: Assigned attacker + defender
    Telemetry: Task completion velocity, assessment scores, rework rate

The Nested Structure

Each group lives within the one above it: General Forum contains → Workplace → Teams → Roles → Objectives → Tasks. This nesting creates clear accountability chains while maintaining democratic oversight at every level. The structure itself generates the data that tells us whether power is distributing as designed.

The ADM Pattern — How Work Flows

At the core of Smartup Zero’s operational design is the Attacker‑Defender‑Midfielder (ADM) pattern. It governs every interaction—from task execution to phase‑gate decisions—and is the mechanism that forces collaboration and generates telemetry for Indicators 3 (Integration) and 8 (Coordination).

graph TD
    A[Attacker / Senior<br/><sub>Drives execution</sub>]
    D[Defender / Junior<br/><sub>Ensures quality, learns</sub>]
    M[Midfielder / Engelbot<br/><sub>Coordinates, logs, enforces rules</sub>]

    A <--> M
    D <--> M
    A -.->|Mentors| D

At every level of the organisation, work is structured as a triangle:

  • Attacker (executes): The person who drives the work forward—writes code, designs interfaces, drafts documents.
  • Defender (oversees): The person who reviews, learns, and ensures quality. In tasks, this is the junior role (10% SC). In governance, it is the oversight layer.
  • Midfielder (coordinates): Engelbot, the permanent middleware. It logs every action, enforces permission checks, and routes commands to the ledger.

The ADM pattern is not just an operational convenience. It is an experimental control:

  • Forces collaboration: No one works alone. Every task requires at least two people, ensuring diverse perspectives integrate.
  • Generates telemetry: Every attacker‑defender pairing, every assessment score, every iteration count is logged to the ledger.
  • Prevents power concentration: The defender role rotates. No single person can dominate a task lifecycle.
  • Enables measurement of Indicators 3 and 8: Contribution Velocity (how fast diverse capabilities integrate) and Task Assessment Distribution (how smoothly coordination happens) are direct outputs of the ADM structure.

When a task is completed and assessed:

  • The Attacker (senior) receives 90% of the Smartup Credit (SC) budget
  • The Defender (junior) receives 10%

This split is not about payment—it is an investment in developing future capability. Juniors learn by observing and assisting seniors. Over time, they accumulate enough skill and Social Karma to take on attacker roles themselves, increasing the group’s overall capability diversity (Indicator 3).

The Official Smartup Business Plan (OSBP)

The Experimental Protocol

The OSBP is the living document that records the experiment’s design, progress, and evidence. It is not a pitch deck for investors—it is a scientific protocol that any researcher can read to understand what is being tested, how, and what the results are.

From Hypothesis to Protocol

The OSBP evolves through each phase of the experiment, growing more detailed as evidence accumulates:

flowchart LR
    H["Smartup Hypothesis<br/>v0.1"] --> PV["Pre‑Validation<br/>Lab setup, baselines"]
    PV --> V["Validation Phase<br/>OSBP v1.0 — concept proven"]
    V --> D["Design Phase<br/>OSBP v2.0 — blueprints validated"]
    D --> P["Production Phase<br/>OSBP v3.0 — MVP tested"]
    P --> O["Organization Phase<br/>OSBP v4.0 — sustainable model"]

    style H fill:#ffb300,stroke:#333,stroke-width:2px,color:#000
    style O fill:#8bc34a,stroke:#333,stroke-width:2px,color:#000

OSBP Structure

Section Responsible Team What It Documents
1. Executive Summary Leadership Team Research question, hypothesis, current phase
2. Design Blueprint Design Team User experience and interface design
3. Development Blueprint Development Team Technical architecture and implementation
4. Business Blueprint Business Team Funding model, treasury health, sustainability
5. Media Blueprint Media Team Public communication and narrative
6. Science Blueprint Science Team Research questions, methodology, evidence
7. Operational Blueprint Operational Team Workflows, tools, constitutional enforcement

Living Document Process

Updates to the OSBP follow a democratic review process:

  1. 72‑hour Lazy Consensus in the Workplace — proposed changes are open for review
  2. 48‑hour General Forum notification — all owners are informed
  3. Auto‑published to timeline0.org — the public always sees the current state

This process ensures that the experimental protocol is always current, always public, and always democratically validated.

Progressive Transparency Architecture

Controlled Variables in the Experiment

Smartup Zero does not operate with total secrecy or naive openness. It uses Progressive Transparency—a tiered access system where information is revealed as contributors earn trust through demonstrated service. This is an experimental control: it ensures that the people making governance decisions are genuinely participating in the community.

The Three‑Tier Information System

Tier Access Contents Who
Tier 1: Public 1_general_forum OSBP, Book of Owners, currency ledger, voting outcomes The world
Tier 2: Contributor 2_workplace and team repos Implementation code, active workflows, work‑in‑progress Work & Campaign license holders
Tier 3: Governance Captain‑only channels Cross‑team coordination, partnership negotiations Team Captains & Founder

Why This Matters for the Experiment

Progressive transparency is not a privacy policy. It is a variable we control. By tiering access, we can observe whether transparency—earned through participation—actually improves trust, coordination, and self‑understanding. If everyone could see everything without contributing, we could not distinguish between transparency that empowers and transparency that overwhelms.

The Oversight Cascade — ADM Between Groups

The ADM pattern does not only operate within tasks. It connects every layer of the organisation, creating a complete chain of accountability from public oversight to individual task execution.

Layer Relationship Attacker Defender Midfielder What This Measures
Public → General Forum Citizens proposing, voting Leadership Team moderating Engelbot publishes to timeline0.org Democratic participation (Ind. 4)
General Forum → Workplace Colleagues executing work Leadership ensuring OSBP alignment Engelbot reports progress Strategic consistency (Ind. 7)
Workplace → Teams Team members organising Team Captains managing budgets Engelbot reports team health Resource allocation (Ind. 8)
Teams → Roles Peers developing skills Team Captains staffing roles Engelbot reports gaps Capability diversity (Ind. 3)
Roles → Objectives Squad members executing Mission Leaders coordinating Engelbot reports progress Plan effectiveness (Ind. 7)
Objectives → Tasks Attacker executing Defender reviewing Engelbot logs sessions Coordination (Ind. 8), Learning (Ind. 1)

This cascade is the structural guarantee that every action in Smartup Zero is observed, logged, and measurable—without surveys, without self‑reporting, and without relying on anyone’s memory.

Next: The Technical Subsystem

The social subsystem establishes democratic ownership and earned authority. But democratic governance without institutional memory is theatre—decisions are made, then forgotten.

The technical subsystem explains how SmartupOS creates permanent, searchable, shared memory that forces learning to compound.

Read The Technical Subsystem

Ways to Participate

  • Join Smartup Zero

    Become an participant in the first experiment.

    Explore

  • Start Your Own Smartup

    Take SmartupOS and run your own experiment.

    Learn How

  • Sponsor the Research

    Support Timeline0 and Smartup Zero through funding.

    Contribute

  • Collaborate as Researcher

    Work on the research programme itself.

    Get in Touch