What this ledger records
Entries distinguish initial publication, correction, clarification, evidence update, translation repair and structural change. Each entry identifies the affected publication and locale, the version before and after the change, why the change happened, whether the claim itself changed, and where the supporting evidence can be inspected.
published state → observed problem or new evidence → classified change → version transition → public explanation → inspectable evidence → current state
What the contract prevents
Once v0.5 is established on the base branch, history becomes append-only. Existing entries cannot be rewritten or reordered, and a managed published route cannot be modified without a newly appended entry that covers that route in the same change.
Evidence boundary
Proves: registered version bookkeeping, append-only history integrity and evidence linkage.
Does not prove: that a correction is factually sufficient, editorially perfect, or that an unregistered page is version-managed.
Loading version history…
Inspect the underlying evidence
The human-readable page and machine-readable ledger should agree.
The JSON ledger is public, the CI contract validates its version chains, and GitHub Actions retains immutable run evidence.