Technical report demonstrates cryptographic anchoring for an append-only governance ledger, indicating third-party detectability of database snapshot divergence.
This record publishes the cryptographic chain head of an append-only governance ledger to an independent dated archive, so that any later divergence between the operational database and this fixed value is detectable by a third party. An append-only table prevents records from being edited, but it does not prevent a database from being restored to an earlier snapshot — which removes records without leaving evidence inside the system. An externally published chain head closes that gap. The anchored value is the SHA-256 entry hash at sequence 4 of chain global: fef26890670e2902ac3c4c48a60fb9626d4163e6515a3b8464f9b36f66981228, recorded 2026-09-05 21:21:20 UTC. The record documents the integrity properties enforced at the storage layer rather than in application code — chain computation performed by the database and not delegated to the writer, serialization against concurrent forks, rejection of UPDATE, DELETE and TRUNCATE at both row and statement level, and attribution resolved by the system rather than asserted by the caller. It includes the hash preimage specification required for independent recomputation, the ledger contents at deposit including two adversarial tests recorded in place, and an explicit statement of the properties not claimed: the application connects as a database superuser, restore-based divergence is detectable only after this deposit date, and the ledger contains no independent traffic. First in a recurring series. Subsequent anchor records extend the same chain and cite this deposit.
No takes yet. Share an insight, caveat, or question.
Lara Stuart (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: