Failure mode · 01
Unclear purpose & scope
When purpose and boundaries stay implicit, expectations drift and conflict becomes personal.
The Blueprint · the first tangible outcome of EcoHubs
The guidebook
we wished had existed.
The Blueprint — formally RCOS (Regenerative Community Operating System) — is an open standard for designing and operating regenerative communities. Not software, not an ideology — a shared way to make community structure explicit, testable, and improvable.
It is the place where the EcoHubs vision meets the ground. The first tangible thing that any community — including yours — can pick up, read, fork, and put to work today.
Open standard Modular & forkable Tested in a live pilot
layer 0 · purpose & scope
layer 1 · membership
layer 2 · governance
layer 3 · economy & resources
layer 4 · conflict, repair & accountability
layer 5 · operations & coordination
layer 6 · evolution & adaptation
— optional —
module · permaculture
module · education
module · housing
module · land commons safeguards
module · alternative economies
Open · Forkable · Adaptable blueprint.ecohubs.community ↗
19-min introduction
If you have nineteen minutes,
here is the whole picture.
A walk-through of what RCOS is, why it exists, and how the layers fit together. Best watched with a coffee — it covers the ground that the rest of this page only sketches.
Why structure, before anything else
Most communities don't fail on values.
They fail on the things no one wrote down.
It's estimated that 80–90% of intentional communities collapse — not because the vision was wrong, but because the same handful of invisible things were never made explicit. The Blueprint is built around those failure points, so a community can name them before they break.
Failure mode · 02
Implicit membership
If roles, rights, and exit paths are undefined, people end up negotiating belonging in moments of stress.
Failure mode · 03
Decision drift
Without explicit decision pathways, authority quietly accumulates and outcomes start to feel arbitrary.
Failure mode · 04
Resource ambiguity
Commons vs. private, contribution recognition, treasury rules — all need shared clarity, or money becomes the wound.
Failure mode · 05
No repair path
Conflict is normal. Without defined escalation and repair, issues get buried until they explode.
Failure mode · 06
Knowledge that walks out
When patterns aren't written down, the community resets every time a key person leaves. Memory shouldn't depend on individuals.
The Blueprint doesn't promise harmony. It just refuses to leave these things unsaid.
What the Blueprint is, and isn't
Clarity, not persuasion.
The Blueprint can be misread as a lot of things it isn't. Before going further, here is the line we hold — carefully, on purpose.
It is A formal, open standard.
- ✓ A layered operating system for community life.
Clear responsibility boundaries across membership, governance, resources, conflict, operations, evolution.
- ✓ A shared language between communities.
So lessons travel. So a hub in Ecuador can learn from one in Portugal without translating from scratch.
- ✓ Grounded in real failure modes.
Stress tests based on what actually breaks communities — informal power, conflict avoidance, resource fog.
- ✓ Modular and adaptable.
Adopt parts now, evolve the rest. No community has to take all of it to benefit from any of it.
It is not And never quietly will be.
- × Software, or an app you install.
RCOS is a standard. Tools may help — they are not the system.
- × A DAO product or token scheme.
A DAO — a rule-based organization where authority is defined by agreed processes — can sit on top, but the Blueprint isn't crypto, isn't tradeable, isn't speculative.
- × A fixed ideology or "the right way" to live.
It describes structure and constraints, not values. Communities of very different worldviews can use it.
- × A replacement for human judgment.
RCOS reduces ambiguity. It does not — and should not — make the call instead of the people in the room.
RCOS Core · the seven layers
Seven layers, each with one job.
RCOS is structured into layers with clear responsibility boundaries. Communities adapt the implementation details — the boundaries themselves are what keep assumptions from going implicit.
L0 Purpose & Scope
Why this community exists.
Why the community exists, what is governed, and what invariants must not be violated.
PurposeScopeInvariants
L1 Membership
How people join, stay, and leave.
No implicit membership. Entry, participation, status changes, and exit are visible and dignified.
Entry pathsRightsExit
L2 Governance
Who decides what, on whose behalf.
Decision pathways, delegation, and the constraints that keep authority reviewable.
Decision typesDelegationTransparency
L3 Economy & Resources
How value flows, how the commons is held.
Commons vs. private, contribution accounting, treasury rules — the things that quietly break communities when left vague.
CommonsContributionTreasury
L4 Conflict, Repair & Accountability
How we repair, hold, and (sometimes) part ways.
Conflict is treated as a normal condition with defined pathways — not a failure to be hidden.
RepairEscalationSeparation
L5 Operations & Coordination
The day-to-day, without burning anyone out.
Roles, meetings, documentation, workload boundaries — the things that look small until they aren't.
RolesCadenceWorkload
L6 Evolution & Adaptation
How the whole system changes — safely, in the open.
Amendments, experiments, retrospectives, and versioning — so the Blueprint can keep getting truer without collapsing on its own changes.
AmendmentsRetrospectivesVersioning
+ Modules
Real-world domains.
Permaculture, education, housing, culture — applied, not theoretical.
↗ Explore
Open the full Blueprint
It's freely readable. Editable by members. Evolving with every pilot.
Core invariants stay the same · modules extend, never override
Modules · the optional outer ring
The core stays small.
The modules go where life is.
Modules are optional extensions that apply RCOS to specific domains — food systems, education, housing, land — without changing the core layers or overriding governance. Adopt the ones that fit your land, your people, your stage. Skip the rest.
Modules describe structure, not "the right way" to live. A community can run the Permaculture module or the Minimal one — both sit cleanly on the same core.
P
Permaculture
Land, food and water as a designed living system.
M
Minimal Permaculture
A lighter starter version, for hubs without acreage yet.
E
Education
Mixed-age, curiosity-led, rooted in real practice.
H
Housing
Forms of dwelling and stewardship, from co-living to villages.
L
Land Commons Safeguards
Protections so land held in common stays held in common.
A
Alternative Economies
Contribution accounting, mutual credit, internal value units.
Why this isn't another community project
Other people have tried.
We learned from where they broke.
We are not the first to try this — and that is the point. Most intentional communities fail in the same handful of ways. The Blueprint is built around those failure points, not around anyone's ideology.
01
Most projects
Built around one founder's vision and aesthetic.
EcoHubs
Built around a pattern language the community itself shapes and forks.
02
Most projects
Avoid talking about money, power, or conflict until they explode.
EcoHubs
Makes the invisible explicit — before it breaks. Conflict patterns are written down on day one.
03
Most projects
Either fully off-grid retreat, or fully digital with no roots.
EcoHubs
Local hubs, woven into a global network. Roots and reach, not one or the other.
04
Most projects
Sell a fixed model. Take it or leave it.
EcoHubs
Open-source. Every pattern is reviewable, replaceable, forkable by the people who'll live it.
05
Most projects
Charisma-based authority. The founder is the rulebook.
EcoHubs
No gurus. Authority is structural, distributed, and written down — so anyone can hold it.
06
Most projects
Idealistic about labor. Pretend everyone contributes equally.
EcoHubs
Honest accounting. XP and ECO make contribution visible — so care and craft don't go unseen.
Where the Blueprint sits in the EcoHubs vision
The vision is the why.
The Blueprint is the first thing you can hold.
EcoHubs is a long-horizon project — small, human-scale communities, woven into a global commons. The Blueprint is the first concrete piece of that. The bridge between intention and ground.
01 · Vision
A network of regenerative hubs.
Small, place-based communities, each adapted to its land and culture, woven into a shared commons that gets stronger over time.
Read the vision →02 · Blueprint · you are here
An open standard any hub can pick up.
RCOS makes the structure of community life explicit — so a hub doesn't have to invent membership, governance, or repair from scratch.
Open the Blueprint ↗03 · Pilots
Real communities, applying it.
A first community in Ecuador is already running the Blueprint under real ecological, social, and economic constraints — feeding what they learn back into the standard.
See the Ecuador pilot →Every pilot teaches the standard. Every standard improvement helps the next pilot. That loop is the project.
From idea to ground, and back
How the Blueprint actually gets applied.
It is built as a loop, not a launch. Every community that runs it teaches the next one something — and the Blueprint that comes after is a little truer than the one that came before.
- 01
Read & locate yourself.
A community reads the Blueprint and identifies which layers are already explicit, which are implicit, and which are missing entirely.
- 02
Adopt what fits.
Pick the layers and modules that match your context. RCOS supports partial adoption — start with one weak point, not all seven layers at once.
- 03
Adapt to your context.
Translate the patterns into your land, your culture, your stage. Local adaptation is expected — the boundaries between layers are the part that stays.
- 04
Run it. Stress-test it.
Apply it under real conditions. Note where it bends, where it breaks, where it surprises you. The stress tests in RCOS are based on what other communities have actually broken on.
- 05
Document, openly.
What worked. What didn't. What hurt. Write it down where the next community can find it — failure is the most useful thing the network has, when it's shared.
- 06
Feed it back into the standard.
Lessons travel back into the Blueprint through proposals, reviews, and version notes. The standard evolves through Layer 6 — safely, in the open, on a cadence the network can keep up with.
Pilot · Ecuador
running RCOS v0.4L0 purpose // adopted, ratified
L1 membership // adopted, in use
L2 governance // adapted: small-circle quorum
L3 economy // adapted: contribution log
L4 conflict // adopted, two repairs run
L5 operations // in progress
L6 evolution // scheduled, month 3
module permaculture // active
module education // scoping
# lessons sent back
+ pattern: silent-exit repair
+ stress test: month-3 rotation
~ delegation: rotation cap (proposed)
Every line above is a real choice the pilot is documenting in the open — the same way any community that adopts the Blueprint can.
Pilot · Active now
FruitHaven community in Ecuador
Applying RCOS Blueprint practice since March 2026
Already Living, Not Just Planned
A pilot is already happening
— and it's working.
In March 2026, we introduced the Blueprint to a community in Ecuador facing complex, long-standing divisions. These were people deeply committed to healing, yet they needed a new path forward to bridge the gaps that had persisted for so long.
The Blueprint doesn't magic away the pain. It does something quieter: it names the thing that's hard, and gives the community a shared language to work on it together.
"The introduction of the Regenerative Community Operating System sparked renewed motivation and inspiration within our community."
— Boris P., Member of the pilot community
Non-ideological
Works online or offline
Fork-friendly · use your own way
Who picks this up
The Blueprint is useful to more than one kind of person.
For founders
Starting a new hub.
Purpose & scope templates. Membership pathways. Decision maps. Things you'd otherwise spend a year discovering the hard way.
For existing communities
Repairing one weak point.
Adopt only the layer that's broken — usually conflict, governance, or resources — without rewriting your whole community.
For researchers & educators
Studying what fails, repeatably.
Stress tests, failure analyses, and a layered vocabulary for comparing communities side by side.
For governance designers
Keeping authority explicit.
Decision rights and constraints, delegation patterns, transparency norms — written down so they can be reviewed.
Contribute
We are not finished.
That is the point.
The Blueprint gets better with every person who reads it carefully, disagrees with a chapter, runs an experiment, or comes back with what they learned. There are four ways in.
01 · Write or improve
Draft new articles or refine existing ones.
Pattern descriptions, examples, stress tests, edge cases. The standard is text — and text gets better with editors.
Open the Blueprint ↗02 · Review & discuss
Argue with a chapter, in public.
The best critiques become co-authors. If something feels wrong, that signal is exactly what the standard needs.
Read & respond ↗03 · Document an experiment
Share what you tried — and what broke.
Communities running parts of RCOS contribute the scars and the wins. Those go straight into the next version.
Become a member →04 · Propose a module
Apply RCOS to a domain we haven't yet.
Modules sit on top of the core. If you know a domain — health, ritual, climate — that the Blueprint should reach, write the module.
Open the Blueprint ↗Contributions sit inside membership — not because we're gating, but because the standard stays coherent when the people editing it are part of the wider community.
Honest questions, honest answers
About the Blueprint, specifically.
What’s the difference between "the Blueprint" and "RCOS"? +
They are the same thing. RCOS (Regenerative Community Operating System) is the formal name. Blueprint is the friendly, human-facing name we use during the transition phase. You’ll see both — they always refer to the same standard.
Do I have to use the whole thing? +
No. The Blueprint is designed for partial adoption. Most communities start with one or two layers — usually the one that’s currently broken — and grow into the others over time. Modules are optional on top of that.
Is this software? A DAO? A token? +
None of those. RCOS is a written standard — a set of patterns, layer boundaries, and stress tests. Tools (governance software, contribution ledgers, even a DAO) can sit on top of it, but the standard itself is non-speculative, non-tradeable, and non-technical. You can run it on paper.
How do I trust this won’t fail like other community models? +
Honestly: we don’t promise it won’t. What we do is treat each community as a learning system, document failures and adaptations openly, and iterate the standard rather than assuming the first version is the right one. The Blueprint is built around known failure modes — not around someone’s belief that they’ve solved community.
Can I use it for a community that isn’t an EcoHub? +
Yes. The Blueprint is open-source and structurally agnostic. A co-op, a co-living house, a research collective, a neighborhood association — any group that needs to make membership, governance, conflict, or resources explicit can adopt parts of it.
Where do I actually read it? +
The current version lives at blueprint.ecohubs.community. It’s a public draft, evolving in the open — read it, fork it, argue with it.
The Blueprint is freely readable
Read it. Argue with it.
Run it.
The standard is open. The pilots are live. The next version is shaped by whoever shows up and edits it well.
Open standard · Modular · Forkable · Built in the open