This is an old revision of the document!
FX Audit and Provenance Node
Discussion
The FX Audit and Provenance Node records and relates audit, provenance, lineage, and evidence-supporting information for FX logical interactions.
The FX Audit and Provenance Node performs audit and provenance recording responsibilities. It records relationships among FX Transaction Candidates, FX Validation Results, FX Semantic Assertions, FX Contract States, FX Cash-Flow Obligations, FX Policy Decisions, FX Release Packages, producing Nodes, consuming Nodes, endpoints, Runtime Planes, timestamps, rule versions, model versions, and evidence expectations.
The FX Audit and Provenance Node participates primarily in the FX Logical Audit and Provenance Plane. It also supports other planes by preserving information about interactions, decisions, and outputs.
Definition
responsible for recording and relating audit, provenance, lineage, and evidence-supporting information
Source
Specialization of Logical Node from Part 2: Distributed Node-Based Logical Architecture, Section 6.2, Logical Audit and Provenance Plane from Part 2: Distributed Node-Based Logical Architecture, Section 9.6, Evidence from Part 1: Conceptual Architecture, Section 7.9, and Traceability from Part 1: Conceptual Architecture, Section 7.10; generalised from audit, provenance, persistence, replay, and evidence material in the original FX Demo Reference Architecture.
Note
The FX Audit and Provenance Node is not merely a logging service. Logs contribute to audit or provenance only when later parts preserve traceable information supporting reconstruction, review, or evidence.
Example
The FX Audit and Provenance Node records a provenance relationship linking an FX Cash-Flow Obligation to the FX Contract State, semantic assertion, computation context, model version, producing Node, and timestamp.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.