Tamper-evident audit log

15 September 2026 · Status: In verification

What changed

• Each audit write is sealed with a SHA-256 over one canonical payload and linked to the previous entry's hash.
• Verification runs from the chain's genesis sentinel across the whole sealed history, not a rolling window.
• A background sweep re-verifies hourly and records how far it read.
• Existing audit rows stay readable but are deliberately outside the chain — nothing is backfilled, because rewriting history inside an append-only log would weaken the evidence rather than improve it.