Audit Log Service · View 24 of 40 · 5 · Runtime
Decisions
- The bundle is self-contained: records, covering checkpoints, inclusion proofs, segment hashes and its own manifest, signed by a key whose public half is published.
- The verifier is a single published binary with a specified algorithm, so verification happens on the auditor's machine with no network access and no trust in us. That is the only configuration in which the verdict means anything.
- Every export is watermarked with the role and caller, recorded as an audit event, and counted against a per-role volume cap. Bulk export is the realistic exfiltration path for a store that is otherwise hard to attack.
What an auditor can ask
- Proof of inclusion for a record: available now.
- Proof of non-existence over a covered range: phase 3, on the absence filters — an auditor asks 'did this never happen?' as often as 'when did it happen?'.
- Whether a gap is a deletion: answered by the tombstone and certificate, so the bundle verifies as lawfully disposed rather than as broken.
Assumptions
- Bundles are delivered out of band — a secure file transfer agreed per matter, not a download link from this service. The service is not on the delivery path and is not asked to be.