RCOS Templates
Each layer asks your community a handful of questions. The templates are where you write the answers down: one document per topic, with the rules it covers, why it matters, and examples from other groups.
How to use this
- 1
Start with Layer 0
Your purpose and the lines you won't cross come first. Every later template refers back to them.
- 2
Fill it in together
Each section says what to cover and why it matters, so the conversation stays on track. Write the answers down while you're in the room.
- 3
Keep it up to date
Note when the group agreed, keep the document where everyone can find it, and change it only in the way you've agreed to.
Layer 0 · Identity & Scope
What problem does this community exist to solve?
- Purpose Charter §2.1 States the one primary purpose your community exists for, its secondary purposes and explicit non-goals, and the conditions under which that purpose may change.
- Scope Declaration §2.2 Draws the boundary of what your community governs: the assets, decision domains, activities, and responsibilities in scope — and what is explicitly out of scope.
- Invariants Register §2.3 Invariants are constraints that MUST NOT be violated while they are in force. No decision, role, process, or emergency measure may override an invariant. If a conflict arises between an invariant and any other rule, the invariant prevails.
- Identity Constraints Register §2.4 Identity constraints are the non-negotiable behavioural, ethical, and structural boundaries that shape who the community is. Unlike invariants (which protect the system itself), identity constraints define how members and the community relate to people, ecosystems, and ideologies.
Layer 1 · Membership System
Who is inside the system, and under what conditions?
- Membership Agreement §3.4 Signed (or explicitly acknowledged) by every member at the time of admission. Defines the rights and obligations of each membership state.
- Onboarding Protocol §3.2 Defines how a person becomes a member: the admission criteria, the onboarding steps, the membership state they start in, and how the trial period is evaluated and recorded.
- Exit & Separation Protocol §3.6 Defines how membership ends — voluntary exit at any time, forced exit and suspension with due process — and how assets, roles, and responsibilities are separated when someone leaves.
- Membership State Registry §3.1 Lists every membership state your community recognizes, with the rights and obligations of each and how people move between them. Each person holds exactly one state at a time.
Layer 2 · Governance & Decision Logic
How decisions are made, changed, and enforced.
- Decision Matrix §4.2 Maps every decision type and domain to an authorized role or body, mechanism, threshold, and escalation path. Decisions made outside this matrix are considered invalid.
- Governance Protocol §4.5 Defines the full lifecycle of a collective decision — from proposal submission to documentation and appeal.
- Authority Registry §4.3 Lists all roles, circles, or bodies that hold decision-making authority, along with their explicit scope, limits, and term.
Layer 3 · Economic & Resource System
How value flows inside the community.
- Internal Economy Protocol §5.1 Defines what is commons and what is private, which contributions are recognized and how, any internal units, and the limits that keep value from concentrating in a few hands.
- Treasury Ruleset §5.3 Sets the rules for the community's shared money: what the treasury covers, where income comes from, who may spend and up to what limit, how it is reported, and the limits on reserves, risk, debt, and conflicts of interest.
Layer 4 · Conflict, Repair & Accountability
What happens when things break.
- Conflict Resolution Ladder §6.1 Gives every conflict a clear path, from direct conversation through facilitated dialogue and formal review up to a governance decision, with rules for non-response, deadlock, facilitators, and privacy along the way.
- Accountability Protocol §6.4 Defines what happens when an agreement is broken: what triggers a review, how it is investigated, the due-process and anti-retaliation guarantees, the repair and sanction options, and how rights are restored.
Layer 5 · Operations & Coordination
How daily life and work actually function.
- Operations Manual §7.1 Describes how day-to-day work gets done: the core processes, ad-hoc responsibilities, how roles hand work to each other, workload limits, continuity when people are away, and where the documentation lives.
- Role Registry §7.1 Lists every operational and functional role in your community with its purpose, domain, and current holder, so it is always clear who does what — and that no one's role is unwritten.
- Meeting Templates §7.2 Meeting templates declare the purpose, decision scope, quorum, and structure of each meeting type. A meeting without a declared template will, given enough time, accumulate authority it should not have. Adapt these templates and add or remove meeting types as your community needs.
Layer 6 · Evolution & Adaptation
How the system changes without collapsing.
- Change Protocol §8.1 Defines how the community's rules change: how a change is proposed, classified, reviewed, adopted or rejected, rolled out and rolled back — plus the narrow paths for emergency changes and experiments.
- Version History §8.2 The authoritative human-readable record of all adopted changes to your community's RCOS implementation. The currently active version is the most recent entry at the top of this file. Superseded rules remain accessible via version control.
- Learning Log §8.4 Records major failures, adaptations, reversals, and systemic learnings. Repeated failure patterns must trigger structural review, not individual blame. Entries are prepended (most recent first).
- Experiment Template §8.3 Experiments let the community try a change without permanently adopting it. To stay safe, every experiment must be time-bounded, labeled, and auto-expiring — and must record its results in the Learning Log.
Download all templates
Every template, bundled as a zip. Pick the format that fits how your community works.
Generated 2026-11-06
Download a single template
Layer 0
Layer 1
About
What's in a template
Every template:
- names the rules in the standard it answers, so you can see exactly what it covers;
- explains each section: why it exists and what goes wrong without it;
- shows how other communities answered: examples, not recommendations;
- leaves clear blanks for your own answers.
The templates don't tell you what to value or how to live. They make sure the things that matter are written down, so they can be discussed, agreed and changed openly.
Who they're for
- Groups starting a community who want clear structure from day one.
- Existing communities checking what they've never written down.
- Facilitators who want a concrete document to work on in the room.
You don't have to do everything at once
Partial adoption still counts, as long as what you adopt is written down and open to review. Skipping a template is fine; claiming to have one you don't is not.
Languages and formats
The templates are available in English, German, Spanish, French and Brazilian Portuguese. Read them here, or download them as Markdown, Word (DOCX) or OpenDocument (ODT) files to edit offline.