7 · Audit

For Both Executive and Technical Readers

Bundle the record. Every element that produced the answer, in one typed object.

The answer is not a string. It is a record with provenance.

Step 7 assembles the AuditRecord from every artifact the pipeline has produced: the formal estimand, the certificates, the model IDs and versions, the evidence set, the posterior, and the outputs of any epistemic checks. The AuditRecord is versioned, serialisable, and diff-able. The same question asked twice with identical evidence and model versions always produces an identical AuditRecord.

Audited results is a concrete artifact, not a promise. The BPMN gateway receives the AuditRecord, not the posterior. The posterior is a field inside it.

All prior step artifacts in. One typed, versioned AuditRecord out.

IN CausalQuery, estimand, certificates, posterior, epistemic check outputs
OUT AuditRecord, typed, versioned, reproducible

Audit Record q-20260721-0041
EstimandP(Sepsis | do(Treatment=empirical), …)
Modelsepsis.bayes, version 2.1.0
IdentificationAttached Identification Certificate
EvidenceFull set of soft and hard evidence bindings entered
PosteriorSepsis = 0.83
RobustnessAttached Robustness Report
PatternAttached Pattern Explanation
Timestamp: 2026-07-21, 15:42:00 UTC. Every certificate this query produced, in one traceable record.

Every field is a typed artifact, not a comment.

The AuditRecord is designed for adversarial inspection. Every field can be read independently. The identification certificate names its criterion and adjustment set, a reviewer can check whether the back-door criterion was correctly applied without re-running the pipeline. The record is also what feeds the BPMN gateway downstream.

Robustness and Pattern Analysis run at Audit, not Execute.

Robustness: perturbs CPT parameters and re-runs inference. Mandatory field in the AuditRecord. Robustness →

Pattern Analysis: feature distinction and evidence attribution. Both fields in the AuditRecord. Pattern Analysis →

Validation: runs pre-deployment, not per-query. The model version field in the AuditRecord traces to it. Validation →

Three epistemic components feed Audit. BPMN consumes it.

Robustness →   Pattern Analysis →   Validation →   BPMN Integration →