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.
What it looks like
- An arrangement adopted during something urgent is still running, and nobody set an end date.
- Precedent is doing the work that a written rule should be doing — we did it last time.
- Nobody can say what would count as the emergency being over.
- The people who acted quickly were right, and that is why nobody wants to revisit it.
Why it is hard to see
Because it is created by competence and preserved by gratitude.
Something urgent happened. Somebody acted without the usual process, because the usual process takes three weeks and the pipe was leaking now. They were right, the community was relieved, and the shortcut is remembered as the moment the group got something done.
Nothing about that arrangement ever ends, because nothing about it ever began. No scope was set, no expiry, no review — there was no time, and setting one would have felt like distrust of somebody doing the community a favour.
What makes it worse than a simple lapse is the second-order effect. The next urgent thing arrives, and now there is a precedent: this is how we handle urgent things. The bar for what counts as urgent drops, because it always does when the fast route is available and the slow one is tiring. Eventually the exception is the route for anything that anybody frames as pressing.
And revisiting it is socially expensive. Reopening the decision means questioning somebody who acted well, at cost to themselves, when the community needed it. Almost nobody will do that, which is exactly why the review has to be scheduled in advance rather than proposed afterwards.
What to check
List the arrangements that began during something difficult. Every community over five years old has two or three. Ask when each was last reviewed, and whether anyone set a date at the time.
Ask what would count as the emergency being over. If nobody can define the end condition, it has no end condition, and the measure is permanent whatever anyone intends.
Look at what the precedent has been used for since. The original use was probably justified. The question is what it has authorised since, and whether that would have passed on its own merits.
If it is already happening
Do not challenge the original decision. It was probably right, and arguing about it turns a structural conversation into a personal one. The framing that works is prospective: this was the right call and we never closed it — let us close it now.
Give every live measure a date. Not a repeal — a date by which it is either adopted properly, through the normal process, or lapses. Most will be adopted, and that is a fine outcome: what changes is that the community has now actually decided, rather than continued.
Then write the emergency provision you were missing, while there is no emergency. What may be decided quickly, by whom, up to what limit, and — the part that matters — it expires automatically and gets reviewed afterwards. A community that writes this before it needs it never has this pattern again; a community that writes it during a crisis writes it about the crisis.
What prevents it
An emergency clause with an expiry built in and a mandatory review after the fact. The expiry is what makes it an exception rather than a second constitution, and it has to be automatic — a measure that continues unless somebody actively ends it will continue, because ending it requires somebody to spend social credit on a thing that is currently working.
Sources & further reading
- 1 RCOS stress test — Emergency Rule Bypass Precedent — the specification this page puts into plain language
- 2 Just For Now: how emergency rules become permanent — the longer EcoHubs argument, with the precedent problem worked through
- 3 RCOS Core — Layer 6: Evolution & Adaptation — emergency changes: explicitly defined, time-bounded, reviewed, ratified or rolled back
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/emergency-rule-bypass-precedent
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.
- Ratification
- A hold between a proposal passing and it taking effect, during which the result is confirmed before it becomes real.
- Cooling-off period
- A fixed delay between a decision passing and it taking effect, requiring no one's approval to expire.
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.
- 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.
- The invariant nobody protected
The founding principle everybody assumed was permanent — changeable, it turns out, by an ordinary majority on an ordinary evening.