Ledger entry format
Entry fields, the three levels, append-only rules and chaining to the previous entry.
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.
| Field | Meaning |
|---|---|
| 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, never personal data |
| Level | 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 |
3 Levels of knowledge
| Level | What it means | Who may use 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 added in a later version.
4 Rules
- Append-only. New entries are added; old ones are never changed.
- Corrections point back. A correction is a new entry that refers to the one it corrects, so both stay visible.
- Chained. Each entry links to the one before it, with a fingerprint, so any change to history is detectable.
- Consolidation deletes nothing. A summary view records which entries it came from; the full history stays.
- No personal data in the entry. Evidence is referenced, never copied in.
5 Illustrative example
{
"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.
