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 each section to see sample content
Verify it yourself.
The Evidence Binder is designed to be verified by anyone, anywhere, without vendor access.
$ binderverify --input binder.pdf --pubkey key.pem
✓ signature valid (ECDSA P-256)
✓ merkle root matches ledger
✓ policy bundle checksum matches
✓ approval token signature valid
✓ timestamp within session window
Binder ID: bnd_8f3a7c...
Session: 2026-04-15T14:32:07Z — 2026-04-15T14:32:09Z
Principal: agent-copilot-prod-01
Actions: 3 attempted, 2 executed, 1 blocked
Policy: v2.4.1 (sha256:a1b2c3...)
Verdict: VERIFIEDNo dashboard login. No API call. No vendor dependency. The Binder carries everything needed to prove its own integrity.
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 a tamper-evident ledger. Each entry is linked to the previous one through cryptographic hashes, forming a chain. If any entry is modified after the fact, the chain breaks and verification fails. This is the same integrity pattern used in supply chain security frameworks like SLSA and in-toto.
Customer-managed keys
All signatures use ECDSA P-256 keys that you control. Panopticore signs with your keys, not vendor-owned material. You control the trust root.
Offline verification
A Binder can be verified with the public key and the binderverify tool. No network connection. No API call. No vendor account. The evidence survives 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
Independent verification of agent actions against stated policy. No reliance on the system being audited to produce its own evidence.
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
Verifiable evidence of controls and enforcement. The Evidence Binder provides the controls and evidence insurers are increasingly requiring as agentic AI systems take production actions.
Regulators
Standardized, verifiable evidence of governance in effect. Independent of vendor claims. Suitable for regulatory examination.
External auditors
Third-party verification without vendor access. The public key and binderverify tool are all that's needed.
Evidence FAQ
How is an Evidence Binder different from logs?
What does tamper-evident mean precisely?
What happens when signing keys rotate?
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.”
See the evidence for yourself.
Request early access and we'll walk through a real Evidence Binder with your team.