- Previous hash
- 3a7b9f2c...c841
- This hash
- f9c24a1e...e037
- Record
- Tamper-evident
- Chain status
- Verified
Tower (AI protection) · Evidence and Audit
An AI audit trail nobody can quietly change.
Change one row and the chain says where. Every decision Raidu makes is written once, hash-chained to the one before it. Nobody can edit the record quietly, including us.
Runs inside your AWS, GCP or Kubernetes install.
Last reviewed
Illustrative. No customer data.
The difference
Their way, and ours.
SHA-256 per record, chained by previous hash, anchored outside the database, and kept write-once for ten years.
Source: Tower signing services and write-once database storage
The record
The record that proves itself.
Every tamper-evident record chains to the one before it. Break the chain anywhere and verification shows the exact row.
The call path
Where the record is written.
- InterceptEvery SDK and console call
- ResolveWho, which model, which data
- InspectPolicy checks on the full prompt
- DecideBlock, redact or allow
- ProveEvery decision, written once and tamper-evident
Also covered
- Tamper-evident records
- Hash chain
- External anchor
- Write-once storage
- Erasure-safe
Common questions