Evidence and auditability

Immutable evaluation evidence

A completed Check preserves the inputs and execution facts required to explain its output:

• Applicant and submitted subject snapshot;
• normalized provider query;
• requested datasets and promoted source versions;
• policy version and complete policy snapshot;
• raw and normalized hit evidence;
• feature-level score contributions;
• decision and suppression evidence;
• provider and end-to-end timing.

Later policy or source changes do not rewrite an earlier Check.

Retrieve the Check as structured JSON or human-readable Markdown from the same resource:

GET /v1/checks/{check_id}
Accept: application/json

GET /v1/checks/{check_id}
Accept: text/markdown

Mutable workflow, immutable history

Alert assignment and state are operationally mutable. Each action also writes an immutable Alert event recording the actor, timestamp, transition, and relevant evidence. Retrieve the timeline from GET /v1/alerts/{alert_id}/events.

Four-eyes policy is copied onto each Alert when it is created. A later global policy change therefore does not silently change the approval control for existing work.

Evidence exports

GET /v1/checks/{check_id}/export produces JSON, CSV, Markdown, or PDF. Use:

• JSON for machine reconciliation;
• CSV for tabular controls and batch analysis;
• Markdown for human-readable, diffable records;
• PDF for fixed examiner or case attachments.

Exports are representations of the Check; they do not create a second product resource.

Scope of claims

Evidence records what ran and how it was evaluated. It does not by itself establish universal source coverage or an accuracy claim. Dataset rights, coverage, validation corpora, and independent assurance remain separate release and diligence controls.