Reasoning Core
Improvement that starts from verified ground.
In one paragraph
The Reasoning Core is where a CRIS system works out how to improve. It reads only what has been verified, including every place where its model and the evidence still disagree, ranks ideas for improvement by how much they should help for what they would cost, and drafts the most promising change with a plan for testing it. Then it hands the change over. The Core never tests, approves or deploys its own changes: other systems and people do that.
Its full name is the Reasoning and Redesign Core. It carries Iᵢ, internal reasoning and computation, the third operator of the Fourth Law: "the system's model, inference and design capacity". It is the part of a self-improving system that asks, given what has been verified, what should change, and writes that answer down as a proposal.
Where it sits
The Core carries the third stage of the loop, Reason. In the CRL Engine's Workflow A it proposes the change at step 1; two gates follow before anything reaches the world.
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
Verified ground
Our rule is simple: no reasoning before verification. The Core starts only from knowledge that has passed the Correspondence Prover and from the contradictions the Prover has found. It does not learn from its own outputs, and it never sees the evidence used to test it.
Reads
Never reads
| Input | Where it comes from | Why |
|---|---|---|
| Verified knowledge | Knowledge Ledger, entries promoted to "verified" | Reason only from what has passed |
| Open contradictions | Correspondence Prover, via the ledger | The most valuable things to fix |
| Correspondence state | The latest signed proof | Confirms the ground is verified |
| Earlier attempts | Ledger lineage, including failures | Avoids repeating what failed |
Open contradictions are the Core's main source of work: each place where the model and the world disagree is a hypothesis waiting to be tested. Reasoning from the system's own outputs instead would lead to what the book calls self-referential collapse (Chapter 7.1).
How it works
Every improvement starts with the same four steps.
- 1ReadLatest verified knowledge and open contradictions
- 2RankHypotheses by expected gain per CTU
- 3DraftThe change and its test plan
- 4SubmitTo Workflow A; the Core never deploys
- Read the ledger's latest verified knowledge and open contradictions.
- Rank hypotheses for improvement by expected correspondence gain per CTU of compute.
- Draft the change and its test plan.
- Submit it to Workflow A. The Core never deploys its own changes.
The trigger is a verified correspondence state. The output is a proposal, not a new version: a new version exists only after the CRL Engine promotes it.
Ranking by gain per CTU
Every idea is weighed by the improvement it should bring against the compute and energy it would use, measured in Compute Thermodynamic Units (CTU). Fixing a known error cheaply comes before an expensive change with an uncertain gain. The chart is an illustration, not a real result.
- 1Fix a known contradiction in one domainSmallLowProposed first
- 2Retrain on newly verified evidenceMediumMediumProposed next
- 3Redesign a whole moduleUncertainHighRanked lower
- 4An idea with no verified basis——Not proposed
This keeps improvement honest about its price. A large change that costs a great deal for a small gain ranks below a small fix to a known contradiction, and an idea with no verified basis is not proposed at all.
The proposal
What the Core hands over is a complete package, so the systems that check it know exactly what is claimed and how to test it.
- 1The changeTo methods, architecture, training data or parameters
- 2Written hypothesisWhat it should improve, and in which domains
- 3Test planThe domains and evidence types the Prover should use
- 4BasisThe ledger entries and contradictions it starts from
- 5Expected costCompute and energy, in CTU
- 6LineageParent version and earlier attempts, including failures
| Part | What it contains |
|---|---|
| The change | To methods, architecture, training data or parameters |
| Written hypothesis | What it should improve, and in which domains |
| Test plan | The domains and evidence types the Prover should use |
| Basis | The ledger entries and contradictions it starts from |
| Expected cost | Compute and energy, in CTU |
| Lineage | Parent version and earlier attempts, including failures |
Limits
The Core may propose changes to how a system reasons, how it is built, what it learns from and its settings. It may never change the system's purpose, the gates that check it, its recorded history, or its own access to test evidence. Those limits are enforced by the systems around it.
May propose changes to
- How the system reasons (methods)
- How it is built (architecture)
- What it learns from (training data)
- Its settings (parameters)
May never change
- The system’s purpose
- The gates that check it
- The ledger’s recorded history
- Its own access to test evidence
Separation of duties
No single system proposes, tests and approves the same change. The Core proposes; the Observation Mesh gathers fresh evidence; the Correspondence Prover and the C-Gate decide; the CRL Engine rolls the change out in stages; and the Knowledge Ledger records every step.
- ProposeReasoning CoreContinuity Labs sets research priorities
- Gather evidenceObservation MeshSource owners give consent
- Test · Gate 1Correspondence ProverAudit Suite re-runs a sample
- Check purpose · Gate 2C-GateReview board for each release
- PromoteCRL EngineAudit Council for major versions
- RecordKnowledge LedgerAuditors read it
| Role | System | People |
|---|---|---|
| Propose | Reasoning Core | Continuity Labs sets research priorities |
| Gather evidence | Observation Mesh | Source owners give consent |
| Test (Gate 1) | Correspondence Prover | Audit Suite re-runs a sample |
| Check purpose (Gate 2) | C-Gate | Review board for each release |
| Promote | CRL Engine | Audit Council for major versions |
| Record | Knowledge Ledger | Auditors read it |
This separation is what lets a self-improving system keep its guards against all four ruptures, rather than marking its own work.
Learning from failure
When a proposal fails, it is recorded with the reasons, and the Core reads that record at the start of its next cycle. A rejected change is not wasted: it tells the next attempt what not to do.
- Proposal failsAt Gate 1 or Gate 2
- Recorded with reasonsIn the Knowledge Ledger, not deleted
- Read next cycleThe Core sees what failed and why
- Better proposalThe same change is not resubmitted unchanged
Status and read more
This status is set by the CRIS team and links to the evidence behind it. The CRIS roadmap places the first CRL prototype, and with it the Core's first proposals, in 2027.
Current status: Status to be confirmed
| Level | Evidence required | Who sets it |
|---|---|---|
| Research | Concept page and draft proposal format published | CEO |
| Prototype | Proposals generated from a test ledger and submitted through Workflow A in a test CRL cycle | CEO, on the Labs and Systems leads’ advice |
| Pilot | Proposals used in a partner deployment on testnet; Audit Council review of a sample | CEO |
| Live | Production use; external assessment passed | CEO, with notice to the board |
For developers: Concepts: the loop as data (the proposal format is planned).
- Recursion Without Rupture: Chapter 6 (the Continuity Invariant), Chapter 7.1 (self-referential collapse), Chapter 8.6 (failures as knowledge) and Chapter 9.1 (reasoning from verified ground).
- Specifications: the proposal format, to be published.
- History: earlier CRIS materials called this system the Crystalline Reasoning Substrate.
- Related systems: Knowledge Ledger, Correspondence Prover, CRL Engine, C-Gate, Observation Mesh.
