The demo
See an evidence bundle hold up under tampering
A walkthrough of what CarveTrace records, what its verifier says, and what happens when someone tries to change the record after the fact.
Moment 1 · The situation
A decision gets challenged
Six months ago, an AI screening system reviewed a candidate's CV and dropped them from the shortlist for a senior engineering role. The candidate has now filed a discrimination complaint. The labor authority wants to see exactly what text the model received, what categories it was scoring against, what model version was running, and what it returned — for that one CV, for that one role.
Moment 2 · The recording
Here is what CarveTrace recorded
An evidence bundle from the CV-screening system. It contains every step that decision went through: the CV text the model received, the categories it was asked to score against, the model and version that ran, the inference output, and the timestamps from an independent RFC 3161 authority — all linked into a cryptographic chain, each event signed. The bundle is ready to be inspected.
Moment 3 · The verdict
The verifier says: VERIFIED
Drop the bundle into the verifier — running entirely in a browser, not on our servers — and you see: VERIFIED. Every signature checks out. Every timestamp resolves to a trusted authority. Every event in the chain references its predecessor. The bundle is exactly what it claims to be: the trace of that decision, sealed at the moment it happened.
Moment 4 · The tamper test
Flip one byte. Watch the verifier reject it.
Now imagine someone tried to alter the recorded reasoning after the fact — change one character in the CV text the model received, or in the categories it scored against. Drop the modified bundle. The verifier says: FAILED. The cryptographic chain breaks at the altered record, and every record that came after fails with it. You cannot change history without leaving a trace the verifier will see.