Reduce Repeated Mistakes
Use shared stress tests and failure reports instead of starting from scratch.
Before
Every community starts from scratch
After
Build on tested foundations
Open Standard
The Blueprint (RCOS) for Regenerative Communities
The Blueprint, formally called RCOS (Regenerative Community Operating System), is a shared way to make community structure explicit—so authority, responsibility, and repair do not drift into informal norms.
Adaptable by design. Grounded in practice. Focused on clarity over persuasion.
Why Structure Matters
Communities fail for repeatable reasons: unclear membership, decision drift, resource ambiguity, and missing repair paths. RCOS treats these as design problems—things that can be made explicit, tested, and improved.
Community living knowledge used to be local and implicit—passed down through generations within relatively isolated groups.
Today, societies are far more complex, interconnected, and regulated. Without shared frameworks, new initiatives repeatedly fail on the same predictable issues.
Reinventing everything locally no longer works. We need shared infrastructure for community knowledge.
The Cycle of Failure
Unclear Purpose & Scope
When purpose and boundaries stay implicit, expectations drift and conflict becomes personal.
A Shared Foundation for Many Communities
Independent communities need a common foundation to scale without losing autonomy. The blueprint provides coordination without centralization.
Fragmented & Fragile
Each community starts from zero
Not one perfect model
A shared structure before ideology
Adapted locally, made explicit
Coordination without centralization
What the Blueprint Is (and Isn't)
Clear positioning. No misconceptions.
What It IS
A formal, open standard (RCOS)
The Blueprint is the human-facing name for RCOS during the transition
A layered operating system
Clear responsibility boundaries across core layers of community life
A shared language for governance
Membership, economy, conflict, operations, and evolution are made legible
Grounded in real failure modes
Stress tests and practice help communities learn without collapsing
What It IS NOT
Software or a platform
RCOS is a standard, not an app you install
A DAO product
Governance tools can help, but they are not the system itself
A fixed ideology
Structure comes before values; communities adapt without losing clarity
A replacement for judgment
RCOS reduces ambiguity but never replaces people
RCOS Core
The RCOS Core Layers
RCOS is organized into layers with clear responsibility boundaries. Communities can adapt implementation details, but the layer boundaries keep assumptions from going implicit.
Layer 0
Layer 0: Purpose & Scope
Why the community exists, what is governed, and what must not be violated.
Examples
Purpose statementScope boundariesNon-negotiable invariantsWhat is out of scope
Optional Extensions
Modules and Adaptability
Modules extend RCOS into real-world domains without changing core invariants or overriding governance. Communities can adopt RCOS partially or fully, and evolve their implementation over time.
What modules do
- Apply RCOS to specific domains like food systems, housing, education, or land stewardship.
- Remain optional: communities choose what fits their context and constraints.
- Stay compatible with the core: modules do not change core layer boundaries.
Example modules
PermacultureMinimal PermacultureEducationHousingLand Commons SafeguardsAlternative Economies
Modules are intentionally non-ideological: they describe structure and constraints, not “the right way” to live.
Iterative Process
From Theory to Practice (and Back)
This is rigorous, iterative, and real. Ideas emerge from practice, get tested, and evolve.
1
Ideas from Practice
Real challenges surface from communities living the work.
Versioned on GitHub so changes are trackable and reviewable.
Auto-playing (hover to pause)
Stress Tests & Realism
RCOS uses real failure modes as learning tools. The goal is not perfection, but legibility under stress.
Faster Learning Cycles
Parallel experiments make learning visible and transferable.
Before
Years to discover what works
After
Shared insights speed progress
Shared Memory Across Hubs
Structure stays legible even as people come and go.
Before
Knowledge walks out the door
After
Institutional memory remains
Lower Barrier to Starting
Adopt parts of RCOS now, evolve the rest over time.
Before
Overwhelmed by complexity
After
Clear starting points
How You Can Use the Blueprint
Practical entry points for different needs.
New Hub Founders
Starting from zero and trying to stay coherent under pressure.
You'll find
- Purpose & scope templates
- Membership pathways
- Decision maps and constraints
Existing Communities
Improving a specific weak point without rewriting everything.
You'll find
- Conflict repair pathways
- Resource governance patterns
- Operations and role clarity
Researchers & Educators
Studying how communities succeed and fail in repeatable ways.
You'll find
- Stress tests
- Failure analyses
- Layered comparisons between communities
Governance Designers
Designing decision pathways that keep authority explicit.
You'll find
- Decision rights and constraints
- Delegation patterns
- Transparency and documentation norms
Join the Effort
Help Improve the Standard
The blueprint is publicly readable. Contributions require membership to help keep the core coherent.
Ways to Contribute
Write or Improve
Draft new articles or refine existing ones.
Review & Discuss
Provide feedback, ask questions, strengthen arguments.
Document Experiments
Share what you've tried—successes and failures.
Propose New Modules
Suggest optional extensions that apply RCOS to specific domains.
Your Journey
1
Explore the blueprint
2
Join the community
3
Find your focus area
4
Start contributing
Apply for Membership
Already a member? Start contributing
This Is a Long-Term Project
Built slowly. Built carefully. Built together.
Designed to outlive its creators. Designed to grow with every community that uses it.
The blueprint grows with every contribution.