Knowledge Ledger
A permanent record of what was learned, including what failed.
In one paragraph
The Knowledge Ledger is the permanent memory of every CRIS system. Every test result, every decision, every verified contribution and every rejected change is written to it, and nothing written is ever overwritten. Each new version of a system inherits the whole ledger, so it starts from everything its predecessors learned, including their mistakes. This is how we guard against knowledge erosion: the slow loss of what a system once knew.
It carries Σ, accumulation, the fourth operator of the Fourth Law. For every result it answers one question: has this earned a permanent place in the record?
Where it sits
The ledger carries the fourth stage of the loop, Accumulate. In the CRL Engine's Workflow A it records every result at step 4, whether the change passed or failed.
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, Article 11: lineage, rollback and archival. They are approved by the Board for implementation.
What gets written
Every system in the loop writes to the ledger, and nothing reaches the next cycle without an entry.
- Correspondence proofsFrom the Prover, pass or failWritten by: Correspondence Prover
- C-Gate decisionsPromote, hold or rejectWritten by: C-Gate
- Rejected upgradesWith the contradictions that failed themWritten by: CRL Engine
- Verified contributionsFrom CIX, with provenance and consent recordWritten by: CIX, after the Prover
- RollbacksWhich version, why, and the resultWritten by: CRL Engine
- IncidentsLinked to every affected versionWritten by: Systems Engineering
| Entry | Written by | When |
|---|---|---|
| Correspondence proof | Correspondence Prover | Every candidate change, pass or fail |
| C-Gate decision | C-Gate | Promote, hold or reject |
| Rejected upgrade | CRL Engine | With the contradictions that failed it |
| Verified contribution | CIX, after the Prover | With its provenance and consent record |
| Rollback | CRL Engine | Which version, why, and the result |
| Incident | Systems Engineering | Linked to every affected version |
Contributions from people enter the same way. In Workflow B, a contribution to CIX reaches the ledger only after the Prover has verified it, and only then can the Participation Value Meter reward it.
- 1Join CIXVia the web or the CES app
- 2Consent and IDPrivacy and ownership
- 3ContributeAn observation or insight
- 4Verified?Correspondence Prover · ↔No → feedback, try again
- 5Enter ledgerKnowledge Ledger · Σ
- 6Value MeterScores the contribution
- 7RewardPaid; reputation rises
- 8Benefit reportAggregate and public
How it works
Every entry follows the same four steps.
- 1WriteAn append-only entry with lineage, evidence references and signatures
- 2PromoteBy rule: hypothesis → supported claim → verified knowledge
- 3ConsolidateCompress periodically without deleting history
- 4ExposeRead-only views to auditors; summaries to the public
- Write an append-only entry with its lineage, evidence references and signatures.
- Promote it by rule: from hypothesis, to supported claim, to verified knowledge.
- Consolidate periodically without deleting history (book Chapter 9.6).
- Expose read-only views to auditors and, in summary form, to the public.
The trigger is any proof, decision or verified contribution. Auditors can read the full ledger at any time; the public sees it in summary form.
Anatomy of an entry
Each entry says what it is, what it builds on, the evidence behind it and who wrote it. It also carries a link to the entry before it, so the record can be checked from end to end. The fields below are a draft; the entry format will be published as a specification.
- Entry ID
- Unique and permanent
- Type
- Proof, decision, contribution, rejection, rollback or incident
- Lineage
- The version and earlier entries it builds on
- Evidence references
- Pointers to evidence, not personal data
- Status
- Hypothesis, supported claim or verified knowledge
- Signatures
- The system or person that wrote it
- Time
- When it was written
- Link to previous entry
- So any change to history is detectable
entry Σ-000412 type correspondence proof parent Σ-000398 lineage version 3 → candidate 4 evidence vault set 17 (reference) status supported claim signed Correspondence Prover previous Σ-000411 · fingerprint
Three levels of knowledge
Not everything in the ledger is treated as fact. A new claim starts as a hypothesis. When it passes the Correspondence Prover it becomes a supported claim, and when it is repeatedly confirmed it becomes verified knowledge, the only ground our systems are allowed to reason from. The rules for each step are published.
- 1HypothesisAn idea or claim on record; not used as ground for reasoning
- 2Supported claimBacked by evidence that passed the Correspondence Prover
- 3Verified knowledgeRepeatedly confirmed; what the Reasoning Core may build on
| Level | What it means | Who uses it |
|---|---|---|
| Hypothesis | A claim on record, not yet tested | Researchers; never the ground for reasoning |
| Supported claim | Backed by evidence that passed the Prover | The Reasoning Core, with caution |
| Verified knowledge | Repeatedly confirmed | The Reasoning Core, as verified ground |
The exact thresholds for each step are set by Continuity Labs and will be published in the specification.
Append-only and consolidation
Append-only means new entries are added and old ones are never changed. If later evidence shows an entry was wrong, we add the correction as a new entry that points back to it, so both remain visible. Each entry also links to the one before it, so any change to history would be detectable.
The ledger
- Σ-101Claim recorded
- Σ-102Proof passes
- Σ-117New evidence contradicts it
- Σ-118Correction, pointing back to Σ-102
Never
- Σ-102Silently edited to match new evidence
- History lostNo one can see what changed
From time to time the ledger is summarised into a compact view for fast reading. This is consolidation, and it never deletes anything: the full history stays, and every summary records which entries it came from.
- Σ-101
- Σ-102
- Σ-103
- Σ-104
- Σ-105
- Σ-106
- Σ-107
- Σ-108
- Σ-109
- Σ-110
- Σ-111
- Σ-112
Failures are knowledge
Our rule is direct: rejected upgrades are written to the ledger, not deleted (book Chapter 8.6). When a change fails its tests, the failure is recorded with what was tried, the evidence that stopped it and why the gate said no. The next cycle reads that record before proposing anything new. A rejected change is not wasted: it is how a system remembers what not to do.
- Version 1Writes entries
- Version 2Inherits all of them, adds more
- Version 3Inherits all, including failures
- RollbackAny version can be traced and restored
Without a ledger
Each new version can forget what earlier ones learned: knowledge erosion.With the ledger
Nothing verified is lost, and no failure is repeated unknowingly.Every successor inherits the whole ledger, failures included, and any earlier version can be traced and restored. That is the guard against knowledge erosion, one of the four ruptures.
Read about knowledge erosion on the ruptures page.
Who can read it
Our systems read the ledger to decide what to do next. Independent auditors can read all of it. The public sees summaries, including the figures in our public benefit report. No one, inside or outside CRIS, can edit or delete an entry.
- Reasoning CoreVerified knowledge and open contradictionsRead
- Participation Value MeterVerified contributionsRead
- Auditors and the Audit CouncilThe full ledgerRead-only, complete
- The publicSummaries and the benefit scorecardSummary
- No oneEdit or delete an entryNot possible
| Reader | What they see | Basis |
|---|---|---|
| Reasoning Core | Verified knowledge and open contradictions | Workflow, Section 9 |
| Participation Value Meter | Verified contributions | Workflow B |
| Auditors and the Audit Council | The full ledger, read-only | Step 4 |
| The public | Summaries and the benefit scorecard | Step 4 |
| No one | Editing or deleting an entry | The append-only rule |
Auditors read the ledger at every one of the 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 roadmap places the first CRL prototype, and with it the ledger's first entries, in 2027.
Current status: Status to be confirmed
| Level | Evidence required | Who sets it |
|---|---|---|
| Research | Concept page and draft entry format published | CEO |
| Prototype | Entries written by a test CRL cycle; append-only and links between entries tested | CEO, on the Labs and Systems leads’ advice |
| Pilot | Used in a partner deployment on testnet; auditors read it; summary views published | CEO |
| Live | Production use; external assessment passed; feeds the benefit report | CEO, with notice to the board |
For developers: the ledger entry format, draft 0.1, and the Verify path.
The ledger is also where our public benefit indicators come from.
- Share of promotions with a complete proof, gate record and rollback testContinuity
- Rejected upgrades and contradictions resolvedContinuity
- Audit findings raised and closedGovernance
- Verified contributions enteredPeople
- Recursion Without Rupture: Chapter 2 (knowledge erosion), Chapter 8.6 (failures as knowledge), Chapter 9 (the Knowledge Ledger) and Chapter 9.6 (consolidation without loss).
- Ledger entry format: draft 0.1, open for comment; promotion thresholds to be added.
- Related systems: Correspondence Prover, Reasoning Core, C-Gate, CIX, Participation Value Meter, Continuity Audit Suite.
