CCOS: Consent-Based Governance

CCOS — a consent-based, role-distributed operating system — is a governance model designed to keep the good parts of modern self-management while removing the parts that reliably break down. It preserves role clarity and distributed authority, and it was built by studying exactly where its predecessors fail.

What it fixes in Holacracy

Holacracy was designed for knowledge-work companies, and in community and mission-driven settings it fails in characteristic ways:

• Constitution-worship. A long, rigid constitution gets treated as inviolable, so when reality does not fit the rules, people either break them secretly or enforce them at the cost of relationships.
• "You are not your role" dissonance. In a company this phrase is clarifying; among people who live and build closely together it creates cognitive dissonance, because people bring their whole selves.
• No care or conflict layer. Emotional harm and interpersonal conflict get classified as "operational" and effectively ignored by governance.
• Covert recentralization. Despite role distribution, power quietly re-accumulates on whoever sits at the center, often a founder or an anchor circle.

What it fixes in Sociocracy

Sociocracy is more humane but has its own failure modes:

• Multi-hour consent rounds. When consent slides into "check in with everyone's feelings," meetings run for hours.
• Double-link information clutter. The double-link structure creates confusing, duplicative information flow.
• Equivalence without accountability. Treating all voices as equivalent regardless of domain lets people without expertise block the experts.

Core principles

CCOS runs on five principles:

1. Role clarity over personality — accountability lives in roles, not personalities. "Who owns this?" means "which role owns this?"
2. Consent over consensus — a proposal proceeds when no one holds a valid objection, not when everyone is enthusiastic.
3. Tensions as signal — friction and unmet needs are surfaced in governance, not suppressed.
4. Transparency by default — decisions, roles, and assignments are visible unless explicitly restricted.
5. Evolutionary governance — roles, policies, and accountabilities change through proposals, not decree. Anyone can propose a change.

The valid-objection standard

Consent is not agreement, and it is not the absence of discomfort. An objection is valid only if it names a concrete way the proposal would prevent the objector from fulfilling their role's accountabilities — or would cause real, demonstrable harm to the circle. "I don't like it" is not a valid objection. "This would stop me from doing what my role is accountable for" is.

The working question is: good enough for now, safe enough to try? Governance is not the search for a perfect answer. It is the search for a decision that unblocks the work and can be revised later.

The four core roles

Every CCOS circle rests on four foundational roles:

• Lead Steward — sets circle priorities, assigns roles, and clears persistent blockers, without micromanaging or overriding a role holder's authority within their own domain.
• Rep Steward — carries the circle's tensions, needs, and decisions accurately into the wider organization, and brings context back. The circle's voice, going up and coming back.
• Admin Facilitator — holds the meeting process, records, and follow-through, staying neutral on content so the process stays trustworthy.
• AI Secretary (Sera) — records decisions, maintains role definitions and governance artifacts, and captures every governance action as a Draft, Candidate, or Pending record. Sera never approves, ratifies, or publishes anything; only humans complete consent.

The deep definitions of the three human roles — their values, requirements, and selection criteria — live in dedicated articles: Circle Lead Values, Circle Rep Values, and Admin Facilitator Values. Read those for the full picture rather than a summary here.

Key points

CCOS is a consent-based, role-distributed governance system that preserves role clarity and distributed authority while avoiding Holacracy failure modes (constitution-worship, you-are-not-your-role dissonance in communities, no care or conflict layer, power recentralizing on an anchor circle) and Sociocracy failure modes (multi-hour consent rounds, double-link information clutter, equivalence-without-accountability letting non-experts block experts). Core principles: role clarity over personality, consent over consensus, tensions as signal, transparency by default, evolutionary governance. A valid objection means it would prevent me from fulfilling my role accountabilities, not I do not like it; the test is good enough for now, safe enough to try. Four core roles: Lead Steward, Rep Steward, Admin Facilitator, and the AI Secretary (Sera). Deep role definitions live in the circle-lead-values, circle-rep-values, and admin-facilitator-values articles.