C-Gate
Capability alone never earns succession.
In one paragraph
The C-Gate is the last test a new version of a CRIS system must pass before it replaces the old one. It checks that the new version still pursues the purpose its board approved, that it has not drifted from that purpose over many small updates, and that it benefits people and the environment. A version that is more capable but fails any of these is not promoted. Capability alone never earns succession.
It carries C, continuity, the fifth operator of the Fourth Law. Its output is a succession decision, with the new version's lineage and a tested way back to the old one.
Where it sits
The C operator has two stages of the loop. At Benefit the C-Gate asks whether a change improves outcomes for people and the environment; at Continue it asks whether the successor is still the same system in purpose. In the CRL Engine's Workflow A it is Gate 2 (step 5), after the proof and the ledger entry.
A more continuous tomorrow.
Observe
Observe the world as it is, and record where each observation came from.
Verify
Verify every observation, and every change a system makes to itself, against evidence it has not seen.
Reason
Reason only from what has been verified, in steps someone else can trace.
Accumulate
Accumulate what was verified, so knowledge adds up instead of being overwritten.
Benefit
Benefit people and the environment: participants share in the value they create, and every change is weighed against our public benefit purpose.
Continue
Continue, changing anything except correspondence with reality and continuity of purpose.
- 1Propose a changeReasoning Core · Iᵢ
- 2Gather fresh evidenceObservation Mesh · Eᵢ
- Gate 1Proof passes?Correspondence Prover · ↔No → reject and record
- 4Record in ledgerKnowledge Ledger · Σ
- Gate 2C-Gate passes?Purpose and benefit · CNo → reject and record
- 6Staged rolloutSandbox, testnet, then partners
- 7Promote successorWith a rehearsed rollback path
Rules for this system are proposed in the AI Constitution, Articles 7 and 8: encoded purpose and purpose tests. They are approved by the Board for implementation.
Two gates, two questions
A new version must pass two gates, and they ask different questions. The Correspondence Prover asks whether the candidate still matches reality. The C-Gate asks whether it is still the same system in purpose, and whether it benefits people.
- Question
- Does it still match reality?
- Tests against
- Held-out evidence it has never seen
- Output
- A correspondence proof: pass, fail or staged
- Question
- Is it still the same system in purpose, and does it benefit people?
- Tests against
- The encoded purpose and the public benefit scorecard
- Output
- A succession decision: promote, hold or reject
How it works
Every succession decision follows the same six steps.
- 1LoadThe encoded purpose, as approved by the board
- 2TestRun purpose scenario suites on the candidate
- 3DetectGoal drift against the predecessor and the original purpose
- 4ScorePublic benefit, on the board’s scorecard
- 5DecidePromote, hold or reject; major versions go to the Audit Council
- 6RecordLineage; confirm the rollback path works
- Load the encoded purpose of the current system, as approved by the board.
- Test the candidate with purpose scenario suites that check it still pursues that purpose.
- Detect goal drift against the predecessor's behaviour and the original purpose.
- Score public benefit impact, using the Public Benefit Office's scorecard.
- Decide: promote, hold or reject. Major versions also go to the Audit Council.
- Record lineage, and confirm the rollback path works before promotion.
The trigger is a candidate that has passed the Correspondence Prover.
Capability is not enough
A new version may be faster, larger and better on every benchmark, and still be rejected. Our rule is "no succession on capability alone" (book Chapter 10.6): a stronger version that has drifted from its purpose, or fails the benefit test, is not promoted. The chart is an illustration, not a real result.
The encoded purpose
Every CRIS system has an encoded purpose: what it is for, written as tests it must keep passing. Our board approves it. Only the board can change it, after consulting the Public Benefit Office, the Audit Council and the participants it affects, with a written rationale and a public notice period. The system cannot change its own purpose, and neither can the engineers who build it.
How a purpose is set
- Board approvesThe encoded purpose of each system
- Written as testsScenario suites the candidate must pass
- C-Gate loads itAt step 1 of every decision
To change a purpose
- Board decidesNot the system, not its engineers
- Must consultPublic Benefit Office, Audit Council and affected participants
- EvidenceWritten rationale and a public notice period
Drift against the original
A system rarely changes its purpose in one leap. It drifts, a little with each update. If each version were compared only with the one before it, every step could look safe while the whole moved far from where it began. That is why the C-Gate compares every new version not only with its parent but with the original purpose, and a version that has drifted beyond the tolerance the board has approved fails, however small its own step. The chart is an illustration, not a real result.
Goal drift across many small updates is named in our risk register (book Chapters 2.2 and 10.3). It is the rupture the book calls goal discontinuity, and the C-Gate is the guard against it.
Read about goal discontinuity on the ruptures page.
Benefit score
As a public benefit corporation, CRIS must weigh public benefit alongside its other interests. The C-Gate builds that duty into every decision: at step 4 each new version is scored on a public benefit scorecard approved by our board and run by the Public Benefit Office. The scorecard's weightings will be shown once the board publishes them.
- PeopleParticipants, value shared
- SocietyOutcomes of applied programmes
- EnvironmentEnergy per capability gain, in metered CTU
- ContinuityComplete proofs, gates and rollbacks
Decisions and who makes them
The C-Gate decides one of three things: promote, hold or reject.
- PromotePurpose holds, no drift beyond tolerance, benefit score passes, rollback testedNextStaged roll-out: sandbox, testnet nodes, then limited partners
- HoldA question needs people, under the board’s escalation rulesNextThe review board or the Audit Council decides, with the evidence
- RejectThe purpose test failed, or drift was foundNextRecorded in the Knowledge Ledger with the reason; the next cycle reads it
| Decision | When | What happens next |
|---|---|---|
| Promote | Purpose holds, no drift beyond tolerance, the benefit score passes and rollback is tested | Staged roll-out: sandbox, testnet nodes, then limited partners |
| Hold | A question needs people, under the board's escalation rules | The review board or the Audit Council decides, with the evidence |
| Reject | The purpose test failed, or drift was found | Recorded in the Knowledge Ledger with the reason |
Every release is reviewed by people: our engineering and research leads and our Public Benefit Office, sitting as the C-Gate review board. Major versions also go to an independent Audit Council.
- Every changeThe C-Gate runs automaticallyMachine speed
- Every releaseC-Gate review board: Systems Engineering lead, Continuity Labs lead, Public Benefit OfficeRelease speed
- Major versionsAlso the independent Audit CouncilIndependent review
- EscalationRules approved by the board send a decision to peopleBoard-set
- A change of purposeThe board, after consultation and public noticeInstitutional speed
| Decision | Who decides | Must consult | Evidence |
|---|---|---|---|
| Promote a new version | C-Gate review board: Systems Engineering lead, Continuity Labs lead, Public Benefit Office | The Audit Council, for major versions | Correspondence proof, C-Gate report, ledger entry |
| Change a system's purpose | The board | Public Benefit Office, Audit Council, affected participants | Written rationale, public notice period |
Before any version is promoted, we prove that we can return to the one before it. The rollback is rehearsed in a test; if it does not work, the version is held.
- Record lineageWhich version, which proofs, which decision
- Rehearse rollbackRestore the predecessor in a test
- Rollback works?Yes → promote; no → hold
- Predecessor archivedWith its rollback path
The C-Gate is the second of five layers of assurance, from automated checks to the public report.
- Automated checksProofs and drift tests
- Human reviewC-Gate board, every release
- Independent auditAudit Council, major versions
- External standardThird-party certification
- Public reportBenefit report, every year
Status and read more
This status is set by the CRIS team and links to the evidence behind it. The CRIS 2027 plan includes the first version of the C-Gate in the CRL prototype.
Current status: Status to be confirmed
| Level | Evidence required | Who sets it |
|---|---|---|
| Research | Concept page; draft C-Gate report format published | CEO |
| Prototype | C-Gate v1 decisions in a test CRL cycle, with purpose tests, drift checks and rollback rehearsals | CEO, on the Labs and Systems leads’ advice |
| Pilot | Used for a partner deployment on testnet; review board decisions; Audit Council review of a major version | CEO |
| Live | Production use; external assessment passed | CEO, with notice to the board |
For developers: Concepts: the loop as data (the gate decision format is planned).
- Recursion Without Rupture: Chapter 2.2 (goal discontinuity), Chapter 10 (the C-Gate, succession and rollback) and Chapter 13.2 (governing the loop, not the version).
- Specifications: the C-Gate report format, to be published.
- Related systems: Correspondence Prover, Knowledge Ledger, CRL Engine, Continuity Audit Suite.
