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.
Active Invariants
RCOS clauses: 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.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 | [link] | ||
| INV-002 | [link] | ||
| INV-003 | [link] | ||
| INV-004 | [link] | ||
| INV-005 | [link] | ||
| INV-006 | [link] |
Ratification Record
- Adopted:
- Decision type: Constitutional
- Version:
- Decision record: