Back to blog

Building a Cooperative Commonwealth Community: A Practical Guide

April 01, 2026 community cooperative governance implementation guide commons practice

This is the implementation guide for The Cooperative Commonwealth. That article described the architecture. This one tells you how to build it. Step by step. Starting tomorrow.


Phase 0: The Seed (1-5 people, Week 1-4)

What You Need

  • 3-5 people who have read What Humans Require and The Cooperative Commonwealth
  • Agreement on the Seven Gates as structural constraints (not ideology - engineering)
  • A shared communication channel (Signal group, not social media - no algorithmic curation from day one)
  • Weekly meeting commitment (2 hours, in person if possible)

What You Do

  1. Read and discuss the Seven Gates together. Not to agree on everything - to understand the constraints and WHY each exists.

  2. Name yourselves. Not a brand. A name that means something to the founding members. Names encode function.

  3. Write your Seed Statement: One page maximum. Three sections:
    • What we are building (a self-governing community based on the Seven Gates)
    • Why (because existing systems have failed the people in them)
    • What we commit to (the bylaws - see Community Bylaws)
  4. Establish meeting rhythm: Weekly assembly. Same time, same place. This is non-negotiable. Rhythm creates trust. Irregular meetings create anxiety.

  5. Open a shared ledger. Simple spreadsheet or notebook. Track: who contributed what (time, money, skills, space). This becomes the Reciprocity Ledger.

What You Don’t Do

  • Don’t incorporate yet. Legal structures come later.
  • Don’t build technology. Meet in person. Technology serves the commune, not the reverse.
  • Don’t recruit aggressively. Grow by attraction, not promotion.
  • Don’t write a manifesto. The Seed Statement is enough.

Phase 1: The Gathering (5-15 people, Month 2-6)

Growing the Core

Each founding member invites ONE person they trust deeply. Not friends-of-friends. Not “interesting people.” People they would trust with their house keys. This is the 150 Boundary (Gate 3) in action - growth through personal trust chains.

First Structures

Weekly Assembly: All members present. Decisions by consensus (not majority vote - consensus means everyone can live with the decision, not that everyone loves it). If consensus fails after 3 attempts, the proposal is tabled for one month.

Working Groups: Formed as needed, dissolved when done. No permanent sub-committees yet. Examples:

  • Food (shared meals, collective purchasing, garden if possible)
  • Space (finding/sharing meeting space, eventual shared workspace)
  • Finance (managing the shared ledger, collecting contributions)
  • Culture (organizing the first festival, rites of passage, celebrations)

Contribution Model:

  • Time contribution: minimum 4 hours/month to community activities
  • Financial contribution: voluntary, proportional to means (not equal)
  • Skill contribution: each member teaches something to the community at least once per quarter

First Festival

Within the first 6 months, organize a festival. Not a meeting. Not a workshop. A CELEBRATION. Food, music, fire, stories. Invite friends and neighbors who are NOT members. This is Gate 5: Anti-Structure - the hierarchy suspension that builds bonds deeper than any meeting can.

Reciprocity Audit (first one)

At month 6, the community does its first Reciprocity Audit:

  • What has each member contributed? (time, money, skills, space)
  • What has each member received? (support, connection, services, learning)
  • Is the exchange roughly proportional?
  • Is anyone extracting without contributing? (address directly, without shame)
  • Is anyone over-contributing and burning out? (address with gratitude and redistribution)

Phase 2: The Commune (15-50 people, Month 6-18)

Formalizing

At 15+ members, informal consensus needs structure. This is when you adopt the Community Bylaws formally.

Adoption process:

  1. Every member reads the bylaws AND the Annotated Bylaws (which explains WHY each rule exists)
  2. Assembly discussion (allow 2-3 sessions)
  3. Adoption by consensus
  4. Any member who cannot accept the bylaws may leave with full dignity and no penalty

Roles emerge (elected, term-limited, recallable):

Role Function Term Selection
Facilitator Chairs assemblies, maintains process 6 months, max 2 terms Elected by assembly
Keeper of the Ledger Manages reciprocity audit, finances 1 year, max 2 terms Elected by assembly
Welcomer Manages integration of new members 1 year, max 2 terms Elected by assembly
Culture Keeper Organizes festivals, rites, celebrations 1 year, max 2 terms Elected by assembly
Boundary Keeper Manages external relations, partnerships 1 year, max 2 terms Elected by assembly

All roles are subject to recall by majority of assembly at any time.

Shared Economy (first steps)

  • Shared purchasing: Food, tools, supplies bought collectively at lower cost
  • Skill exchange: Internal “time bank” - one hour of your work = one hour of anyone else’s work (plumber, programmer, cook, teacher - all equal)
  • Shared space: If possible, establish a community space (rented, donated, or member’s property made available). This is where assemblies, festivals, meals, and workshops happen.
  • Emergency fund: Small monthly contributions into a pool for members facing crisis. No application process - assembly decides instantly.

Integration Protocol (for new members)

  1. Introduction: Existing member sponsors the newcomer. Sponsor vouches for basic trust.
  2. Orientation: Newcomer attends 3 assemblies as observer (voice but no vote)
  3. Contribution: Newcomer contributes to one working group for 1 month
  4. Reading: Newcomer reads bylaws + annotated bylaws
  5. Assembly vote: After 3 months, assembly votes on full membership. Consensus required.
  6. Celebration: New member welcomed at next festival. Public.

Phase 3: The Full Commune (50-150 people, Month 18-36)

At this scale, new structures are needed

Sub-assemblies: When assembly exceeds 50, split into neighborhood/affinity sub-assemblies of 15-30. Sub-assemblies handle routine matters. Full assembly handles community-wide decisions. Delegates from sub-assemblies (mandated, recallable) coordinate.

Cooperative enterprises: Community members can start worker cooperatives under the community umbrella. Rules:

  • Maximum pay ratio: 6:1 (Mondragon model)
  • Minimum 30% worker ownership
  • Reciprocity ledger contribution to community (percentage of revenue/profit)
  • Products/services available to community at cost

Land and housing: If the community reaches 100+ members, explore:

  • Community land trust (land owned collectively, buildings owned individually)
  • Housing cooperative (shared ownership of multi-unit housing)
  • These are the most powerful embeddings of economy in social relationships

Digital tools (NOW, not before):

  • Polis-style consensus platform for large-group deliberation
  • Transparent ledger (can be blockchain-based but doesn’t have to be)
  • Communication (Signal, Matrix - encrypted, community-controlled, no algorithmic curation)

The 150 Boundary

When the commune approaches 150 members, it does NOT grow larger. It SPLITS. Like a cell dividing. Two communes of 75, each with full autonomy, linked by a coordination council of delegates from both. This is how you scale: not by making communes bigger but by making MORE communes.

The coordination council handles:

  • Inter-commune disputes
  • Shared resources (land, buildings, enterprises)
  • Relations with external communities and municipalities
  • Collective defense and mutual aid

This IS the beginning of nested sovereignty. Commune -> coordination council -> eventually: municipal federation.


Phase 4: The Network (150+ people, multiple communes, Year 3+)

Federation

Multiple communes in a region form a federation:

  • Each commune sends 2 mandated delegates (recallable)
  • Federation handles: shared infrastructure, inter-commune economy, external relations, defense
  • Federation CANNOT override commune decisions on matters within commune competency
  • Federation decisions require 2/3 consensus of communes (not delegates - communes vote as units)

Regional Economy

  • Inter-commune trade: Using community currency or time credits
  • Shared enterprises: Cooperatives that serve multiple communes
  • Training and apprenticeship: Members move between communes for cross-domain learning
  • Festival circuit: Rotating festivals between communes builds inter-commune bonds

External Relations

  • Partner with other cooperative movements (Mondragon network, cooperative federations)
  • Engage with municipal government (not replace it - yet)
  • Establish legal structures (cooperative association, community land trust, etc.)
  • Maintain boundary permeability: always accept new members through integration protocol

The Ongoing Cycle

Every community, regardless of phase, maintains:

Frequency Activity Gate served
Weekly Assembly meeting Governance, meaning
Monthly Shared meal/potluck Reciprocity, anti-structure
Quarterly Skill-sharing workshop Reciprocity, meaning
Biannual Reciprocity audit Reciprocity, leveling
Biannual Festival/celebration Anti-structure, boundary
Annual Role elections Leveling, governance
Annual Bylaws review + amendment All gates
At 150 members Cell division Scale gate

What This Costs

Time: 4-8 hours/month per member (assembly + working group + contribution)

Money: Community contribution of 2-5% of income (voluntary, proportional). Emergency fund contributions. Cooperative enterprise investments.

Emotional: Learning to make decisions collectively is hard. Conflict is inevitable. The bylaws provide process for conflict resolution. The anti-structure gate provides space for renewal.

What it returns: Mutual aid in crisis. Shared economy reducing costs. Meaningful relationships. Skill development. Festival culture. The experience of genuine governance. The knowledge that you are not alone.


Start Here

  1. Find 3-5 people
  2. Read the articles together
  3. Set a weekly meeting
  4. Open a shared ledger
  5. Begin

The forest designs itself. You create the conditions and protect the constraints.


*Next: Community Bylaws Annotated Bylaws*