The invariant nobody protected
The founding principle everybody assumed was permanent — changeable, it turns out, by an ordinary majority on an ordinary evening.
What it looks like
- The community has principles it calls non-negotiable and no rule saying how they change.
- The same process amends the guest policy and the constitution.
- Members would be shocked by a change that is procedurally available today.
- Nobody can list what could never be decided by a simple majority.
Why it is hard to see
Because the protection everybody is relying on is social, and social protection is invisible until it fails.
Ask a community whether it could sell the land, or drop the thing it exists for, and the honest answer is usually of course not, nobody would ever vote for that. Which is true, and is a statement about the current membership rather than about the community. It describes who is in the room, not what the rules permit.
Membership turns over. A principle held by everybody in year three is held by a majority in year nine and by a large minority in year fifteen — not because anybody changed their mind, but because different people arrived. At no point does anybody betray anything. The protection simply evaporates, quietly, through ordinary intake.
The second reason it hides: a community with one decision process cannot see the distinction. If the guest policy and the founding purpose are amended by the same procedure, there is no visible difference between them, and nothing prompts the group to ask whether there should be. The absence of a constitutional tier is not experienced as a gap. It is experienced as simplicity.
What to check
Ask what could not be changed by a simple majority tomorrow. Then check the agreements for whether that is actually true. The gap between the two answers is the exposure, and it is usually total.
Try to find the amendment rule. Not for a policy — for the founding document. Most communities discover their agreements do not describe how they themselves are changed, which means they are changed by whatever process is at hand.
Ask the newest members what they think is permanent. If their list differs from the founders’ list, the group already has two constitutions and only one of them is written.
If it is already happening
Write the short list first. Not a constitution — a list. The three to six things this community exists for and would not survive losing. Communities routinely find this takes an evening and produces a much shorter list than anyone expected, which is itself useful.
Then attach a higher bar to that list, and only that list. A supermajority, a longer deliberation window, an objection period, a second vote at a later meeting — the specific mechanism matters less than that it differs from the ordinary one. Applying constitutional ceremony to everything is the failure at the other end, and it produces a community that cannot decide anything.
Include the amendment rule in what is protected. A high bar that can be lowered by an ordinary vote is not a high bar. This is the step most often missed, and it is the one that makes the rest hold.
Expect resistance from an unexpected direction. Some members will read this as distrust of the group’s future self, which is exactly what it is — and that is the point. You are protecting the community from a membership that does not exist yet, and the current membership is not the one at risk.
What prevents it
An invariants register: the things that may not be changed by ordinary decision, listed explicitly, with a stated constitutional process for changing them and the amendment rule inside the protected set.
Sources & further reading
- 1 RCOS stress test — Unprotected Core Invariants — the specification this page puts into plain language
- 2 RCOS Core — Layer 0: Identity & Scope — the invariants register, and what may never be overridden
- 3 Decision tiers — operational, strategic, constitutional — and why the unclear case defaults upward
Written by EcoHubs members, with AI assistance for drafting and editing, and reviewed by a person before publication. Facts are checked against the sources listed; anything we could not verify is marked. How this is written
The specification
This page is the plain-language version. RCOS publishes the stress test itself — the failure pattern, what is being tested, and what a compliant community would have in place.
RCOS stress test — change-emergencies/unprotected-core-invariants
Terms used here
- Agreements
- The written rules a community has consented to. Distinct from values: agreements say what happens, and what follows when it does not.
- Decision tiers
- Sorting decisions by what they cost to get wrong, and giving each class its own method and timeline.
- Drift
- The slow failure where nothing breaks. Agreements stop being read, shared habits thin out, and nobody ever decided any of it.
- Ratification
- A hold between a proposal passing and it taking effect, during which the result is confirmed before it becomes real.
These travel together
Failures are rarely alone. If this one is familiar, check the others from the same lesson before concluding you have found the whole problem.
- The emergency measure that stayed
Decided fast because it had to be, never reviewed, and now it is what the community does — with a precedent attached.
- A community that forgot why
The rule survives and the reason does not — so nobody can tell whether it still earns its place, or which version is even in force.
- Experiments with no way back
A trial that quietly became the arrangement — because nobody wrote down when it ended or what would count as it failing.
- Sub-groups with undefined autonomy
A community grows into parts, and nobody says what the parts may decide — so each one improvises a constitution and discovers later they do not match.
- Governance with no path to change it
The rules can no longer be changed, so people stop trying — and the community loses its members quietly instead of loudly.