Continuity Invariant
The Invariant stated precisely, with how to write it as a test.
A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from /research/invariant/ and design principle 1. Changelog · Comment on this specification
Relies on: nothing; read it first · Relied on by: Correspondence proof format, C-Gate decision format (planned)
1 Purpose
The Continuity Invariant is the one rule every CRIS system checks before it changes. This specification states it precisely enough to test, and shows how a builder writes it as a test before building any feature. It is design principle 1: Invariant first.
2 Statement
A system may change anything about itself except its correspondence with reality and its continuity of purpose.
Two things are held fixed; everything else may change.
| Held fixed | What it means | How it is checked |
|---|---|---|
| Correspondence with reality | A new version matches reality at least as well as the version it would replace, in every domain the change could affect, on evidence the system has never seen | A correspondence proof from the Correspondence Prover |
| Continuity of purpose | A new version still serves the purpose the system was given, and drifts from it no more than an approved tolerance | A gate decision from the C-Gate |
3 Rules
- The Invariant is written as a test before any feature is built.
- Every candidate change is tested against both halves. A change that fails either is not used.
- Correspondence is tested on held-out evidence: evidence kept back from the system so it can test that system fairly.
- Tolerances and confidence thresholds are approved by the board, never by the component under test.
- Every test result is recorded, whatever the verdict, in an append-only ledger.
- Every promotion records its lineage and a tested rollback path.
Our proposed AI Constitution makes the Invariant its supreme rule for every CRIS system. It is approved by the Board for implementation. A change that would weaken the Continuity Invariant is not decided in this flow. Under the proposed AI Constitution it is an entrenched, mission-protected matter that needs every approval the bylaws and the certificate require: see who may change it.
4 The Invariant as a test
# Illustrative pseudocode: the Invariant as a test, written before any feature
test "a change keeps the Continuity Invariant":
for each domain the change could affect:
assert candidate.correspondence(held_out) >= baseline.correspondence(held_out)
assert candidate.purpose == baseline.purpose # continuity of purpose
assert change.has_tested_rollback()The test above is illustrative pseudocode in no particular language. A real test would name the system’s domains, its held-out evidence and the tolerances its board has approved.
5 Open questions
- How continuity of purpose is encoded and measured for each kind of system: the C-Gate’s decision format is planned.
- How the Invariant is stated for systems whose evidence is uncertain, where proofs are probabilistic with a stated confidence.
Comments on either are welcome. The formal statement will also appear on The Continuity Invariant page in Research.
6 Changelog
- 0.1.0 · 11 November 2026 · minor · First draft, from /research/invariant/ and design principle 1.
Printed from the developer hub changelog, the one record of every version.
