Evidence your auditor, your insurer, and your regulator can verify.
The Evidence Binder is a cryptographically signed, self-contained record of what an agent did, which policies governed it, and whether those policies were enforced. Any third party can verify it offline, without vendor access.
What's inside an Evidence Binder.
Hover or tap a section to see sample content
Verify a Binder offline.
binderverify, Panopticore's verification CLI, checks a Binder without contacting any service.
$ binderverify --binder binder.json \
--evidence-signature binder.evidence.dsse --pdf binder.pdf
binder: binder.json
binder_json_hash: 4e1c09b7d2...
merkle_root: 9f8e7d6c5b...
ledger_root: 3a71c2e8d4...
policy_checksum: a1b2c3d4e5...
pdf_hash: 77d0f1a9c6...
key_id: binder-key-v1
signing_time: 2026-04-15T14:32:09ZIt rebuilds the ledger hash chain and Merkle root from the Binder's entries, re-hashes binder.json and the PDF, and checks the ECDSA P-256 signature against the embedded or supplied public key. Any mismatch fails verification.
How the evidence stays trustworthy.
Each event links to the previous via cryptographic hash. Break any link and verification fails.
Merkle-linked ledger
Every governance event is recorded in the hash-linked ledger shown above. Sigstore's Rekor transparency log and Certificate Transparency rely on the same Merkle-tree integrity pattern.
Customer-managed keys
All signatures use ECDSA P-256 keys that you control. Panopticore signs with your keys, so the trust root is yours.
Offline verification
binderverify checks a Binder with the signer's public key, with no network connection or vendor account. It stays verifiable through vendor outages, contract termination, and organizational change.
Key rotation
Evidence Binders carry the verification artifacts needed to validate them against the key that was active at signing time. Binders produced before a rotation remain verifiable after the rotation.
Who uses Evidence Binders.
Internal auditors
Check agent actions against stated policy using evidence the audited system did not produce.
Incident responders
Precise reconstruction of agent behavior during an incident. What was attempted, what was blocked, and the exact policy state at the time.
Legal teams
Tamper-evident, signed records suitable for legal proceedings. The Binder is a self-contained artifact, not a screenshot of a dashboard.
Insurance carriers
The Evidence Binder provides the controls and evidence insurers are increasingly requiring as agentic AI systems take production actions.
Regulators
Verifiable evidence of which governance was in effect, in a form suited to regulatory examination.
External auditors
Verify Binders with binderverify and the signer's public key, without vendor access.
Evidence FAQ
How is an Evidence Binder different from logs?
What does tamper-evident mean precisely?
Can a Binder be subpoenaed?
What's included in a Binder by default?
Can payloads be included?
“Every decision is recorded in a cryptographically signed audit trail that can be verified offline by any internal auditor or third party.”
Further reading
Our NIST submission in plain language: the evidence gap, action-level risk, bypass-by-architecture, and governance independence.
AI systems cannot reliably govern themselves. Why deterministic, infrastructure-layer governance beats self-reporting by the agent under review.
See the evidence for yourself.
Request early access and we'll walk through a real Evidence Binder with your team.