Evidence layer
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.
Core capabilities
What the Evidence Vault includes
Bitemporal audit trail
Every screening event is recorded with both transaction-time (when the event occurred) and valid-time (which list version was active). This supports point-in-time reconstruction and historical compliance review.
Point-in-time screening reconstruction
Answer the question: 'What would our screening have shown on March 15 at 12:36 EDT?' Reconstruct any historical screening against the exact list versions and algorithm version that were active at that moment.
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 export format containing query input, screened_at timestamp, list_versions, algorithm_version, match_score, recommendation, reviewer_action, and audit_id — in JSON.
Roadmap
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