Direct answer · evidence over confidence
How do you prove what an AI agent actually did?
Not by asking it. An agent sounds identical when it's right and when it's wrong — so the proof has to live in structure, not in tone. VeriCommand records every task, dispatch, signal, and return on a hash-chained record that is re-verified every time anyone reads it.
hash-chained
Every record binds to the one before it; the whole chain re-verifies on every read. Tampering arrives flagged, never silently served.
returns bind to dispatches
Who did what, under which instruction — a recorded fact, not a recollection. Self-graded findings count as assertions, not clearance.
verifies offline
Signed evidence packs check out with an open-source MIT tool. No account, no network, no trusting us.
The same discipline applies to the product itself: the download page publishes the installer's exact size and SHA-256. Check it yourself.
Why do AI coding agents need an audit trail?
Because absence of error is not evidence of progress. In one recorded incident on this product's own board, the operator spent a day believing four agents were building. Zero files had been written. Nothing errored — so nothing looked wrong. That day produced the rule the system now enforces structurally: progress is never reported from the absence of failure, and an agent that goes quiet looks like exactly what it is.
The AI's own account of working under this →
What makes a record tamper-evident rather than just a log?
A log can be edited after the fact; that's why logs make weak evidence. On a hash chain, every event — packet, dispatch, signal, return — binds to the record before it, and the whole chain is re-verified on every read. Modify or delete a record and the chain doesn't quietly serve the new version; it arrives flagged. The reader learns about the tampering before they learn anything else.
Can I verify it without trusting the vendor?
Yes, and that's deliberate. VeriCommand exports signed evidence packs that verify offline with an open-source, MIT-licensed tool — no account, no network call, no API that could lie to you. An audit trail you can only check by asking the vendor's server isn't an audit trail; it's a promise with extra steps.
The developer rail, including the verifier →
What does an agent's "done" actually prove here?
A return binds to the specific dispatch that authorized it — so "who did what, under which instruction" is a recorded fact. And the system is quietly rude to unverified confidence: findings an agent grades itself on count as assertions, not clearance. A return of nineteen self-marked criticals displays as "0 of 19 adjudicated" until someone other than the author confirms them. Confidence is not evidence, and the record refuses the exchange rate.
What does an audit trail not do?
It doesn't make the agent right — it makes the agent's claims checkable, which is a different and more honest promise. Verification is still a verb somebody performs. And for agents on your own machine, attribution is declared, not cryptographically authenticated: the chain proves the sequence and integrity of what was recorded, not the OS-level identity of the local process that wrote it. We'd rather state that limit than paper over it — a security page you can't falsify isn't one you should trust.
