Preserve the proof behind every decision.
When an examiner asks "what did your screening show on March 15 at 12:36 EDT?", you need an answer that is both verifiable and instantly exportable. The Evidence Vault is our vision for that answer — with Evidence Capsule as the live implementation today.
What the Evidence Vault includes
Bitemporal audit trail
When an evidence record is durable, it preserves transaction time and source-version context for point-in-time reconstruction. Pending and unavailable evidence states remain explicit.
Point-in-time evidence reconstruction
Answer the question: 'What did our screening record on March 15 at 12:36 EDT?' Reconstruct and verify the recorded decision — the list versions, algorithm version, candidate IDs, and source provenance that were active at that moment. This verifies the stored evidence record; it does not re-execute the original matching engine.
List version records
Every source ingestion is versioned and hash-identified. Screening events are bound to specific list snapshots, not just 'the current list.'
Evidence capsule
Structured JSON export built around the Evidence Capsule: the query input, screening decision, the sources and list versions checked, deciding engine, recommended action, coverage status, and a capsule identifier that ties back to the original screening decision.
From audit log to cryptographic proof
v1 — Today
- Bitemporal audit logging
- Evidence capsule export (JSON)
- List version binding
- Point-in-time query via dashboard
v2 — Next
- Cryptographic hash chain per audit event
- Daily Merkle root
- Signed receipt with verification CLI
- Immutable S3 object-lock anchoring
v3 — Future
- Regulator response pack generator
- XBRL export support
- Third-party auditor verification portal
- Cross-jurisdiction evidence templates