RCOS — Regenerative Community Operating System

A modular operating system for intentional communities

Source: blueprint.ecohubs.community by EcoHubs
License: Open-source
Version: RCOS v1.0

---

What Is RCOS?

RCOS is a modular governance framework — an operating system for intentional communities. It makes implicit social structures explicit so communities can design, stress-test, and evolve their operations before conflicts arise.

The core principle: Explicit beats Implicit.

RCOS is designed for communities of 5–150 people and structured as 7 independent layers (Layer 0 through Layer 6). Each layer has a stable boundary — communities adapt details via modules without altering the invariants that hold the community together.

---

The 7 Layers at a Glance

Layer	Name	Core Question
Layer 0	Identity & Scope	Why does this community exist, and what does it govern?
Layer 1	Membership	How do people join, participate, and leave?
Layer 2	Governance	Who decides what, and how?
Layer 3	Economy & Resources	How do we manage value flows, contributions, and commons?
Layer 4	Conflict, Repair & Accountability	How do we handle disputes and hold each other accountable?
Layer 5	Operations & Coordination	How do we organize daily work without burnout?
Layer 6	Evolution	How do we adapt and improve over time?

---

Layer 0 — Identity & Scope

Core question: Why does this community exist, and what does it govern?

Layer 0 establishes the foundational why and what of the community. It defines:

• Purpose statement — The reason the community exists
• Governed elements — What the community explicitly governs (assets, domains, activities)
• Invariants — Non-negotiable rules that cannot be changed (e.g., core values, safety standards)
• Out-of-scope — What the community explicitly does not govern (prevents hidden ideology or scope creep)

Why It Matters

Most community conflict comes from unstated assumptions about what the community is "about." Layer 0 makes these explicit from day one. It draws a clear boundary: inside the scope = governed; outside = out-of-bounds.

Key Sub-Questions

• What is our purpose?
• What assets, domains, and activities do we explicitly govern?
• What would break the community's identity? (those are your invariants)
• What are we not doing?

RCOS Stress-Tests for Layer 0

• Does the purpose statement actually guide decisions?
• Are invariants genuinely non-negotiable, or just preferences?
• Is anything missing from the scope that should be included?

---

Layer 1 — Membership

Core question: How do people join, participate, and leave?

Layer 1 defines the complete membership lifecycle:

• Entry pathways — How newcomers join (application, trial period, sponsorship, etc.)
• Participation rights — What members can do, access, and decide
• Status changes — How members move between roles or levels
• Exit paths — How and why members leave (voluntary, involuntary, graduated)
• Obligations symmetry — Rights and duties are balanced — no special classes

Key Sub-Questions

• What are the stages of membership?
• What rights does each status grant?
• What happens if someone wants to leave?
• How do we handle involuntary exits?

RCOS Stress-Tests for Layer 1

• Are there elite classes with special rights?
• Can members exit without penalty or stigma?
• Is the trial period long enough to surface real alignment?

---

Layer 2 — Governance

Core question: Who decides what, and how?

Layer 2 makes decision-making explicit:

• Decision rights — Who has authority over what domains
• Authority constraints — What no one can decide alone
• Delegation patterns — How authority flows to roles and circles
• Protocols — Specific procedures for making different types of decisions
• Constitutional vs. operational separation — Day-to-day operations vs. fundamental rule changes (kept separate for stability)

Key Sub-Questions

• What types of decisions require what process (majority, consensus, single person)?
• How are roles assigned and rotated?
• What are the constraints on founders and leaders?
• How do we distinguish operational decisions from constitutional ones?

RCOS Stress-Tests for Layer 2

• Can founders become authoritarian without accountability?
• Are there review mechanisms for concentrated power?
• Do decisions actually get made efficiently, or does everything stall?

---

Layer 3 — Economy & Resources

Core question: How do we manage value flows, contributions, and commons?

Layer 3 governs the economic layer:

• Value flows — How money and resources move through the community
• Commons vs. private resources — What is shared vs. individually owned
• Contributions — How labor, care work, and intangible inputs are tracked and valued
• Treasuries — How community funds are managed and accessed
• Anti-privatization — Preventing invisible enclosure of common wealth

Key Sub-Questions

• What is commons, what is private?
• How do we value and track contributions fairly (including care work)?
• Who controls treasury access?
• How do we prevent resource privatization?

RCOS Stress-Tests for Layer 3

• Is care work (cooking, cleaning, emotional labor) actually valued?
• Can a small group capture common resources for private gain?
• Are treasury decisions transparent to all members?

---

Layer 4 — Conflict, Repair & Accountability

Core question: How do we handle disputes and hold each other accountable?

Layer 4 provides a structured "resolution ladder" for handling conflict:

• Conflict pathways — Step-by-step process for raising and resolving disputes
• Escalation steps — What happens when initial resolution fails
• Safety provisions — How to protect members during conflicts
• Repair mechanisms — How to rebuild trust after a breach
• Due process — Fair hearing for all parties before consequences

Key Sub-Questions

• What is the first step when a conflict arises?
• Who can escalate, and to whom?
• How do we protect the person raising a concern from retaliation?
• How do we repair relationships after a conflict?

RCOS Stress-Tests for Layer 4

• Do members know how to use the conflict process, or does conflict go underground?
• Can someone be excluded informally without due process?
• Is there a "resolution ladder" or does everything get escalated to the same level?

---

Layer 5 — Operations & Coordination

Core question: How do we organize daily work without burnout?

Layer 5 enables the community to function day-to-day:

• Role clarity — Every role has a clear description, scope, and deliverables
• Meeting structures — Regular meetings with clear purposes and formats
• Documentation — Decisions, agreements, and processes are recorded
• Workload limits — Preventing heroics and burnout through sustainable pace
• Coordination mechanisms — How work gets organized across teams and circles

Key Sub-Questions

• Is every role description current and clear?
• Are meetings serving their stated purpose, or are they performative?
• Is there a single place to find how things work?
• How do we prevent reliance on "hero" members who do everything?

RCOS Stress-Tests for Layer 5

• Does work actually get distributed, or does it accumulate on a few?
• Are meetings producing outcomes, or just discussion?
• Can someone new figure out how to contribute within 24 hours?

---

Layer 6 — Evolution

Core question: How do we adapt and improve over time?

Layer 6 enables controlled, learning-based change:

• Versioning — How the community's own rules and agreements can change
• Learning frameworks — Regular retrospectives, retrospectives with teeth
• Stress-testing — Ongoing testing of each layer against real conditions
• Change control — Preventing whimsical or self-serving alterations to core structures

Key Sub-Questions

• How can the community's own rules be changed? By whom, with what process?
• Are we learning from failures, or just filing them away?
• How do we distinguish genuine improvement from captured change?
• How do we prevent the community from drifting away from its purpose?

RCOS Stress-Tests for Layer 6

• Have we actually changed anything based on past failures?
• Can a well-resourced actor capture the evolution process?
• Is change too easy (chaos) or too hard (stagnation)?

---

How RCOS Relates to Other Frameworks

Framework	Role	Relationship
Community Alchemy	Sequential step-by-step journey (vision → land → funding → build → live)	RCOS fills the governance and operations gaps within each Alchemy step
RN 5-Spiral Model	Timeline and milestones for community development	RCOS Layer 2 (Governance) maps to Alchemy Step 3; RCOS Layer 5 (Operations) maps to Spiral 4
CLIPS	Inner work + personal/community health checks	CLIPS fills the individual readiness layer that RCOS doesn't address

Failure Factor Comparison

Failure Factor	RN Framework	Community Alchemy	RCOS
Unclear vision	✓ Spiral 1	✓ Step 1	—
Financial failure	✓ Financial modeling	✓ Step 4	✓ Layer 3
Governance collapse	✓ Human Systems pillar	✓ Step 3	✓ Layer 2, 4
Member conflict	✓ Human Systems pillar	✓ Step 3	✓ Layer 4
Operational burnout	✓ Spiral 4	✓ Step 10	✓ Layer 5

---

How to Apply RCOS

For New Communities

1. Start with Layer 0 (Identity & Scope) — before anything else
2. Build Layer 1 (Membership) and Layer 2 (Governance) before people join
3. Add Layer 3, 4, 5 in parallel as the community grows
4. Layer 6 is ongoing from day one

For Existing Communities

1. Audit first — Run the RCOS stress-tests as diagnostics
2. Ask: "What's frustrated members lately?" — that'll point to the broken layer
3. Don't impose top-down — surface pain points and address them with the affected members
4. Layer 4 (Conflict) is often the most urgent to formalize in existing communities

Practical Starting Sequence

Priority	Layer	Why
🔴 Urgent	Layer 4	Conflict processes prevent community death
🟡 Important	Layer 2	Unclear governance causes most friction
🟡 Important	Layer 3	Economic fairness prevents resentment
🟢 Foundation	Layer 0	Purpose drift destroys alignment
🟢 Foundation	Layer 1	Unclear membership creates boundary conflicts
🔵 Ongoing	Layer 5 + 6	Operational clarity and learning loops

---

Key Vocabulary

Term	Definition
Layer	One of the 7 independent structural areas of RCOS
Module	Adaptable details within a layer — changeable without altering invariants
Invariant	Non-negotiable rule that cannot be changed (layer-specific)
Explicit vs. Implicit	RCOS principle — written, agreed, visible beats unwritten, assumed
Role	Explicit bundle of responsibilities, authority, and accountability — attached to a position, not a person
Scope	Explicit declaration of what the community governs vs. out-of-scope
Stewardship	Responsibility for care and maintenance of a resource within defined boundaries
Stress-test	A diagnostic exercise that probes whether a layer will hold under pressure
Resolution Ladder	Step-by-step escalation path for resolving conflicts

---

Resources

• Official site: blueprint.ecohubs.community
• EcoHubs: ecohubs.community
• RCOS Community: Join the EcoHubs network for templates, stress-tests, and ongoing refinement

---

RCOS is open-source and DAO-governed — contributions welcome from all communities applying and improving it.