Guided demo · evidence check · synthetic records included
Run the proof. Then break it.
Choose a surface. Check the intact record. Then check the tampered one. The compliance view shows what matched, what failed, and why the result changed.
Record check
Have a real record? See how a record is checked →
01 ·
Same machine, easier entrance.
Guided record · visible tamper path · no account
The intact run should pass. The tampered run should fail. The useful thing is not the sample record; it is the shape of the receipt: a compliance team can see which part of the record held.
What it proves
A signed evidence record can be recomputed later.
The browser checks the root, file hashes, and signature when supported.
What it does not claim
This is not a live customer deployment or a named-network integration.
The surfaces are synthetic. Real work produces customer-specific evidence.
Why it matters
The record can survive outside the meeting where it was explained.
A compliance team can inspect the receipt instead of taking the claim on trust.
Check status
FilesNot checked
RootNot checked
SignatureChecked when present
What happened
Root comparison
Claimed in record
Recomputed in your browser
Record receipt
Artifact ledger
| Filename | Claimed sha256 | Recomputed sha256 | · |
|---|
02 ·
Where next.
If the walkthrough convinces · what to do