Change log

The log

• 6 August 2026 — first publication

  The site was published for the first time: the standing pages that describe who publishes it, how it works and what it will not do; the maintained registers and the claims ledger at version 1.0; this log; and an empty, dated corrections index.

  All ten articles listed on the front page were published on the same day, at version 1.0. That is worth saying plainly rather than staggering the dates to look like a slower operation: the site was written and then launched, and every date printed on it is the real date of a real event. Each article carries its own Last reviewed date, and from here those dates move independently and are logged here when they do.

This is the whole log. It begins on the day the site began, and nothing precedes it, because nothing was published before then to change.

What is logged

• A correction. Every correction is cross-listed here and indexed permanently at Corrections, and appears at the top of the corrected page.
• New material on an existing page — a section added, a document newly retrieved and quoted, a table extended.
• A figure updated to a newer collection year, or a register row re-verified against its primary source, including when the re-verification changed nothing. Re-read and unchanged is information, and it is the only evidence that a review actually happened.
• A citation that moved — a rule renumbered by its agency, a statute recodified, a primary URL that died and the archived capture we replaced it with.
• A conclusion changed. This is a major version bump, and the entry has to say which conclusion changed and what changed it.
• A page superseded. The page keeps its address and gains a notice pointing forward. Nothing here is deleted.
• A change in how this publication is funded or governed. There is nothing to declare today, and if that ever stops being true it will be a dated entry here rather than a quiet edit to Independence and funding.

What is not logged, and two things this page deliberately does not do

Typographical fixes, repaired internal links and changes to the stylesheet are not logged. An entry for every comma would bury the entries that matter, which is a way of hiding a correction rather than publishing one.

There is no forward review calendar here. Every article and every register carries its own Next review date in its own metadata block, on the page whose accuracy the date is a promise about. A second copy of that promise, centralised here and maintained by hand, would be the copy that drifted out of step with the first, and a reader checking one page would have two different answers about it. The commitment stays where it can be read by the person it is made to.

There is no automatically generated list of our own overdue items. A counter that renders how late we are is a display, not a discipline; the discipline is doing the review and logging it here when it is done. If a review is late, the way you will find out is that the page’s Last reviewed date has not moved, which is a plain fact printed on the page and not something we can dress up.

Version numbers, and what each kind of bump means

• 1.0 — first publication.
• Minor bump, 1.x — new material, updated figures, added or re-verified register rows, new sources. The conclusions are unchanged.
• Major bump, 2.0 — a conclusion changed. The entry here names the conclusion and the evidence that moved it.
• Correction — a factual error. It produces a dated notice on the page itself, an entry at Corrections, a version bump and an entry here. Four places, one event, no silent edit.
• Review with no change — logged, and the page’s Last reviewed date moves. Nothing else moves.

There are no frozen version URLs. A page has one address, and the history of what that address has said is here rather than in a shadow archive of old copies.

Elsewhere on this site

• Corrections

  The permanent, dated index of every factual error we have published and fixed.

• Editorial standards

  The correction policy in full, the sourcing rules, the certainty ladder and the review process.

• Documents cited

  The index of primary documents, with the date each one was retrieved — the field that goes stale first and is checked most often.