product · evidence packs
Evidence Packs
The artefact you hand an auditor. Generated on demand from the tape, mapped to the framework they name, sealed so they can verify it without a Wytness account.
An auditor cannot use a JSON log. An Evidence Pack turns the period they ask about into the document they expect: what ran, under which controls, with the signatures and the chain walk attached. It is built from the record Ledger keeps, and it verifies against your key and ours on their machine, offline.
what you get
One pack, six parts.
executive summary
What was recorded, over which period, by which agents, and what the verifier found.
control mapping
Control by control against the framework you pick: EU AI Act (Articles 12, 13, 15), SOC 2 Type II, ISO 27001. GDPR Article 30 and HIPAA follow Q1 2027.
sampled events
Events with their signatures, so the auditor checks the primitive, not a summary of it.
chain attestation
The hash-chain walk for the period, breaks surfaced, not buried.
methodology and limits
An honest section on what the pack proves, what it samples, and what it cannot see.
sealed download
A signed, dated JSON pack sealed with the Wytness key, carrying the signed bytes and the public keys, so it verifies offline. Print it for the file.
Anyone can check a pack at Verify an Evidence Pack — the check runs in the browser and makes no network request. On cancellation, your history is handed over as signed Evidence Packs, one per year, before anything is deleted.
availability
What each tier gets
| Starter | Growth | Business | Enterprise | |
|---|---|---|---|---|
| Evidence Packs · generated on demand · sealed download | — | — | ✓ | ✓ |
| Handover packs on cancellation · one per year | ✓ | ✓ | ✓ | ✓ |