Audit And Provenance Plane

Return to Terms and Definitions

Discussion

The Audit and Provenance Plane supports reconstruction, accountability, lineage, and defensibility. It carries or records information about what happened, when it happened, which Nodes or processes participated, which information served as input, which rules or versions the system applied, which decisions the system made, and how outputs relate to inputs.

The Audit and Provenance Plane helps the architecture support review, replay, recovery, evidence, conformance assessment, and long-term governance. It preserves relationships among Data Structure Instances, Nodes, Communication Endpoints, policy decisions, analytical outputs, and evidence.

A later implementation profile may realise Audit and Provenance Plane interactions through audit topics, provenance records, event stores, immutable logs, evidence packages, lineage graphs, release audit records, or replay records. Those mechanisms do not redefine the Audit and Provenance Plane.

Definition

Runtime Plane supporting auditability, provenance, lineage, reconstruction, and defensibility

Source

Adapted from FX Demo Reference Architecture, Section 4.4.6, Audit and Provenance Plane, and Section 4.8, Persistence, Audit, and Provenance; informed by SIP-RA traceability, audit, review, and reproducible processing concerns and by FDIS-RA evidence, provenance, auditability, and defensibility concerns.

Note

The Audit and Provenance Plane is not merely logging. Logs may contribute to audit or provenance by preserving traceable information that supports reconstruction, review, or evidence.

Example

A provenance record linking an analytical assertion to its input data, producing Node, model version, timestamp, and calculation run, may belong to the Audit and Provenance Plane.