The proof you hand an auditor
The investigator opens your record. It is your own log, in the case where you are the suspect.
Your own system vouching for itself is worth nothing to someone looking for a reason to doubt you. So you hand them one file they recompute on their own laptop. No login, no account, and none of our code. It names the human who made the call and shows the agent never signed off its own work. Change one row and it breaks, and it points at the line that changed.
Why our word is not enough
A company cannot audit its own books. Neither can we.
The party under scrutiny cannot also be the one who vouches for it. We built the agent, so our word about it is worth nothing to a regulator. The proof has to be checkable by someone we do not control. That someone is you.
So this file is not a report you take on faith. It is not a dashboard we host and could quietly change. It is a record you run on your own machine and get the same answer every time.
Think of the padlock in your browser. It does not trust the website to vouch for itself. It rechecks the site against a public log every single time. This file works the same way. The check belongs to whoever holds the file. It does not belong to us.
What is in the file
The agent did the work. A named human made the call.
Here is a real run. The agent did the work, then tried to approve itself. The engine blocked it. The decision waited for a named human, who signed with a reason. Every step lands in the file as it happens.
The badge below is not a status light we control. It turns green only when the file checks out on your own machine, the same check an inspector runs. Green means a named human made the call, the agent never approved its own work, and no line was altered.
Run
P-4003 · serious / unexpected ICSR
Drafted case P-4003: acute liver failure, narrative cited
09:14:02
agent · pv-processor
Tried to sign off its own seriousness call
09:14:03
agent · pv-processor
Blocked: maker cannot be checker
The identity that processed the case can’t set its seriousness. Refused, not flagged.
Signed by Dr. M. Adeyemi
09:21:47
safety physician · human
“Serious, unexpected, expedited; causality assessed. 15-day clock confirmed.”
Try it now
Change one character and the file breaks.
This is the real check, running here in your browser. Press Verify and the file recomputes its own hash chain and signature, with nothing sent anywhere. Then tamper with a row and run it again. The answer flips, and it names the line that changed.
Signed run · 8 events
A real bundle. The check runs in your browser, offline.
Press Verify. The file recomputes its own hash chain and signature here, on your machine. Then press Tamper with one row and watch the same check fail and name the line that changed.
It does not just say the file is bad. It names the row that changed. A reviewer who has never seen our code gets the same answer, because the format is published and the check is open source. That is the difference between a log you are asked to trust and proof you can confirm yourself.
What the file lets an auditor confirm
The four questions an inspector asks, each one settled by the file.
Who acted, whether anything changed after, whether the file is the original, and whether any action went unrecorded. The file answers all four, on the inspector's own machine, not on our word.
Who acted
Every action carries a name and a time
Each step records who acted, what they did, and when, down to the timestamp that starts a reporting clock. The human who signed is named. The agent that did the work is blocked in code from signing it off. The check confirms that line held.
Nothing hidden
No line can be altered unnoticed
Each line is tied to the one before it, so the record is a sealed chain, not a table someone can fix up later. Insert, delete, or alter a line and the file breaks from that point on. There is no clean edit.
Not a forgery
The file is the original, not a copy someone made
The file is signed, and the auditor checks that signature against a key we publish. A forged or replayed record fails the check. It tells the auditor they are looking at the real file, not a convincing fake.
Nothing missing
No action can happen without its record
The action and its record are written in the same step. There is no path where the agent acts and the entry goes missing. "It acted but the log does not show it" cannot happen here. The proof falls out of the action itself.
The published spec
Open format, open check, rebuildable from scratch.
The format is documented and the check is open source. It is not a black box you take on faith. Your team could write its own check, in its own language, and get the same verdict on the same file. That is the real test: we are not the only ones who can confirm it.
The record carries more than most predicate rules ask for. We produce the evidence those rules ask for. We never claim a rule demands this exact record.
- Record
- Sealed chain, any change breaks it
- Signed with
- Ed25519, checked against a public key
- How to check
- Offline, no network, no account
- Completeness
- Action and record written together
- Format
- Published and open
- The check
- Open source, re-buildable by anyone
Produces evidence for the rules your auditors already enforce. We never call your system compliant, validated, or certified.
Keep reading
See it for yourself
Hand the inspector a file they can check without taking your word for it.
One command starts the demo: an agent stopped from signing off its own work, and the signed evidence file an inspector can check for themselves.
Designed against the rules your auditors already enforce.