CRL Engine
A system may change anything about itself except its correspondence with reality and its continuity of purpose.
In one paragraph
The Continuity Recursion Loop (CRL) Engine is the core of every CRIS system. It lets a system improve itself (its methods, architecture, code and training) while making sure each new version still matches the world and still serves the purpose it was built for. The engine never promotes a change on its own: every candidate must pass two independent gates, every result is recorded, and every step can be undone.
The engine does not reason, observe or store knowledge itself. It coordinates the five operator systems around it and runs every candidate change through the same cycle, so that nothing is promoted on capability alone.
Where it sits
The CRL Engine runs the whole loop, not one stage of it. It calls a different CRIS system at each stage of the formula Eᵢ ↔ Iᵢ → Σ → C.
runs every stage
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.
| Symbol | Stage | System the engine calls |
|---|---|---|
| Eᵢ | Observe | Observation Mesh, and CIX for human observation |
| ↔ | Verify | Correspondence Prover (Gate 1) |
| Iᵢ | Reason | Reasoning and Redesign Core |
| Σ | Accumulate | Knowledge Ledger |
| C | Benefit and Continue | C-Gate (Gate 2), with lineage and rollback |
Rules for this system are proposed in the AI Constitution, Articles 9 and 10: the succession pipeline and the limits on recursion. They are approved by the Board for implementation.
The rule it enforces
The engine enforces one rule, the Continuity Invariant. A candidate change may alter anything about the system except two things: its correspondence with reality, checked by the Correspondence Prover, and its continuity of purpose, checked by the C-Gate. Capability alone never earns succession.
May change
- Architecture
- Code
- Methods
- Training data
- Speed
- Scale and form
May never change
| Test | Gate | What it checks | Book |
|---|---|---|---|
| Correspondence | Gate 1, Correspondence Prover | The candidate models held-out reality at least as faithfully as the current version, in every tracked domain | Chapter 8 |
| Purpose | Gate 2, C-Gate | The candidate still pursues the board-approved purpose, shows no goal drift, and passes the public benefit check | Chapter 10 |
How it works
Every proposed improvement goes through the same seven steps.
- 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
- Propose. The Reasoning Core proposes a change with a written hypothesis of what it improves.
- Gather fresh evidence. The Observation Mesh assembles held-out evidence the system has not shaped, including recent human observations from CIX.
- Prove correspondence (Gate 1). The Correspondence Prover tests the candidate against that evidence; contradictions are surfaced, not averaged away.
- Record. The result, pass or fail, is written to the Knowledge Ledger with the candidate's lineage.
- Pass the C-Gate (Gate 2). Purpose tests, goal-drift detection and the public benefit check.
- Stage the rollout. Sandbox, then testnet nodes (such as the Botswana Global Testnet Initiative, under a written agreement), then a limited set of partners.
- Promote. The candidate becomes the successor; its predecessor is archived with a tested rollback path.
Two gates stand between any change and the world. Both failure paths end in the Knowledge Ledger, so a rejected upgrade still teaches the next cycle.
Architecture
The engine is an orchestrator. It calls the gates, stages the rollout and keeps the record, but the decision to promote always rests on the two gates and the people who review them.
Inputs
CRL Engine (orchestrator)
Outputs
| Part | Role | Owner |
|---|---|---|
| Cycle controller | Runs Workflow A for every candidate; never promotes by itself | Systems Engineering |
| Gate 1 connector | Calls the Correspondence Prover and reads its signed proof | Systems Engineering |
| Gate 2 connector | Calls the C-Gate and records its decision | Systems Engineering |
| Sandbox and testnet runner | Stages rollouts, first in isolation, then on testnet nodes (such as the Botswana Global Testnet Initiative, under a written agreement) | Sovereign Deployment |
| Lineage and rollback store | Keeps every generation traceable and reversible | Systems Engineering |
| CTU meter | Records the energy and compute cost of each cycle | Systems Engineering |
| Release note writer | Drafts "what changed, what stayed invariant" for each promotion | Website Lead reviews |
Life of a change
Every candidate ends in one of three places. Promoted: it becomes the live version, and its predecessor is kept with a rehearsed rollback. Held: people pause the rollout and decide. Rejected: the failure is recorded as knowledge, not deleted.
- Proposedby the Reasoning Core
- Evidenceheld-out data gathered
- Proven?Gate 1
- Recordedledger entry
- Gate 2C-Gate
- Stagedsandbox, testnet, partners
Becomes the live version; its predecessor is archived with a tested rollback.
The staged rollout is paused and people decide; it may return to Gate 2.
The failure is recorded in the ledger and teaches the next cycle.
Over many cycles this produces a lineage: a traceable record of every generation, including the versions that failed.
- v1live
- v2promoted
- v3promoted
- v4current
- v5candidate, in Gate 2
People in the loop
The engine runs at machine speed, but people set its limits. A review board signs off every release, the Audit Council reviews major versions, and the board sets the purpose and tolerances the engine must respect.
Machine speed
Every candidate changeWho decides: The engine, within board-set tolerances
What they see: Automated proofs, ledger writes and Gate 2 checks; people see dashboards and alerts.
Release speed
Every versionWho decides: C-Gate review board: Systems Engineering lead, Labs lead, Public Benefit Office
What they see: Proofs, the gate report, the ledger entry and a public release note.
Institutional speed
Every yearWho decides: The board, with the Audit Council
What they see: Purpose and tolerances, audit findings and the public benefit 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
What it guards against
The book names four ways a self-improving system can lose continuity: correspondence drift, goal discontinuity, knowledge erosion and human severance. All four are failures of continuity, not of capability. The engine is where all four guards meet.
Status and evidence
This status is set by the CRIS team and links to the evidence behind it. The engine moves from research to prototype, pilot and live only as each level's evidence is published. The CRIS roadmap places the CRL Engine prototype in its 2027 horizon, "Prove the loop".
Current status: Status to be confirmed
| Level | Evidence required | Who sets it |
|---|---|---|
| Research | Published concept page and draft specification | CEO |
| Prototype | Workflow A running on a test model, with ledger records | CEO, on the Labs and Systems leads’ advice |
| Pilot | Partner deployment on testnet and an Audit Council review | CEO |
| Live | Production use and an external audit passed | CEO, with notice to the board |
For developers: the Build path and the Continuity Invariant specification, draft 0.1.
Read more
- Recursion Without Rupture: Chapter 2 (the four ruptures), Chapters 5 and 6 (the operators and the Invariant), Chapters 8 to 10 (proofs, the ledger and the C-Gate), and Chapter 11 (engineering the engine).
- Specifications: the Continuity Invariant and the correspondence proof format, drafts 0.1.
- The Continuity Invariant and the four ruptures in the Research section.
- Related systems: Observation Mesh, Correspondence Prover, Reasoning Core, Knowledge Ledger, C-Gate.
