Changes that cannot be undone

Every rule in a community was written by people responding to a situation. Ten years later some of those situations are gone, some of the rules are load-bearing, and almost nobody can tell which is which.

That is the subject of this lesson: not what the rules are, but how they move — and the fact that most communities have no account of their own movement at all.

The five

• The invariant nobody protected — the founding principle everybody assumed was permanent, changeable by an ordinary majority on a Tuesday
• The emergency measure that stayed — decided fast because it had to be, never reviewed, now precedent
• Governance with no path to change it — the opposite failure, and the one that produces departures rather than arguments
• Experiments with no way back — a trial that quietly became the arrangement, because nobody set an end date
• A community that forgot why — the rule survives, the reason does not, and nobody can evaluate either

And one more that RCOS does not catalogue: sub-groups with undefined autonomy, which is what happens when a community grows into parts without deciding what the parts may decide.

Why drift is the hardest of them

Four of these announce themselves eventually. Drift does not, and it is the one most communities are actually living in.

Nobody notices a slow forgetting by paying closer attention, because there is no moment to notice. The agreements stop being read, then stop being taught, then describe a place that no longer exists — and every step of that is a non-event.

Which is why vigilance is the wrong defence and bookkeeping is the right one. A community that can say which version is in force, when it last changed, and who decided it has turned a feeling into a check anybody can run.

The difference that makes is mostly social. Without a current text, raising drift means saying I think we have lost something — a criticism of everyone present, and heard as one. With it, the same observation is that the practice and the document disagree. A discrepancy, pointed at rather than levelled, and the sort of thing a group can look into without anyone having to be at fault.

Note how little would have prevented it: an adoption record and a summary of changes. Two fields.

Is there a way back?

Five changes a community has made. Some were called temporary, some were called experiments, and one was not called anything. For each, decide whether the community could actually return to how things were — not whether it should.

1. Three years ago the group suspended the two-week notice rule for guests, "while the building work is on". The building work finished last spring.

On paper only — the decision could be reversed, the situation cannot correct answer Right, and the trap is that reversing it looks trivial: one vote, and the old rule is back. But three years of practice is now the normal way of doing things, so reinstating the rule would not be experienced as returning to the agreement — it would be experienced as a new restriction, proposed by somebody, on everybody. That is how an emergency measure becomes the constitution without ever being adopted. Yes — there is a date and the old arrangement still exists There is no date. "While the building work is on" sounded like one at the time, which is precisely why nobody set a real one, and the condition it was tied to passed a year ago without anything happening. There is nothing to reverse — no change was ever recorded A suspension was decided, so there is a decision on the record to point at. That makes this recoverable in a way the genuinely unrecorded cases are not.

Where this comes from

2. The community agreed to try shared childcare for one term. There is a review date in the diary, and the previous arrangement is still running alongside it.

Yes — there is a date and the old arrangement still exists correct answer Right, and both halves are load-bearing. The date means somebody has to actively decide to continue rather than merely fail to stop. Keeping the old arrangement running is the expensive half and the one usually skipped — a way back that has been dismantled is not a way back, however clearly the minutes say the trial may end. On paper only — the decision could be reversed, the situation cannot Nothing has been dismantled and no facts have been created that would outlast the term. This is what a time-bounded experiment is supposed to look like. There is nothing to reverse — no change was ever recorded It was recorded, with an end date, which is more than most arrangements described as trials ever get.

3. Six households were allowed to opt out of common meals "as an experiment". Four have since converted their dining rooms into other things.

On paper only — the decision could be reversed, the situation cannot correct answer Right. The vote is still there to be retaken and the rooms are gone. An experiment that lets people build on its outcome has stopped being an experiment, whatever the minutes call it — and the households would be right to feel that ending it now is a change being made to them rather than a trial concluding. Yes — there is a date and the old arrangement still exists There is no date in the scenario, and for four households the old arrangement no longer physically exists. Both of the things that make a trial reversible are missing. There is nothing to reverse — no change was ever recorded A permission was granted and can be found. The problem is not the record — it is that the situation moved further than the decision did.

Where this comes from

4. The membership fee is named in the founding charter. Last month the group changed it by ordinary majority at a Tuesday meeting, and nobody present raised the charter.

On paper only — the decision could be reversed, the situation cannot correct answer Right, though the reason is unlike the others: the fee could be put back tomorrow, and what cannot be put back is the discovery that a founding document can be amended by an ordinary majority on a Tuesday. Everyone now knows it, and the next thing in the charter is protected only by nobody happening to want it changed. An invariant is a rule about which rules a Tuesday meeting may reach. There is nothing to reverse — no change was ever recorded The change was made and minuted. What was not recorded is the collision with the charter, because nobody in the room noticed there was one. Yes — there is a date and the old arrangement still exists The old figure is recoverable from the charter, so the fee itself is easy. The precedent is the part with no way back, and it is now available to anybody who wants it.

Where this comes from

5. A revised version of the work agreement appeared in the shared folder with a new number. There is no adoption record, no summary of what changed, and the previous version was deleted to avoid confusion.

There is nothing to reverse — no change was ever recorded correct answer Right, and this is worse than an unpopular change, because the community cannot establish what it used to require or whether the new text was ever agreed. Everything downstream — every rule and decision citing the agreement — inherits the ambiguity. Deleting the old version to avoid confusion destroyed the only evidence of what the community previously thought, which is exactly what you need when somebody asks why a rule exists. On paper only — the decision could be reversed, the situation cannot There is no decision to reverse. That is the distinction worth holding: a bad change can be revisited, and an unrecorded one leaves nothing to revisit. Yes — there is a date and the old arrangement still exists Neither is true — the old text was deleted and no adoption date exists. Two fields, an adoption record and a summary of changes, would have prevented the whole situation.

Where this comes from

If it is already happening

Establish the present before you reconstruct the past. Which documents are in force, as of today, agreed by whoever is in the room. Not their history — their status. This can be done in one meeting and it stops the bleeding.

Then date everything from now on. A change record with four fields: what changed, who decided it, under which rule, and from when. A community with two clean years and a murky past is in a far better position than one that spent six months excavating and gave up.

Keep the superseded versions. Deleting the old text destroys the only evidence of what the community used to think, which is what you need when somebody asks why the rule exists.

And review the emergency measures specifically. Every community has two or three arrangements adopted quickly during something difficult and never revisited. List them, and give each one a date by which it is either ratified properly or ends.

What prevents it

A change protocol that says how a rule changes and who decides, a version history that makes “which version is in force” answerable, and a learning log so that what a difficult year taught does not leave with the people who lived it.

All three are boring. That is the point — this is the one failure class where the defence is entirely clerical, and a community that finds that beneath it will forget why it exists.

Sources & further reading

1. 1 RCOS stress tests — Change & Emergencies — the five documented patterns this lesson covers, in specification form
2. 2 RCOS Core — Layer 6: Evolution & Adaptation — change mechanisms, version history, time-bounded experiments and the learning log
3. 3 Just For Now: how emergency rules become permanent — the longer EcoHubs argument about temporary measures that outlive their emergency
4. 4 Resilience & why communities fail — drift as one of the six recurring patterns, and why it is the only one that does not feel like anything

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