GovernedAI
The institutional surface for governed AI · sealed receipts only.

The Chronicle

The continuous, hash-chained record of every sealed Council decision, every contested claim, every accepted correction.

Why this exists

A receipt that can be silently rewritten is not a receipt. The chronicle is the discipline of publishing every consequential decision in a hash chain that cannot be backfilled without detection.

This is not a blog. It is not a changelog. It is the audit-grade narrative spine of the publication.

Why the chronicle cannot be backfilled

Each chronicle entry references its predecessor by hash. The chain is monotonic: the entry sealed at time T commits to the entry sealed at time T-1. To insert an entry at T-N retroactively, every entry from T-N+1 through today would have to be re-hashed and re-signed. The signatures would change. Anyone with a copy of the prior chain can detect the rewrite.

This is why the chronicle is one of the seven irreducible moats: once started, it strengthens with every entry. It cannot be acquired, copied, or replayed by a competitor on day one.

Chronicle index

The chronicle is being seeded as 48-hour sprint artifacts pass adversarial review. Forthcoming entries:

Each entry will resolve to /chronicle/<date>-<slug>.html with: timestamp, decision class, parties involved, prior-entry hash, content, signature reference. Sealed entries cannot be silently edited; corrections amend forward.

Contestation log

A separate sub-index at /chronicle/contests/ records every contestation submitted via the corrections policy, regardless of verdict.