Prove what the AI did — to a skeptic.
A chained record you can export, and a chain head anyone can re-derive.
Every action the AI takes against your data is written to your tenant's usage chain: each row hashed together with the one before it, so the order is fixed and a removed or edited row moves the head. Export the window as JSON or CSV and hand it to your compliance officer; the head hash it was read under is printed beside it, and Verify integrity re-derives that head on demand.
That is a strong record and a limited one, so here is the line: the exported bundle is not signed. Read access to the audit store deliberately cannot request a signed export — signing is an owner capability, not a reader one — so what an auditor can check today is that the chain is internally consistent and matches the head, not that a key attests to it.
Exportable audit record
Live todayYour tenant's chained activity as JSON or CSV, with the chain head it was read under.
Chain integrity, on demand
Live todayVerify integrity re-derives the head from the rows and answers. A dropped or altered row moves it.
Signed receipts an auditor can check offline
RoadmapPer-event Ed25519 signatures, the diffs, and a zero-dependency verifier that needs no vendor server. Proven on the local agent host; not wired into the hosted product.
Tamper-evident, trusted-operator forensics. Detectable and provable — not “unalterable.” Today's exported bundle carries a chain, not a signature: bundle-level signing for third-party auditor trust is roadmap, and the per-event Ed25519 signing that already exists belongs to the local agent host rather than the hosted service.
The verifiability claim is always one click from a way to check it — no account, no trust required.