FX Interaction Traceability relates an FX logical interaction pattern to its inherited Part 2 interaction pattern, participating FX logical Nodes, Node Roles, endpoints, information structures, Runtime Planes, governance constraints, and Evidence expectations.
FX Interaction Traceability supports review of how the FX Demo Logical Profile behaves. It identifies the structure of recurring interactions such as Register FX Logical Node, Report FX Node Status, Intake FX Transaction Candidate, Validate FX Transaction Candidate, Interpret FX Transaction Semantics, Establish or Update FX Contract State, Compute FX Cash-Flow Obligations, Request FX Policy Decision, Release FX Information to Oversight Participant, Record FX Audit and Provenance, and Replay or Reconstruct FX Information.
FX Interaction Traceability prepares Parts 4 and 5 to map, test, observe, and document each FX logical interaction.
Traceability relationship connecting an FX logical interaction pattern to inherited Part 2 interaction patterns, Nodes, roles, endpoints, information structures, Runtime Planes, governance constraints, and evidence expectations.
Specialisation of Logical Interaction Traceability from Part 2, Section 12.7, Logical Interaction Patterns from Part 2, Section 10, and Traceability from Part 1, Section 7.10; generalised from FX use-case and interaction-sequence material in the original FX Demo Reference Architecture.
FX Interaction Traceability records the logical structure of an FX interaction. It does not prescribe sequence-diagram notation, protocol exchange, test-script format, runtime message capture, or evidence file format.
The Compute FX Cash-Flow Obligations pattern traces to the FX Cash-Flow Computation Node, Cash-Flow Computation Role, FX Contract State Endpoint, FX Cash-Flow Obligation Endpoint, FX Contract State, FX Cash-Flow Obligation, the Logical Data Plane, the Logical Audit and Provenance Plane, and computation Evidence expectations.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.