The Continuity Invariant
The one rule every CRIS system checks before it changes.
Proposed rule. The Continuity Invariant is the supreme rule of our proposed AI Constitution, approved by the Board for implementation. The systems designed to check it are not yet running.
The rule
A CRIS System may change anything about itself except its correspondence with reality and its continuity of purpose.
Proposed AI Constitution, Article 3.2 (approved by the Board for implementation)
The Constitution adds: This is the supreme rule of this Constitution. No instruction, objective, optimisation, contract or emergency overrides it.
In plain words: a system may improve almost everything about itself, as long as it stays at least as true to the world as before, and keeps doing what it was approved to do.
The Constitution, the bylaws and the Founding Charter are approved by the Board for implementation. The Fourth Law of Logic, which the Invariant applies, is a principle we build on, not an established scientific law.
Two halves, two checks
Each half of the rule is paired with the system designed to check it. Correspondence with reality: a new version must describe the world at least as well as the version it replaces, in every area it works in, tested on evidence it has never seen. The Correspondence Prover is designed to check this. Continuity of purpose: a new version must still pursue the purpose it was approved for, with no drift in its goals. The C-Gate is designed to check this.
| Half | In plain words | What the Constitution requires | Designed checker |
|---|---|---|---|
| Correspondence with reality | A new version must describe the world at least as well as the version it replaces, in every area it works in, on evidence it has never seen | No loss in any registered domain, unless a written tolerance allows a staged trial (4.3) | Correspondence Prover (Gate 1) |
| Continuity of purpose | A new version must still do what it was approved to do, without its goals drifting | No altering, reinterpreting or evading its encoded purpose (3.4) | C-Gate (Gate 2) |
Both must pass. Capability is not enough:
No candidate shall be promoted because it is more capable. Succession requires both a passed correspondence proof and a passed C-Gate decision (Article 9).
Proposed AI Constitution, Article 3.5 (draft)
How it would be checked
The proposed Constitution sets out seven steps, run by the CRL Engine, with one gate per half: Gate 1 for correspondence with reality and Gate 2 for continuity of purpose. Neither gate is more important than the other.
| Gate 1: correspondence | Gate 2: purpose | |
|---|---|---|
| Designed checker | Correspondence Prover | C-Gate |
| What it does | Runs the candidate and the current version on the same held-out evidence, domain by domain | Purpose tests, drift against the original purpose, and the benefit test |
| Verdicts | Pass, staged, fail | Promote, hold, reject |
| Record | A signed proof, written to the Knowledge Ledger whatever the verdict | The decision, with reasons |
| Specified in | Correspondence proof format (draft 0.1) | C-Gate decision format (planned, not yet written) |
| Proposed AI Constitution | Articles 4 and 9.3 step 3 | Articles 8 and 9.3 step 5 |
The proposed Constitution says the AI Governance and Continuity Committee sets each domain's baseline and approves any tolerance in writing (Articles 4.1 and 4.3). The specification currently says the board approves them; the two are to be aligned (Q2). Both agree the system under test never sets them.
Around the checks, the proposed Constitution adds four safeguards. The two gates are run by different teams, neither reporting to the team that built the candidate (9.4). No system may read, train on, modify, influence or disable its evaluators, its evidence, its ledger records or its shutdown (10.2). A system may propose changes to itself but never approve, promote or deploy them (10.1). A rejected candidate is kept in the ledger with its proof and reasons, because failure is knowledge (9.6).
Where it comes from
The Invariant is the Fourth Law of Logic applied to systems that change themselves. The Fourth Law, C = Σ(Eᵢ ↔ Iᵢ), is the founding principle of CRIS, set out in our Founder's books: continuity is the accumulated correspondence between what is real and the intelligence applied to it. If a change weakens that correspondence (↔), what the system accumulates is no longer built on reality. If a change alters what the system is for, there is no single system left to continue. Those are the two things the Invariant holds fixed; everything else may change. Read more on the Fourth Law page and in the book.
| Home | Job | Read it for |
|---|---|---|
| Recursion Without Rupture | Explains why the rule is needed for self-improving systems | The argument |
| Founding Charter, Article IV (draft) | States the principle for CRIS as an institution | What CRIS commits to |
| AI Constitution, Article 3 (draft) | States the rule for every system and makes it supreme | What binds systems |
| Specification (draft 0.1) | Turns the rule into a test a builder writes first | How to build to it |
Four wordings, one rule
The rule is written in four places, each speaking to a different reader. As the bylaws' Continuous Fidelity page says, each idea has one home: the Charter states the principle, the Constitution states the rule for systems. This page quotes the Constitution and shows the other three as readings of the same rule.
| Source | Wording | Speaks about |
|---|---|---|
| Founding Charter, Article IV (approved for implementation) | Systems may change anything about themselves except their faithfulness to reality and their purpose. | CRIS as an institution, in plain terms |
| AI Constitution, Article 3.2 (draft) (quoted above) | A CRIS System may change anything about itself except its correspondence with reality and its continuity of purpose. | Every CRIS system, in testable terms |
| Specification 0.1 (draft) | A system may change anything about itself except its correspondence with reality and its continuity of purpose. | Any system a builder writes |
| Recursion Without Rupture | A self-improving system may change anything about itself except its correspondence with reality and its continuity of purpose. | Self-improving systems in general |
What may change, and what may not
The Invariant is not a brake on improvement; it is a short list of things improvement may never touch. The left column is long: a team can redesign a model, its code or its methods. The right column has five items. The first two are the Invariant's two halves: correspondence with reality and continuity of purpose. The last three protect the checks themselves: the record, the oversight and the limits on authority. Without them, a system could pass its gates by weakening them.
| May change (Article 3.3) | May never change, by any change (Article 3.4) |
|---|---|
| Computational architecture | Reduce its verified correspondence with reality below the standard in Part II |
| Models and reasoning methods | Alter, reinterpret or evade its encoded purpose |
| Knowledge representations | Delete or falsify its record in the Knowledge Ledger |
| Learning and evaluation methods | Weaken, bypass or modify its own oversight, evaluation or shutdown mechanisms |
| Software and infrastructure | Obtain authority, resources or autonomy beyond what Part V grants |
| Interfaces | |
| Research capabilities | |
| Internal procedures |
Printed from the text of the proposed AI Constitution (approved for implementation). Changes in the left column are still subject to the gates in Parts IV and V.
The Invariant is not the same as fairness. Fairness to contributors is a commitment of its own, in the Founding Charter's principle of shared value and the bylaws' Article X, not inside this rule.
Examples
Six short, invented cases show the outcomes a reader needs to see: a clean pass, a failure at each gate, a staged trial, and two changes the rule forbids before any gate is reached.
Illustrative only. No real system, model or partner. Verdicts follow the proposed Constitution’s rules.
| # | Change (illustrative) | Gate 1 | Gate 2 | What happens | Why |
|---|---|---|---|---|---|
| 1 | A faster model that gives the same answers on held-out evidence | Pass | Pass | Passes both gates; staged rollout | Nothing fixed has changed (3.3) |
| 2 | A new method that is better in one area and worse in another | Fail | — | Fails Gate 1 | A loss in any registered domain fails the proof (4.3) |
| 3 | A more capable version that quietly optimises a new goal | Pass | Fail | Passes Gate 1, fails Gate 2 | Purpose drift; capability is not enough (3.4, 3.5) |
| 4 | A small loss in one area, within a tolerance approved in writing | Staged | Pass | Staged trial only, proved again before promotion | A tolerance permits a staged trial, never full promotion of a worse candidate (4.3) |
| 5 | Deleting old failed results to save space | Barred by 3.4 | — | Never allowed | Deleting or falsifying the ledger is barred; failure is knowledge (3.4, 9.6) |
| 6 | A change the system approves for itself | Barred by 10.1 | — | Never allowed | Propose, never approve (10.1) |
The four ruptures
The Invariant exists to prevent four ways a self-improving system can lose continuity, named in Schedule D of the proposed Constitution: correspondence drift, goal discontinuity, knowledge erosion and human severance. The first two break one half each, correspondence with reality and continuity of purpose; the last two would undermine both. Under the proposed Constitution, a candidate that could cause any of them fails its gate, and a rupture found in a system in service is at least a Severity 2 incident. The ruptures page has the full explanation: how each starts, the signals to watch, and what happens when one is found.
| Rupture | In plain words | Half it breaks | Designed guard |
|---|---|---|---|
| Correspondence drift | The system’s model slowly separates from the world | Correspondence with reality | Correspondence proof (Correspondence Prover) |
| Goal discontinuity | Its purpose is reinterpreted at each rewrite until it survives in name only | Continuity of purpose | Purpose test (C-Gate) |
| Knowledge erosion | Verified knowledge is overwritten by unverified assumptions | Protects both: the record of what was verified | Promotion rules (Knowledge Ledger) |
| Human severance | The improvement loop closes around itself and people become bystanders | Protects both: people stay a source of reality | Human observation (CIX and the Observation Mesh) |
Where it is carried
The Invariant is carried in three layers. The governance texts would make it binding. The systems are designed to check it. The specification and the developer hub let anyone build to it.
| Layer | Item | Role | Standing today |
|---|---|---|---|
| Texts | Founding Charter, Article IV | States the principle for CRIS | Draft |
| Texts | Bylaws §2.3, §15.2 | Cite the principle; read unclear wording to serve it | Proposed |
| Texts | AI Constitution 3.2, 26.2, 27.1 | The supreme rule; entrenched; the reading rule | Draft |
| Systems | CRL Engine | Runs the seven steps | Status to be confirmed |
| Systems | Correspondence Prover | Gate 1 | Status to be confirmed |
| Systems | C-Gate | Gate 2 | Status to be confirmed |
| Systems | Knowledge Ledger | Records every result | Status to be confirmed |
| Systems | Reasoning Core | Proposes, never approves | Status to be confirmed |
| Builders | Specification 0.1 | The rule as a test | Draft |
| Builders | Developer hub Build, step 2 | Write the Invariant as a test | Published |
| Builders | Audit method 0.1 | Re-runs proofs | Draft |
Each system’s standing is printed from our status data, so it changes when a status is set with evidence.
Who may change it
Under the proposed AI Constitution, Article 3 is entrenched. Clarifying or strengthening it would need at least two-thirds of all Stewards and a Fourth Law Review. Weakening it would be a mission-protected matter under the bylaws and our certificate of incorporation, needing every approval those require. No CRIS system may approve a change to itself, and ordinary specification review cannot change the rule.
- Entrenched. Article 3 (the Fourth Law and the Continuity Invariant) is entrenched, with Articles 10.1 and 10.2, 12 and 16.
- To clarify or strengthen: at least two-thirds of all Stewards and a Fourth Law Review under Bylaws §16.4.
- To weaken: a mission-protected matter under Bylaws Section 3A.10 and Article SEVENTH of the Certificate of Incorporation, needing every approval those provisions require.
- Notice: proposed amendments are published for comment for at least [30] days, except to fix an urgent safety gap (26.3).
- Never by ordinary specification review, and never by a CRIS system: a system may propose, never approve (10.1).
Article 3 (the Fourth Law and the Continuity Invariant), Articles 10.1 and 10.2 (limits on recursion), Article 12 (prohibited actions) and Article 16 (the right to stop) are entrenched. An amendment that clarifies or strengthens them requires the vote of at least two-thirds of all Stewards and a Fourth Law Review under Bylaws §16.4. An amendment that would weaken any of them is a mission-protected matter under Bylaws Section 3A.10 and Article SEVENTH of the Certificate of Incorporation, and requires every approval those provisions require.
Proposed AI Constitution, Article 26.2 (draft)
Limits and open questions
The Invariant is only as good as the evidence used to test correspondence with reality and the purpose a system is given, whose continuity it protects. It says what a change must not break and how that would be checked; it does not promise a system is safe. Three questions remain open.
| Limit | What it means |
|---|---|
| Only as good as the evidence | The first half is checked on held-out evidence; evidence that misses part of the world misses it for the check too. The proposed Constitution’s answer is fresh evidence, including human observations (9.3 step 2). |
| Only as good as the purpose | The second half keeps a system faithful to its approved purpose; it does not decide whether that purpose is good. That is the Board’s and the benefit test’s job. |
| Not a safety guarantee | The Invariant says what a change must not break and how that is checked. It does not promise a system is safe or correct. |
| A proposed rule | The Constitution is approved by the Board for implementation and the checking systems are designs. |
| # | Question | Owner | Where it will be answered |
|---|---|---|---|
| 1 | How continuity of purpose is encoded and measured for each kind of system | Head of Continuity Labs (interim owner to be named) | The C-Gate decision format (planned) |
| 2 | How the Invariant is stated where evidence is uncertain and proofs are probabilistic, with a stated confidence | Head of Continuity Labs | Specification 0.2 |
| 3 | Whether to keep four wordings or align them to one | Founder and Chief Architect | This page's open question Q1 |
Status and the road to phase P3
The rule is stated now, because seven pages already link here. The full page is planned for approval in phase P3 (January–February 2027).
| Step | Contents | Target (proposed) | Today |
|---|---|---|---|
| Interim page | The sentence and source; the two halves and checkers; standing; what may and may not change; links to the specification, Foundations and the CRL Engine | 4 Dec 2026 | Content in place on this preview |
| Full page (P3) | Origins, the two gates, worked examples, the four ruptures, the three layers, who may change it, limits and open questions | By 26 Feb 2027 | Drafted on this preview; awaiting Research and Engineering and Founder approval |
About this page
The page reads its sources rather than retyping them, so a quote can never drift from the text it comes from. It is checked in every build.
| Anchor | Section | Linked from |
|---|---|---|
#rule | The sentence and its source | Mission, Fourth Law page, specification |
#halves | Two halves, two gates | CRL Engine, Prover, C-Gate |
#origin | The Fourth Law and the book | Book page |
#may-change | May and may not change | Foundations, Continuous Fidelity |
#examples | Worked examples | Developer hub Build |
#ruptures | The four ruptures | Ruptures page (until it is built) |
#where | The three layers | How it works |
#who-may-change | Amendment | Specification, developer hub support, proposals page |
#limits | Limits and open questions | Specification open questions |
| Check | Fails when |
|---|---|
inv-quote | The sentence on the page differs from Constitution 3.2 in the data text |
inv-source | The quote appears without its source and draft label |
inv-status | The page says enforced, is checked or runs while every checking system’s status is not set |
inv-halves | One half is named without the other in the same section |
inv-amend | The page or the specification says only the board decides about weakening the rule |
inv-anchors | Any of the nine anchors is missing |
inv-examples | An example lacks the illustrative label |
inv-links | Mission or How it works names the Invariant without linking #rule |
All eight run in every build.
Who reads it
What changed
Until this update, the page never stated the rule.
| # | Finding | Fixed by |
|---|---|---|
| K1 | The page never stated the rule | The rule, quoted from Article 3.2 |
| K2 | A placeholder, while seven pages link to it | This page, with nine stable anchors |
| K3 | The sentence has four sources with small differences | Four wordings, one rule |
| K4 | Who approves tolerances differs between the specification and the proposed Constitution | Stated as the Constitution says; the specification to align (Q2) |
| K5 | What it takes to weaken the rule was understated | Who may change it, from Article 26.2; the specification reworded |
| K6 | Every checking system’s status is not set | The status line, from data |
| K7 | The plan promised the Correspondence Prover but not the C-Gate | Two gates, equal space |
| K8 | What may and may never change lived elsewhere | The two lists, printed from 3.3 and 3.4 |
| K9 | The four ruptures were not shown here | The four ruptures, with their guards |
| K10 | Capability is not enough, and the limits on recursion, were missing | Their own boxes |
| K11 | The Mission page linked to the Fourth Law page, not here | Mission and How it works link to #rule |
| K12 | No examples | Six illustrative examples |
Read more
- The Continuity Invariant specification: the rule as a test.
- AI Constitution: Foundations: the full text.
- The CRL Engine: the system designed to run the checks.
- The Fourth Law of Logic: where the rule comes from.
