Provenance Recording Role
Discussion
The Provenance Recording Role identifies responsibility for recording lineage relationships among FX information structures, Nodes, endpoints, interactions, rules, versions, models, decisions, and outputs.
This role includes linking inputs to outputs, associating assertions with rule versions or model versions, identifying producing and consuming Nodes, preserving timestamps, and recording relationships needed for replay, reconstruction, review, and evidence.
The Provenance Recording Role primarily participates in the FX Logical Audit and Provenance Plane. It supports validation, semantic interpretation, contract state, cash-flow computation, policy decisions, release packages, replay, and reconstruction.
Definition
responsible for recording lineage relationships among FX information structures, Nodes, endpoints, interactions, rules, versions, models, decisions, and outputs
Source
Specialization of Logical Node Role from Part 2: Distributed Node-Based Logical Architecture, Section 6.4, Logical Information Lineage from Part 2: Distributed Node-Based Logical Architecture, Section 8.10, Traceability from Part 1: Conceptual Architecture, Section 7.10, and Evidence from Part 1: Conceptual Architecture, Section 7.9; generalised from provenance and lineage material in the original FX Demo Reference Architecture.
Note
The Provenance Recording Role does not prescribe a provenance store, graph database, event store, log format, lineage tool, database, or evidence repository.
Example
The FX Audit and Provenance Node performs the Provenance Recording Role when it links an FX Cash-Flow Obligation to the FX Contract State, model version, semantic assertion, and the producing Node that generated it.