Evidence
Every decision produces a verifiable record.
This is not a log or a score. It is a complete, structured account of what was decided, why, and with what data.
Evidence Bundle
The core evidence object is the DecisionEventPackage. Once assembled, it is immutable — no field can be modified, appended, or removed.
| Component | Content |
|---|---|
| Resolution trace | Which layers were attempted, what each returned, where resolution occurred |
| Confidence basis | Score and threshold at the resolving layer |
| Rule binding | Rule pack version, rule pack hash, specific rules triggered |
| Data binding | Watchlist snapshot ID, snapshot hash, sources consulted |
| Config snapshot | Tenant configuration version active at execution time |
| Lineage | Full path from raw input through normalization, clustering, resolution, and output |
| Entity context | Input entity, resolved canonical match, entity type, source batch |
| Execution metadata | Trace ID, batch ID, decision run ID, timestamps, execution hash |
Example evidence record
Try It
Screening Demo
Enter an entity name to see resolution, evidence lineage, and receipt binding.
Try "Acme Shipping Ltd" (L1 match) or "Global Trade Partners" (L4 escalation).
Receipt References
After evidence assembly, the package is handed to Intelligent Analyst for attestation. The receipt is stored in the IA truth ledger and can be independently retrieved and verified without access to CCAI.
| Field | Purpose |
|---|---|
| receipt_id | Unique identifier for the attestation receipt |
| receipt_hash | SHA-256 hash binding the receipt to the decision |
| receipt_status | BOUND (attested) or ATTESTATION_PENDING (IA unavailable) |
| bound_at | Timestamp of attestation |
Audit Export
Evidence can be exported in formats suitable for regulatory examination. Audit reports include governance context: rule pack version, threshold policy, approval chain, and configuration snapshot.
| Type | Format | Contents |
|---|---|---|
| Screening results | CSV | Entity results with layer, confidence, decision |
| Evidence bundle | JSON | Full DecisionEventPackage per entity |
| Audit report | Regulatory narrative with evidence chain and governance metadata | |
| Lineage export | JSON | Complete input-to-output trace per entity |
| Receipt archive | ZIP | VeracityReceipts for all entities in a batch |
Why this matters for regulated use.
What was the decision?
CCAI records the resolution outcome and decision state for every entity.
What data was used?
The watchlist snapshot ID and hash identify exactly which version of reference data was consulted. Snapshot immutability ensures the data cannot be retroactively changed.
What rules were applied?
Rule pack versioning with approval chains provides a complete governance trail. The configuration snapshot records the exact policy state at execution time.
Can the decision be reproduced?
The combination of input entity, configuration snapshot, watchlist snapshot, and rule pack version is sufficient to replay any decision.
Is the evidence independently verifiable?
The VeracityReceipt is stored in a separate system (IA) with its own integrity guarantees. The hash binding allows independent verification without trusting either system alone.
CCAI does not claim to eliminate compliance risk. It provides the evidence infrastructure that allows regulated institutions to demonstrate the rigor, consistency, and traceability of their screening operations.