Invariants Register

Active Invariants

What must never happen here, whatever the circumstances or the majority?

RCOS clauses 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6

2.3.1 Invariants are constraints that define what MUST NOT be violated while they are in force.
2.3.2 Invariants MUST be explicitly listed and documented.
2.3.3 Invariants MUST apply across all layers of RCOS.
2.3.4 No decision, role, process, or emergency measure MAY override an invariant.
2.3.5 If a conflict arises between an invariant and any other rule, the invariant MUST prevail.
2.3.6 Invariants MAY only be changed or removed through a constitutional change process as defined in Layer 2 and Layer 6.

Why are invariants unoverridable?

Invariants are the hard floor of the system — the things that must hold true even under pressure, emergency, or a popular vote. If any decision, role, or crisis measure could override them, they would stop being constraints and become preferences. Listing them explicitly and binding them across every layer is what makes the governance system trustworthy under stress, not just on calm days.

How to fill this in

Each invariant is a hard constraint. Keep them few, specific, and absolute — phrased so that any violation is unambiguously identifiable. Common categories: purpose protection, authority traceability, exit rights, ideological neutrality, non-extraction, safety primacy.

ID	Invariant	Added	Decision record
INV-001	<Invariant statement, e.g. The primary purpose may never be overridden by any operational or strategic decision, role, or emergency measure.>	<YYYY-MM-DD>	[link]
INV-002	<Invariant statement, e.g. Authority must always be explicit and traceable to the governance system — no person or role may hold or exercise undeclared authority.>	<YYYY-MM-DD>	[link]
INV-003	<Invariant statement, e.g. Exit from the community must always be possible and must never be blocked, penalised, or made conditional beyond what is defined in Layer 1.>	<YYYY-MM-DD>	[link]
INV-004	<Invariant statement.>	<YYYY-MM-DD>	[link]
INV-005	<Invariant statement.>	<YYYY-MM-DD>	[link]
INV-006	<Invariant statement, e.g. Physical, psychological, and child safety always override participation rights, role continuity, and reputational concerns.>	<YYYY-MM-DD>	[link]

What to cover

What must never happen here, even in an emergency or after a popular vote? Write each as one clear sentence.
For each one: how would anyone know, without argument, that it has been broken?
Does each one hold everywhere — in membership, money, roles, safety and how we decide — or have we worded it so it only covers one area?
When a decision, a role or any other rule clashes with one of these, do we say plainly that the invariant wins and the other gives way?
Is the list short enough that each one is truly absolute — and is anything on it really just a strong preference?
Do we agree these can only be changed through our highest-level (constitutional) change process, never by an ordinary decision?

Examples

No one may be prevented from leaving the community, or punished for leaving. No person or role may use authority that is not written into our governance documents. The physical safety of any person, and above all of a child, comes before anyone's role, reputation or participation. These hold for every rule, role, decision and emergency measure we have; where anything conflicts with them, they prevail, and they change only through our constitutional change process.

Examples, not recommendations. Your answers will be your own.

Invariants Register

Download this template

Active Invariants

Ratification Record