Evidence packs
Export a zip of a task's Agent Ledger slices, approvals, agent versions and costs, and verify it offline.
On this page
An evidence pack is a zip that shows what Titan recorded for one task, or for the tasks created in a period: the Agent Ledger entries of their sessions, their approvals, the agent versions they ran and what they cost. An auditor can verify the Ledger entries offline.
hexel harness evidence-pack create --task tsk_123 --out tsk_123.zip
hexel harness evidence-pack create --from 2026-11-01T00:00:00Z --to 2026-11-15T00:00:00Z --out november.zip
hexel harness evidence-pack pull evp_456 --out evp_456.zipPOST /harness/evidence-packs {"task_id": "tsk_123"} or {"from": "<RFC 3339>", "to": "<RFC 3339>"}
→ 201 {"id": "evp_456", "task_ids": [...], "created_by": "...", "created_at": "..."}
GET /harness/evidence-packs/{id} → 200 application/zipA period is at most 31 days and 200 tasks, in the environment of the request. The tasks are fixed when you ask for the pack. The zip is built when you download it.
Who can create and download one
Asking for a pack needs harness:audit:read. The pack is built with the downloader's own access, so downloading also needs titan:ledger:read and titan:approval:read at organization level. For the organization's costs it also needs org:billing:read; without it, the pack's costs are your own. The harness holds no Titan or billing credential for packs.
What a pack holds
| File | What |
|---|---|
pack.json | What the pack covers, the Titan deployment, the Ledger verification, every session's slice pages and whether they are signed, the SHA-256 of every other file, and what the pack proves |
ledger/verify.json | Titan's verification of the whole Ledger chain when the pack was built |
ledger/sessions/<n>-<session>/page-<n>.json | The Ledger slice of each Titan session of the tasks, byte for byte as Titan exported it |
keys/ledger-slice.pub | The public key the slices are signed with |
tasks.json | The tasks, their runs and each run's Titan sessions; never a goal, inputs or outputs |
approvals.json | Each approval as the harness recorded it and as Titan holds it |
agent-versions.json | The agent versions the tasks ran, with their bundle digests |
costs.json | The cost of each task and run, and the settled harness costs for the period |
README.md, verify.sh | How to verify every page offline |
Verify a pack offline
verify.sh runs titan-ledger-verify on every Ledger page:
titan-ledger-verify -pack ledger/sessions/1-<session>/page-1.json \
-pubkey keys/ledger-slice.pub -deployment <deployment id>Hexel Studio provides titan-ledger-verify to preview customers on request. It needs no database or network access.
What it proves. Every included entry is intact: each re-hashes to its digest and links to its neighbours. A signed page was selected by Titan's Gateway for that session. What it does not prove is completeness, that no entry or session was left out: to check that, compare a page with an independent record of the chain using -expect-seq and -expect-digest. A session marked pruned_gap was exported after older entries were pruned from the live chain.
When a pack cannot be built
A pack never leaves a session out silently: any failure fails the whole download.
| Error | Meaning |
|---|---|
409 ledger_not_verified | Titan's Ledger chain did not verify. |
409 ledger_not_anchored | Recent entries are not anchored yet. Try again shortly. |
403 titan_forbidden, 403 billing_forbidden | Your access does not cover the Ledger, approvals or costs. |
422 evidence_pack_too_large | More than 200,000 entries, 256 MiB, or a task with too many approvals or usage records. Use a shorter period. |
429 evidence_pack_busy | Another pack of your organization is being built. Try again shortly. |