Export the record. Check it yourself.
Take the record with you — and, on the local build, the proof with it.
From the audit view you can export your activity as JSON or CSV — the events, their actors and targets, and the chain head they were read under. That file is yours: keep it, hand it to someone, or diff it against a later export.
The local agent host goes further. It exports a session as a signed receipt — the events, their diffs, the hash chain, and an Ed25519 signature per event from the agent identity registered with Token Holder — and ships a small verifier that recomputes all of it offline, with the format spec written inside the receipt itself. That build is proven and has no download link yet, so it is labeled roadmap here.
Export your activity record
Live todayJSON or CSV from the audit view, on real rows only — sample data is deliberately not exportable.
Signed session receipt
RoadmapEvents, diffs, hash chain and a per-event Ed25519 signature in one portable JSON file, carrying its own format spec.
Offline verifier
RoadmapA 65-line Node script with no dependencies and no network. Exit 0 is a pass; a failure names the check that broke.
Tamper matrix
RoadmapEight field-class tampers — content, diff, signature, chain link, key swap, dropped event, attestation, and a full recompute-and-replace — each caught with the right failure.
This is tamper-evident, trusted-operator forensics: an alteration is detectable and provable. It is not “cryptographically unalterable” — the value is that you can catch and prove a change, not that a change is impossible. Signing on the local ledger is also fail-open by design: an event recorded while no key is available is stored unsigned and counted as unsigned, rather than the write being refused.
The verifiability claim is always one click from a way to check it — no account, no trust required.