Core Concepts
Evidence
Exportable proof packages for consent publish and rights deletion.
Evidence
What it is
An Evidence package is a structured, exportable record assembled on read from domain events and snapshots, not a separate write-time archive product.
Kinds (v1)
| Kind | Source |
|---|---|
| Consent publish | Accord publish events / version context |
| Rights deletion | Case Activity and fulfillment outcomes |
Why it exists
Operators need more than raw logs when someone asks "what happened?" Evidence packages support internal review and export (JSON, CSV, report UI).
How it differs from Activity
| Activity | Evidence | Server logs |
|---|---|---|
| Event timeline in the console | Portable package for a publish or case | Debug/ops noise |
| Who did what, in order | Facts + steps for review | Not customer-facing |
Honesty (Beta)
- Assembled from Erasure-mediated actions, not proof about systems you never connected
- Not marketed as a cryptographically sealed legal WORM archive
- Useful operational proof, not a substitute for counsel
Related
- Consent · Deletion jobs
- Guide: Generate evidence · DPDP: Evidence
For how evidence differs from audit trails and logs, see Audit trail vs evidence and the privacy evidence hub.