Proof
Check a record yourself.
The check runs entirely in your browser. Nothing is uploaded to any server.
These are illustrative sample records for demonstration purposes only. They do not represent production records.
Three checks. No trust required.
Every record carries a currentLogHash field. The verifier recomputes it from sixteen record fields, joined with a pipe character and hashed with SHA-256. If even one character changed after the record was written, the recomputed hash will not match.
Fields: timestamp | aiSystemId | aiSystemVersion | eventType | eventAction | eventDescription | inputDataHash | outputDataHash | decision | confidenceScore | userId | ipAddress | userAgent | sessionId | requestId | previousLogHash
Each record includes the previousLogHash of the record that came before it. The verifier checks that this value exactly matches the currentLogHash of the preceding record. A gap or reorder anywhere in the chain is immediately visible.
Each record carries a public-key signature field. The verifier uses the WebCrypto API to confirm it against the supplied public key, entirely in your browser. If the signature check fails, either the record or the key is wrong. These sample records are illustrative; paste your own public key to verify records from your environment.
This page checks Tower evidence records. For Wheelhouse, a verifier that runs offline on a laptop ships in the Proof Pack.
Proof that holds up in any room.
Every decision Raidu makes is written once, tamper-evident, and chained to the one before it.