Logical Audit and Provenance Plane

Go up to Terms and Definitions

The Logical Audit and Provenance Plane supports reconstruction, accountability, lineage, review, replay, recovery, auditability, and defensibility for FX logical processing.

Logical Audit and Provenance Plane interactions record or relate what happened, when it happened, which FX logical Nodes 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 Logical Audit and Provenance Plane preserves relationships among FX Transaction Candidates, FX Transaction Records, FX Validation Results, FX Semantic Assertions, FX Contract States, FX Cash-Flow Obligations, FX Policy Decisions, FX Release Packages, FX Audit Records, FX Provenance Records, FX Replay Requests, FX Replay Results, FX logical Nodes, FX endpoints, and Evidence expectations.

Runtime Plane supporting Audit, Provenance, lineage, reconstruction, replay, and defensibility

Specialization of Logical Audit and Provenance Plane from Part 2: Distributed Node-Based Logical Architecture, Section 9.6, and Audit and Provenance Plane from Part 1: Conceptual Architecture, Section 8.6; generalised from FX audit, provenance, persistence, replay, reconstruction, and evidence-support material in the original FX Demo Reference Architecture.

The Logical Audit and Provenance Plane is not merely logging. Logs contribute to Audit or Provenance only when the implementation and evidence layers preserve traceable information that supports reconstruction, review, or evidence.

An FX Provenance Record links an FX Cash-Flow Obligation to the FX Contract State, FX Semantic Assertion, calculation context, model version, producing FX logical Node, and timestamp.

Return to Top