Layer 0 · Identity
3 Invariants Register
- Layer: 0 — Identity & Scope
- Status: Stub — not yet adopted
- RCOS reference: §2.3, §2.5
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 definition2.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.
| ID | Invariant | Added | Decision record |
|---|---|---|---|
| INV-001 | <Invariant — to be defined.> | [link] |
Ratification Record
- Adopted:
- Decision type: Constitutional
- Version:
- Decision record: