The Governance Stack

Abstract

Every cooperative faces the same accusation: you can’t be democratic and fast. The evidence used to support this claim is real. The 6.3% average voter participation in DAOs. The cooperative board meetings where nothing gets decided. The worker-owned businesses that move at a glacial pace while competitors adapt and grow. Pure democracy is a speed tax. This much is true.

But the conclusion drawn from it is wrong.

Cooperatives and DAOs alike apply democratic process to every decision, when most decisions don’t need democracy at all. They need expertise, or speed, or a single person with clear authority and clear scope. Democracy is the right process for a narrow category of decisions. Applied everywhere, it produces either paralysis or apathy.

This paper describes a governance architecture that routes decisions to the right process. It calls this architecture the governance stack: three layers, each optimized for a different category of decision, all operating simultaneously, all accountable to the same cooperative principles. The architecture draws from five governance traditions: sociocracy, holacracy, Ostrom’s polycentric governance, Falkvinge’s swarmwise model, and Brafman and Beckstrom’s starfish/spider framework. Each has a piece of the answer. The stack assembles the pieces.

This is the fourth paper in R3SET’s series on cooperative economics. The first three established the ownership structure (Paper 1: “The Ownership Cure”), the economics of emergence (Paper 2: “Synergistic Commerce”), and the financial infrastructure (Paper 3: “The Community Mint”). The governance stack is the operating system that runs on top of all of it.

Part I: The Speed Problem

Name it honestly.

Pure democracy is slow. Not slow like careful deliberation is slow, where you take time because the stakes warrant it. Slow like gridlock is slow. The mechanism itself imposes a cost that scales with group size, and that cost compounds until the mechanism collapses.

A Harvard Business School study examining 2,988 governance proposals across 10 major blockchain protocols found that average voter participation sits at 6.3%. Uniswap has over one million token holders. A typical governance vote attracts fewer than ten thousand participants. The ENS DAO centralization analysis from 2024 found that a handful of wallets controlled the majority of governance outcomes across most major protocols. This is not voter apathy. It is rational behavior in a broken system. Most token holders have no relevant expertise on most proposals. Asking them to vote anyway produces two outcomes: they don’t vote, or they vote badly. Both are failures of governance design, not failures of the people.

Cooperatives without blockchains have felt this for decades. They just didn’t have on-chain data to quantify it. The 1995 Cornforth study found that once a cooperative reaches 15 to 20 members, a high degree of democratic involvement can only be maintained by developing a more complex democratic structure. Most cooperatives never build that structure. They keep running everything through full-membership consent as the organization grows. The cost accumulates invisibly until it either drives out the people who do the work or concentrates real power in an informal elite that operates outside the democratic structure entirely.

The swarm model has a different version of the same problem. Rick Falkvinge built the Swedish Pirate Party to 50,000 members and 18,000 active activists using pure swarm principles, won more than 7% of the Swedish vote in the 2009 European Parliament election, and then watched the party fall below 1.4% in the 2010 general election. Swarm organizations excel at mobilization. They fail at sustained governance because they have no economic engine, no accountability structure, and no legitimate decision-making process for multi-stakeholder disputes. The energy that builds a swarm is not the same energy that runs an institution over years.

And autocracy, the most common “solution” to the speed problem, concentrates power and reproduces extraction. Cooperatives exist because autocratic governance failed communities. Trading democratic slowness for executive speed by putting control in the hands of one person or a small group is not a fix. It is the problem wearing different clothes.

The problem is routing, not democracy.

Here is what the data actually shows: organizations that are 30% faster at addressing inefficiency report 16% higher profit growth opportunity, according to Orgvue’s 2020 research. The organizations achieving that speed are not doing it by abandoning democratic governance. They are doing it by routing different decisions to different processes, each optimized for its type.

Buurtzorg, the Dutch nursing organization with 12,000 nurses across 24 countries, runs on self-managing teams of 10 to 12 people. Each team governs itself. No managers. No approval chains. The back office that supports the entire network is 45 to 50 people. Overhead is 8% versus the industry average of 25%. The organization is simultaneously more democratic and faster than the hierarchical institutions it competes with. The KPMG study from 2015 found Buurtzorg used 40% fewer hours of authorized patient care while achieving better outcomes.

Buurtzorg did not solve the speed-vs-democracy tradeoff. It dissolved it by asking a different question: which decisions belong to the team, which belong to the organization, and which belong to nobody, because they don’t need to be decided at all?

The governance stack is the answer to that question, built on 50 years of evidence from five different governance traditions.

Part II: Five Traditions, One Problem

What each tradition got right. What each one missed.

The governance stack is not invented. It is assembled. Five governance traditions have been working on the same problem from different angles for decades. The stack integrates their best insights while discarding what failed.

Sociocracy: Endenburg’s consent insight.

Gerard Endenburg was a Dutch electrical engineer who inherited his family’s company in 1970 and spent a decade turning it into a governance laboratory. He based his approach on cybernetics, the science of steering and feedback, combined with the egalitarian practice of the Quaker school he had attended as a child. What emerged was the Sociocratic Circle-Organization Method: four principles operating together. Consent decision-making. Circle organization. Double-linking. Elections by consent.

The consent insight is the most important. Everyone has preferences (what they ideally want) and a range of tolerance (what they can live with). Consensus seeks the overlap of preferences. Consent seeks the overlap of tolerances, which is a much larger space. “The area of overlap between ‘no objection’ is considerably bigger than the overlap between personal preferences.” The decision standard is not “do you agree?” It is “can you live with this? Is this good enough for now, safe enough to try?”

This makes consent faster than consensus without sacrificing inclusion. Every voice is heard. Every objection is integrated. Nobody gets steamrolled. But the bar is not unanimous agreement. It is the absence of reasoned objection. That is a bar most groups can clear much faster than consensus requires.

Dutch companies using sociocracy are exempt from labor laws requiring works councils, because the government recognizes that workers are already represented daily through the sociocratic process. Endenburg Electric operated sociocratically for 25 years and remained competitive throughout. Ternary Software, an early sociocracy adopter, grew revenue 38% in one year and an average of 50% per year over three years.

What sociocracy left underspecified: the operational layer. Who decides what when there’s no circle meeting? Consent processes work for policy. They are overkill for “should we use Postgres or SQLite.”

Holacracy: Robertson’s role clarity.

Brian Robertson built holacracy from sociocratic foundations starting in 2006, driven by a specific frustration: sociocracy’s consent threshold left room for personal concerns to infiltrate organizational governance. His innovation was explicit criteria for what counts as a valid objection, removing preference-based blocking from the process.

Holacracy’s genuine contribution is role authority. In holacracy, authority attaches to roles, not people. Roles have defined purposes, accountabilities, and domains. A person in a role does not need permission to act within that role’s scope. They act, then report. This creates real-time operational speed while maintaining governance accountability. The tension-processing mechanism gives every role-holder a clear path to escalate organizational problems into governance changes. No tension accumulates until it explodes. It gets processed.

What holacracy got wrong was complexity and rigidity. Zappos tried to implement holacracy across 1,500 employees and lost 18% of its workforce when 260 people took the buyout. Annualized turnover stabilized around 14%. The company fell off Fortune’s 100 Best Companies to Work For list for the first time in eight years. Medium adopted holacracy in 2013 and abandoned it in 2016, citing three specific failures: coordination across functions was “time-consuming and divisive,” codifying responsibilities in explicit detail “hindered a proactive attitude and sense of communal ownership,” and the system created perception problems in recruiting. Medium described it as “a small but persistent tax on both our effectiveness, and our sense of connection to each other.”

The lesson is not that role authority fails. It is that role authority fails when it is implemented through a rigid constitution at scale, without cultural preparation, and without democratic accountability. The governance stack takes the role authority insight from holacracy and grounds it in a consent-based democratic structure.

Ostrom’s polycentric governance: the theoretical foundation.

Elinor Ostrom won the Nobel Prize in Economics in 2009 for a body of work that demolished a 40-year assumption. Hardin’s “tragedy of the commons” claimed that shared resources were inevitably destroyed through individual self-interest, and that the solution was either privatization or state control. Ostrom’s empirical research showed that communities had been solving collective-action problems without markets or states for centuries, and that their solutions consistently outperformed both market and government alternatives.

Her Nepal irrigation systems study is the clearest evidence. Of 12 government-managed systems, 40% had high performance. Of 25 farmer-managed systems, over 70% had high performance. Farmer-governed systems grew more rice, distributed water more equitably, and kept their infrastructure in better repair. The finding held across 229 systems in an expanded dataset. “Not a single case was found where a large centralized police department outperformed smaller departments serving similar neighborhoods.”

Ostrom’s eighth design principle is the theoretical spine of the governance stack: nested enterprises. “Every sphere of activity has an optimal scale. Large-scale governance requires finding the optimal scale for each sphere of activity and appropriately coordinating the activities.” Governance is not a single layer. It is a stack of nested circles, each with its own appropriate scale, connected by well-designed coordination mechanisms.

Her institutional diversity argument is equally important: there is no single optimal governance structure. Different types of decisions require different governance mechanisms. The appropriate mechanism depends on the nature of the decision, the scale of the decision, the level of trust among participants, and the degree of interdependence with other systems. This is not relativism. It is the empirical finding of 30 years of field research.

Falkvinge’s swarmwise model: mobilization intelligence.

Rick Falkvinge built a political party from nothing to 50,000 members and 7% of the Swedish vote in three years using a governance model that had no precedent in political organizing. The core insight: in networks, the cognitive cost of decision-making scales faster than group size, so the only way to stay fast is to push authority all the way to the edge.

The three-person rule is the operational expression of this: if three activists agree an action is good for the organization, they have full authority to act in its name. Not permission to ask. Authority to act. The ban on seeking permission is as important as the grant of authority. Falkvinge put it plainly: “Their own judgment was the best available in the organization for their own social context, and they were required to use that judgment rather than aspiring to hide behind somebody else’s greenlighting.”

The magic group sizes, 7, 30, and 150, are Falkvinge’s distillation of Dunbar’s research into operational design. A group of 7 has 21 relationships to maintain. A group of 9 has 36. The cognitive overhead compounds faster than the group’s capacity. Seven is the maximum for tight coordination without structural friction.

What the swarm model lacks: an economic engine, sustainability mechanisms, and governance accountability over time. The Swedish Pirate Party’s collapse after 2009 is not a failure of the swarm principles for mobilization. It is a failure of the swarm principles for sustained institutional governance. “The driving force toward creating a more conventional organizational structure was the party’s youth branch... which set up an organization much more similar to other parties.” The swarm is an input to the governance stack, not a replacement for it.

Brafman and Beckstrom: the hybrid sweet spot.

Ori Brafman and Rod Beckstrom’s 2006 book drew the distinction between spider organizations, where cutting off the head kills the organization, and starfish organizations, where each arm carries the full genetic code and the organization can regenerate from any part. The Apache nation, AA, Wikipedia, Craigslist. The decentralized organization is harder to defeat, faster to adapt, and more resilient to attack.

Their most important strategic insight is the sweet spot: neither pure spider nor pure starfish. eBay hosts the marketplace centrally but lets user-to-user transactions and community self-policing through ratings operate as a peer system. Toyota sets centralized strategic direction but distributes production decisions through kaizen. McChrystal’s Joint Special Operations Command went from 4 raids per month to 300 raids per month by building networked small teams with shared consciousness and distributed authority: a 75-fold improvement in operational tempo.

The Cow Principle is the governance stack’s structural argument against transferable governance tokens. The Spanish couldn’t defeat the Apaches militarily for generations. What defeated them was giving Apache leaders cattle. Once the Nant’ans, who had been spiritual leaders with no property, had something to protect, they became centralized around that property. Then they could be conquered. The moment governance becomes property that can be accumulated and transferred, the starfish becomes a spider. Non-transferable governance tokens are the structural defense against this failure mode.

Part III: The Governance Stack

Three layers. Each optimized for its category of decision.

The governance stack is a routing system. It identifies three categories of decision and routes each to the governance process optimized for it.

Layer 1: Constitutional. Democratic. Slow by design.

Existential questions belong here. Who can be a member. How surplus is distributed. What the mission is. Whether to merge or dissolve. Bylaw changes. These decisions affect everyone’s ownership and rights. They require the fullest democratic participation and the most deliberate process.

Every member gets one vote. The governance token carries exactly one democratic weight at this layer, regardless of contribution level. No accumulation. No proportionality. One person, one voice.

The decision process is consent, not consensus or majority vote. A proposal passes when no member raises a reasoned objection. “Can you live with this?” replaces “Do you agree?” The objector must articulate why the proposal would harm the organization, not just express a preference against it. Personal disagreement is not a valid organizational objection. This keeps the process from being captured by chronic objectors while ensuring that serious concerns have full voice.

Constitutional decisions happen quarterly or annually. The deliberate slowness is a feature. These are not decisions that need to be made in a meeting. They are decisions that need to be right. The Community Mint’s contribution decay mechanism ensures that dormant members don’t accumulate indefinite veto power over an organization they’ve left in practice but not on paper. Active membership is the condition for constitutional voice.

Layer 2: Strategic. Domain circles. Medium speed.

Product roadmap. Budget allocation. Partnerships. Hiring. Market positioning. These decisions require expertise, context, and accountability. They don’t require input from every member of the organization. They require input from the people who actually know the domain.

Sociocratic circles govern here. Five domains map to R3SET’s actual structure: technology (M3SH, SP3AK EASY, EL3VATE, MARK3T), community engagement (ID3A Jams, Blackshires), finance (Profit First accounts, cooperative surplus), education (R3SET Academy, EL3VATE), and commerce (MARK3T, community stablecoin, community currency). Each circle has semi-autonomous authority over its domain. It does not need permission from the full membership to act within its scope.

Governance weight at this layer is contribution-weighted, not equal. The governance token carries domain weight proportional to patronage in that specific area. A member who has contributed 2,000 hours to platform development carries more governance weight in the technology circle than a member who joined last month. This is not plutocracy. Plutocracy is purchasing power. This is earned competence: weight proportional to demonstrated participation in the domain being governed.

Circles are connected by double-linking. Each circle sends an elected delegate upward to the general circle. The general circle appoints a lead downward to each domain circle. Both sit as full members in each other’s meetings. Information flows in both directions. No circle can be overruled by a higher circle without going through the people who represent that lower circle at the higher level. The double-link is a structural feedback loop that prevents hierarchical capture.

Five to twelve people who know their domain make better domain decisions than five hundred people voting on something they don’t understand. The strategic layer moves weekly or monthly.

Layer 3: Operational. Role authority. Real-time.

This is where 90% or more of decisions actually happen. A developer choosing a technical approach. A facilitator designing a session format. A community organizer deciding how to run the room. These decisions don’t need a vote. They need a person with clear authority and clear scope.

Holacracy’s role authority principle governs here, stripped of the complexity overhead that sank Zappos. Within a circle, individual roles have defined purposes, accountabilities, and domains. A person in a role acts within that scope without asking permission. They act, then report. The tension-processing mechanism gives every role-holder a path to escalate: when you hit the limits of your role authority, bring the tension to the circle. The circle processes it by consent. If it exceeds the circle’s scope, it escalates to the constitutional layer.

Subsidiarity governs the whole thing: decisions at the lowest level capable of handling them. The operational layer handles the vast majority of decisions. Escalation is the exception, not the rule.

The decision routing table.

Table scrolls sideways →

The routing table is what makes the stack work. Without it, every decision defaults to the process the organization defaults to: usually either full-membership democracy (slow, regardless of decision type) or informal authority (fast, unaccountable). The routing table matches the process to the decision.

Part IV: The Token Architecture

How the governance token encodes all three layers.

The governance token from Paper 3 (The Community Mint) is not a simple voting credential. It carries two separate weights, routing automatically based on the decision type.

The democratic weight is one per member, equal, regardless of contribution level. This is what every member receives when they join the cooperative through N3TWORK. It is non-transferable, permanently tied to verified identity, and carries full constitutional voice. It is the operative expression of one-person-one-vote at the cooperative’s foundational layer.

The domain weight is proportional to contribution within a specific circle. The Slicing Pie patronage tracking system already measures this. The governance token already carries the data. The smart contract reads the decision type, checks which circle the decision belongs to, and applies the domain weight of members in that circle to the consent process.

Operational decisions require no token at all. Role authority is granted through the circle’s governance process, not through a vote. The role itself is the governance mechanism.

Contribution decay prevents accumulation of governance power by inactive members. Governance weight is not a permanent historical ledger. It reflects current and recent participation. A founding member who has been absent for three years does not carry more constitutional voice than a new member who has been active for six months. The decay rate is set by the cooperative’s bylaws through the constitutional process.

The Cow Principle is why all of this is non-transferable. The moment governance tokens can be purchased or transferred, they become property. Property can be accumulated. Accumulated property produces concentration. Concentration produces extraction. The cooperative structure, the non-transferable token, the contribution-based weight, the decay mechanism: all of it is designed to prevent the starfish from becoming a spider.

Part V: Group Size and Network Design

Humans are wired for specific group sizes. The governance stack is built around them.

Robin Dunbar’s research established that the number 150 is not a cultural artifact. It appears in hunter-gatherer societies, 11th-century English villages, modern corporate offices, military organizations, and Facebook friend networks (a dataset of 61 million pages showed an average friend count of exactly 149). The neocortex, the part of the brain associated with cognition and language, has a direct ratio relationship with the size of cohesive social groups humans can maintain.

But 150 is not the only number. Dunbar’s complete framework reveals a fractal series of nested layers, each approximately three times the size of the one below.

Table scrolls sideways →

The governance stack is built around these layers. The operational layer operates at 5 to 7 (Falkvinge’s working group limit, grounded in the same cognitive science). The strategic layer operates at 5 to 12 per circle (the research-optimal size for collaborative decision-making). The constitutional layer operates at 150 and below for direct participation; beyond that, it requires representative structures.

The organizations that figured this out independently all converged on the same design. Buurtzorg caps every nursing team at 12 and requires the team to split before it grows larger. The mandate is structural, not advisory. When a team hits the limit, it splits. W.L. Gore caps every facility at approximately 150 people. When a plant approaches that number, the company builds a new factory rather than expanding the existing one. “Gore accepts duplication costs as worthwhile for maintaining social cohesion.” Mondragon’s cooperative congress has 650 elected representatives governing a $11 billion enterprise across 70,000 workers: a representative structure that preserves democratic accountability without requiring every worker to attend the same meeting.

McChrystal’s transformation of the Joint Special Operations Command is the operational proof. In 2003, JSOC was conducting roughly 4 raids per month. By building networked small teams with shared consciousness and distributed execution authority, the organization reached 300 raids per month: a 75-fold improvement. The small teams didn’t get bigger. They got better connected and more trusted to act. Shared consciousness replaced centralized control. Empowered execution replaced approval chains.

The governance stack is the cooperative-sector implementation of that same architecture. It doesn’t require a military budget. It requires a shared vocabulary and the discipline to hold the structure.

Part VI: The Tyranny of Structurelessness

Jo Freeman wrote the warning in 1972. Nobody in the cooperative movement has fully answered it yet.

Jo Freeman published “The Tyranny of Structurelessness” in 1972 based on her experience in the women’s liberation movement. The essay has been continuously reprinted and cited for over 50 years because the problem it describes never went away.

The central argument: unstructured groups are not actually structureless. They always have an informal structure, based on friendships, personal connections, shared history, and charisma. “Structurelessness becomes a way of masking power, and within the women’s movement it is usually most strongly advocated by those who are the most powerful, whether they are conscious of their power or not.”

The informal structure is not benign. Freeman identified seven mechanisms by which informal power structures emerge in ostensibly flat organizations: the formation of informal friendship networks as decision-making units; the development of communication channels that exclude some members; the lack of criteria for judging performance or accomplishment; the use of personal loyalty as the basis for assignment to critical tasks; the concentration of skills in a small elite by accident of circumstance; the differential in information access between members; and the dependency of the whole group on a few people who have the will and capacity to act.

The modern examples are everywhere. Valve’s flat structure, famously described as “no managers, no bosses,” contains, as former employees have documented, a hidden layer of powerful management: senior employees who exercise substantial informal power based on tenure and proximity to Gabe Newell. The Occupy movement, built on the explicit rejection of hierarchy, reproduced hierarchies of charisma, connection, and meeting attendance. Every “leaderless” organization studied under Freeman’s lens has leaders. They just don’t have accountability.

Sociocracy’s formal structure is a direct answer to Freeman’s critique. Making authority explicit through domains eliminates ambiguity about who decides what. Electing roles by consent through open nomination makes leadership visible and accountable. Double-linking creates bidirectional information flow that prevents any single person from controlling the connection between layers. Consent rights for all circle members means nobody can be steamrolled by informal influence. Transparent decision records mean there are no backroom deals.

The governance token extends this transparency to the financial layer. Contribution history is on-chain. Governance weight is calculated automatically and publicly. Power is not hidden. It is proportional, auditable, and subject to the decay mechanism that ensures it reflects current engagement rather than historical position.

This sounds counterintuitive until you understand what Freeman actually showed: the absence of formal structure does not produce equality. It produces informal hierarchy, unaccountable to anyone. The governance stack is the answer to the tyranny of structurelessness. It makes power visible, bounded, and earned.

That is the point. Not just that power exists, but that everyone can see it, trace it, and contest it through a legitimate process.

Part VII: How This Maps to R3SET

The governance stack is not abstract. It runs on R3SET’s actual infrastructure, through R3SET’s actual domains.

N3TWORK is the identity and governance layer. This is where governance tokens live. When a member joins through N3TWORK, they receive their non-transferable governance token tied to verified identity. Their contribution history accumulates transparently. Their patronage weight in each domain circle is calculated automatically. N3TWORK becomes the governance infrastructure for the entire cooperative ecosystem, not just a product platform.

The five domain circles map directly to R3SET’s operating reality.

• Technology circleGoverns M3SH, SP3AK EASY, EL3VATE, and MARK3T: product roadmap, technical architecture, platform decisions. Weight is proportional to platform development contribution, measured through the Slicing Pie system already tracking this.
• Community engagement circleGoverns ID3A Jams and partnerships: facilitation methodology, community partnerships, field operations. Weight is proportional to direct community engagement hours.
• Finance circleGoverns Profit First account allocation and cooperative surplus distribution: the decision about how much goes to operating expenses, owner’s pay, taxes, and the community transformation reserve. This is not the CEO’s call. It is a circle decision, made by the people who understand the cooperative’s financial realities.
• Education circleGoverns R3SET Academy and EL3VATE: curriculum development, instructor credentialing, learning design. Weight is proportional to educational content development and delivery.
• Commerce circleGoverns MARK3T, the community stablecoin, and community currency: marketplace rules, pricing mechanisms, currency circulation design. Weight is proportional to commerce infrastructure development and operations.

The swarmwise integration document maps directly to the stack’s structure. The core circle of 7 is the general governance circle: the people doing active governance work, holding the double-link positions between domain circles. The chapter leads of 30 are the domain circle delegates: the people representing each circle upward and connecting the stack horizontally. The community nodes of 150 are the active cooperative membership: the full constitutional electorate. The broader movement beyond 150 is what Falkvinge called the swarm: people who align with the mission and contribute what they can, without the formal membership structure of the inner circles.

Part VIII: From Stack to Movement

The governance stack is open. Any cooperative can adopt it.

The degeneration thesis, associated with Cornforth, Webb, and Luxemburg, says cooperatives become less democratic as they grow. The evidence supporting this is real: competitive market pressure forces adoption of capitalist logics; individual member input is diluted by centralized oligarchic decision-making; informal elites develop who are unacknowledged and therefore unaccountable. The cooperative movement has been watching this happen to its own organizations for over a century.

The counter-evidence is also real. Cornforth’s 1995 study found that three of the four cooperatives he studied were successfully negotiating their growth without compromising democratic principles. The critical countermeasure they all used: job rotation to democratize expertise, combined with more complex democratic structures that combined representative and direct forms at different scales. The governance stack is the formalized, token-supported version of that countermeasure.

Digital tools make the stack operable at scale. Loomio, the worker cooperative from New Zealand that grew from the Occupy movement, enables asynchronous consent-based decision-making across organizations in more than 100 countries. The Semkovo cooperative used Loomio to govern 130 members across 32 countries, maintaining genuine participation in constitutional decisions without requiring everyone to attend the same meeting. Decidim, Barcelona’s open-source participation platform, has reached 1.5 million users across 30 countries. Taiwan’s vTaiwan platform uses Polis, a computational consensus-building tool, to surface cross-group agreement on contested policy questions, with a mailing list of 200,000 individuals participating in national governance processes.

These tools are the interface layer of the governance stack: they handle the asynchronous participation problem, provide permanent decision records, and make constitutional governance accessible to members who can’t attend synchronous meetings. They do not replace the structure. They run on top of it.

The SUCC3SS platform is the cooperative-to-cooperative governance interoperability layer. What makes the governance stack genuinely scalable is not that every cooperative runs the same technology. It is that every cooperative running the stack operates on compatible principles: nested enterprises, consent-based circles, non-transferable governance tokens, subsidiarity as default. A community in Pittsfield and a community in Austin and a community in Lagos can run on the same governance architecture without belonging to the same organization. The stack is an open protocol.

Policy recognition matters. State cooperative statutes were written for organizations that run full-membership majority-vote governance. Consent-based circle governance is legally valid but not explicitly recognized in most state cooperative law. The governance stack argument to state legislators is straightforward: consent-based governance is more democratic than majority vote, not less. It requires every voice to be heard and every objection to be integrated. States should explicitly recognize it.

Any cooperative can adopt the governance stack without permission. The principles are documented here. The tools are available. The legal structures already exist in Colorado’s Limited Cooperative Association Act and Wyoming’s DUNA Act. The precedents are established by Mondragon’s congress structure, Buurtzorg’s team-of-teams model, and Endenburg Electric’s 25-year operating history.

Part IX: The Four-Paper Synthesis

This is what a complete cooperative operating system looks like.

Paper 1, “The Ownership Cure,” established the cooperative financial operating system: Profit First for cash management, Slicing Pie for dynamic equity tracking, cooperative surplus distribution at year-end. It answered the question of who owns what and how money flows.

Paper 2, “Synergistic Commerce,” established the economics of emergence: how cooperative networks generate value that no single actor could generate alone, and how that value is captured by the community rather than extracted by intermediaries. It answered the question of where wealth comes from in a cooperative economy.

Paper 3, “The Community Mint,” established the financial infrastructure: the three-token architecture (non-transferable governance token, community stablecoin, community currency) that makes cooperative economics programmable, transparent, and interoperable. It answered the question of how money moves and how participation is tracked.

Paper 4, this paper, establishes the governance architecture: how decisions are made, how authority is distributed, how power is made visible and accountable, and how the organization stays democratic without trading away its ability to act. It answers the question of who decides.

Together: ownership plus emergence plus financial infrastructure plus governance architecture. That is the complete R3SET operating system.

Not a philosophy. An operating system.

The cooperative movement spent 180 years building the values. The tools to build the infrastructure have existed for decades. The governance models have been tested in organizations ranging from 10-person worker cooperatives to 70,000-person federations to 12,000-nurse self-managing networks. What was missing was the synthesis: a complete architecture that pulls them together into something any cooperative can adopt and adapt.

The governance stack is that synthesis. Build with it.

R3THINK EVERYTHING.

Sources

1. Ostrom, E. (2010). Beyond Markets and States: Polycentric Governance of Complex Economic Systems. American Economic Review 100: 641–672. web.pdx.edu
2. Ostrom, E. (1990). Governing the Commons. Cambridge University Press. actu-environnement.com
3. Ostrom, E. Nobel Prize Lecture Slides (2009). nobelprize.org
4. Freeman, J. (1972). The Tyranny of Structurelessness. The Second Wave. jofreeman.com
5. Falkvinge, R. (2013). Swarmwise: The Tactical Manual to Changing the World. falkvinge.net
6. Brafman, O. and Beckstrom, R. (2006). The Starfish and the Spider: The Unstoppable Power of Leaderless Organizations. Portfolio/Penguin. Overview
7. Robertson, B. J. (2007–2025). Holacracy Constitution v5.0. holacracy.org
8. Robertson, B. J. History of Holacracy. holacracy.org
9. Robertson, B. J. Why Consent Is Better Than Consensus. holacracy.org
10. Sociocracy For All. Consent Decision-Making. sociocracyforall.org
11. Sociocracy For All. Organizational Circle Structure. sociocracyforall.org
12. Sociocracy For All. Sociocracy and Cooperatives. sociocracyforall.org
13. Sociocracy For All. Decision-Making Methods Comparison. sociocracyforall.org
14. Sociocracy 3.0. Principle of Consent. patterns.sociocracy30.org
15. Sociocracy.info. Gerard Endenburg. sociocracy.info
16. Strategy+Business. (2006). Sociocracy overview. strategy-business.com
17. Dunbar, R. BBC Future. (2022). Dunbar’s Number: Why We Can Only Maintain 150 Relationships. bbc.com
18. Research Outreach. (2025). Size Matters: Social Groups and Human Evolution. researchoutreach.org
19. Buurtzorg. About Us / Organisation. buurtzorg.com
20. Commonwealth Fund. (2015). Buurtzorg Case Study. commonwealthfund.org
21. W.L. Gore Organizational Model. publish.obsidian.md
22. W.L. Gore Lattice Organization. participedia.net
23. McChrystal Group. Team of Teams. mcchrystalgroup.com
24. ASIS Online. (2020). McChrystal: Focus on Empowering Frontline Decision-Makers. asisonline.org
25. Mondragon Corporation Annual Report 2023. mondragon-corporation.com
26. Co-operative News. Mondragon 2024 Results. thenews.coop
27. Business Insider. Zappos CEO Tony Hsieh on Holacracy Transition. businessinsider.com
28. Fortune. Zappos, Tony Hsieh, Holacracy. fortune.com
29. SI Labs. Holacracy Case Studies. si-labs.com
30. HBR. (2016). Beyond the Holacracy Hype. hbr.org
31. Bloomberg. Holacracy’s Failing. bloomberg.com
32. Medium / Andy Doyle. Medium Drops Holacracy. blog.ruben.org
33. Cornforth, C. (1995). Patterns of Cooperative Management. Economic and Industrial Democracy 16(4). geo.coop
34. Ephemera Journal. Pirate Politics Between Protest Movement and Parliament. ephemerajournal.org
35. The Register. (2010). Swedish Pirate Party Election Fail. theregister.com
36. NPR. (2009). In Sweden, Pirates Make The Web A Political Cause. npr.org
37. Orgvue. (2020). Research: Faster Decision-Making and Profit Growth. orgvue.com
38. Loomio. loomio.com
39. Loomio. (2026). Semkovo Cooperative Governance. loomio.com
40. Decidim. decidim.org
41. ScienceDirect. Decidim Platform Analysis. sciencedirect.com
42. vTaiwan. info.vtaiwan.tw
43. People Powered. Digital Participation in Taiwan. peoplepowered.org
44. Ternary Software / Holacracy revenue data. strategy-business.com
45. McGinnis, M. (2016). Polycentric Governance in Theory and Practice. Indiana University. mcginnis.pages.iu.edu
46. iRevolutions. Starfish and Spider: Decentralization Principles. irevolutions.org
47. Commons Library. Decentralisation: The Starfish and the Spider. commonslibrary.org
48. Harvard Business School. Buurtzorg. library.hbs.edu
49. World Economic Forum. (2022). Organization Structure and Work. weforum.org
50. Psych Safety. (2022). Dunbar’s Number, Psychological Safety and Team Size. psychsafety.com