Proof.
Not promises.Every SET, GET, and DEL is recorded with the principal, timestamp, outcome, and a BLAKE3 hash linking it to the previous entry. Break the chain — Zaps sees it.
Hash-chained audit trail
#847✓
SET
scout
0x7f3a…
prev: 0xe2c1
hash
#848✓
GET
scout
0x2b1c…
prev: 0x7f3a
hash
#849✓
SET
auth-svc
0x9e4d…
prev: 0x2b1c
hash
#850✗
DEL
rogue-x
0xd1a0…
prev: 0x9e4d
hash
#851✓
GET
observer
0xa1f7…
prev: 0xd1a0
hash
#852✓
SET
deploy
0xc3e9…
prev: 0xa1f7
Chain: #847 · building… · BLAKE3 verified
What if someone modifies an entry?
Break the chain.
#847OK
SET agent:ctx
0x7f3a
#848OK
GET agent:ctx
0x2b1c
#849OK
SET session:abc
0x9e4d
#850OK
DEL admin:config
0xd1a0
#851OK
GET agent:ctx
0xa1f7
#852OK
SET flag:beta
0xc3e9
Compliance
Your auditor will thank you.
Every audit entry maps directly to compliance framework controls. Export 2.4M entries in seconds. JSON, CSV, Parquet, or direct SIEM integration.
SOC 2 Type IIGDPR Art. 30HIPAA §164.312ISO 27001 A.12.4
Export: JSONExport: CSVExport: ParquetExport: SplunkExport: ELK
Compliance is not a feature toggle.
It is a property of the system. Zero configuration. Zero ops overhead.