See a pack produced live
Run the demo end to end and watch the evidence trail assemble from the call.
Open the demoExplainer · Proof of action
What's in an evidence trail — and why it holds up
Every Verigence call ends with a signed evidence trail. Here's exactly what it contains, how it's signed, and how a reviewer verifies it.
Evidence trail
EP-2026-0517-40192
- Events
- 7
- Approvals
- 1
- Consent
- Yes
- Sig
- ed25519
e3b0c44298fc1c149afbf4c8996fb924·27ae41e4649b934ca495991b7852b855
What it contains
A pack is a structured, ordered record of one call. It isn't a recording you have to trust — it's the decomposed sequence of everything that happened, each item timestamped:
The conversation
Original audio transcript plus translation, turn by turn.
The reasoning
Labeled reasoning milestones and outcome grading used for review.
The tool calls
Tool-call timeline entries and preview metadata that are safe to include in the signed pack.
The approvals
Approval or gate-decision events when a sensitive action required review.
The outcome
What was committed, escalated, or declined.
How it's signed
When the call closes, the ordered events are serialized and hashed, and the hash is signed with an ed25519 key. The signature travels with the pack. Because the signature covers the full content, any later change to any event — a word in the transcript, a tool result, an approval — breaks verification.
How a reviewer verifies it
A reviewer recomputes the hash from the pack's events and checks it against the signature using the public key. If they match, the pack is intact and authentic. If they don't, it's been altered. That's what "tamper-evident" means here: not that tampering is impossible, but that it can't go unnoticed.
The signature proves the record wasn't altered after signing. It doesn't, on its own, assert that the underlying action was correct — that's what the human approval gate is for.
See a pack produced live
In the interactive demo