Data Freshness
Reproducible evidence still needs freshness context.
A screening result can be deterministic and replayable while still depending on the age of the source data. CCAI treats freshness as part of the evidence package rather than a footnote.
Freshness signals.
The goal is to show which data version was used and whether newer source data may require review or re-screening.
| Snapshot build timestamp | Shows when CCAI assembled the local screening snapshot. |
| Upstream source timestamp | Shows when the provider or regulator last published source data, when available. |
| Snapshot age | Discloses the age of the data used for a screening result. |
| Freshness policy | Compares snapshot age against the customer or environment policy. |
| Stale-window review | Identifies results that may need review or re-screening after newer source data arrives. |
| Sentinel observations | Surfaces source-age findings and freshness evidence for operator attention. |
| Operational queue items | Shows when freshness or restore-evidence context needs a human handoff instead of silent automation. |
Why it matters.
Regulators often care about whether screening data was current at the time of review. Freshness metadata helps customers explain what was known, when it was known, and whether later source updates created a stale-window review obligation.
Start with examination readiness.
Freshness, reliance, human review, and evidence all meet in the regulatory examination package.