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.
Impatient ? Drop the bundle into the verifier above — the story below is for context.
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
Below is a real CarveTrace evidence bundle from a CV-screening pipeline. Seven candidates over five working days, three reviewers — three approvals, two overrides, two escalates. The bundle contains every step each decision went through: the input fingerprint, the categories the model scored, the model + version that ran, the AI verdict, the human reviewer's verbatim rationale, the timestamps from an independent RFC 3161 authority, all linked into a cryptographic chain, each event signed.
Both bundles ship inside the verifier itself if you'd rather pull them from there.
Moment 3 · The verdict
The verifier says: VERIFIED
Open verify.carvetrace.com in any modern browser — Chrome, Firefox, Safari — and drag the valid bundle onto the page. The verifier runs entirely in your browser, not on our servers, and reports: VERIFIED. Every signature checks out. Every timestamp resolves to a trusted authority. Every event references its predecessor by hash. The included report is human-readable : one "dossier" per decision, with the AI verdict, the human rationale, and the cryptographic binding side-by-side.
Moment 4 · The tamper test
Flip one byte. Watch the verifier reject it.
Now drop the tampered bundle. It is byte-identical to the valid one except for a single bit flipped inside the signed report — the kind of change someone might make to rewrite history after the fact. The verifier says: FAILED. The signature no longer matches the report content ; the manifest no longer matches the file's SHA-256. You cannot change a CarveTrace bundle without leaving a trace any third party can see in seconds.
What this means for your AI Act program
Every AI decision your high-risk system makes can be wrapped in a bundle like this — yours to keep, yours to hand to your auditor, yours to defend in front of the EU AI Office or a claimant under the Product Liability Directive. The verifier we just used is the same verifier they will use. The verdict you see is the verdict they will see.