Resources

Ledger entry format

Entry fields, the three levels, append-only rules and chaining to the previous entry.

Approved by the Board for implementation · 20 November 2026

DraftVersion 0.1.0Drafted 11 November 2026Owner: Systems Engineering (role being recruited; interim owner to be named, Q4)Licence: [to be confirmed]Side of the line: published

A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the Knowledge Ledger page. Changelog · Comment on this specification

Relies on: Correspondence proof format, C-Gate decision format (planned) · Relied on by: CTU metering method, Audit method

1 Purpose

The Knowledge Ledger is the append-only record of everything that happens in the loop. This specification describes one entry: what it holds, the level of knowledge it carries, and the rules that keep the record checkable from end to end.

2 Fields

Draft 0.1. Field names may change.

FieldMeaning
Entry IDUnique and permanent
TypeProof, decision, contribution, rejection, rollback or incident
LineageThe version and earlier entries it builds on
Evidence referencesPointers to evidence, never personal data
LevelHypothesis, supported claim or verified knowledge
SignaturesThe system or person that wrote it
TimeWhen it was written
Link to previous entrySo any change to history is detectable

3 Levels of knowledge

LevelWhat it meansWho may use it
HypothesisA claim on record, not yet testedResearchers; never the ground for reasoning
Supported claimBacked by evidence that passed the ProverThe Reasoning Core, with caution
Verified knowledgeRepeatedly confirmedThe Reasoning Core, as verified ground

The exact thresholds for each step are set by Continuity Labs and will be added in a later version.

4 Rules

  1. Append-only. New entries are added; old ones are never changed.
  2. Corrections point back. A correction is a new entry that refers to the one it corrects, so both stay visible.
  3. Chained. Each entry links to the one before it, with a fingerprint, so any change to history is detectable.
  4. Consolidation deletes nothing. A summary view records which entries it came from; the full history stays.
  5. No personal data in the entry. Evidence is referenced, never copied in.

5 Illustrative example

Illustrative only. Not from a running system. Field names may change.
{
  "entryFormat": "0.1.0",
  "entry": "example-000412",
  "type": "correspondence-proof",
  "buildsOn": ["example-000398"],
  "lineage": "example-system@1 -> example-system@2",
  "evidence": ["held-out-set-A"],
  "level": "supported-claim",
  "writtenBy": "correspondence-prover",
  "time": "2027-01-01T00:00:00Z",
  "previous": { "entry": "example-000411", "fingerprint": "..." }
}

6 Changelog

  • 0.1.0 · 11 November 2026 · minor · First draft, from the Knowledge Ledger page.

Printed from the developer hub changelog, the one record of every version.

Owner: Systems EngineeringNext review: 2027-05-11