Router / Chain integrity
Tamper-evident audit log
Each record stores a SHA-256 over its own canonical content plus the hash of the record before it. Alter a record and its own hash stops matching; remove one and the next record's prev_hash stops matching. Either way the walk halts and names the sequence number where it broke.
Chain intact. Chain intact from the anchor at entry 202 to head. Run npm run verify for a full walk from genesis. 202 entries.
head e5816a3f26d38b4306f1ce56e6f7234709c27eea64d033ba903f8d16ef9c37ae
head e5816a3f26d38b4306f1ce56e6f7234709c27eea64d033ba903f8d16ef9c37ae
The records themselves are not public
A record names the organisation that called, the key prefix, the policy applied and the models involved. Publishing that would leak one institution's operations to every other. Records are available at the examination pack, behind a login and scoped to your own organisation, or through GET /api/v1/audit/verify with a key carrying the read scope.
Verify it yourself
The check above walks from the last verified anchor, which is what makes it cheap enough to render on a page. A full walk from genesis is a separate, deliberate act.
curl -s https://governai.space/api/v1/audit/verify | jq # integrity, no key needed npm run verify # full walk from genesis npm run verify -- --tamper # edits a row, shows the break, restores it