This is an old revision of the document!
FX Information Structure Traceability
Discussion
FX Information Structure Traceability relates an FX logical information structure to its inherited logical source, conceptual source, semantic context, producing FX logical Nodes, consuming FX logical Nodes, endpoints, interactions, Runtime Planes, governance constraints, lineage, and Evidence expectations.
FX Information Structure Traceability supports interpretation, validation, review, compatibility assessment, replay, reconstruction, and Evidence planning. It allows reviewers to identify which FX information definition governed an information instance, which FX logical Node produced it, which FX logical Node consumed it, which endpoint carried it, which Runtime Plane framed it, and which Evidence expectations apply.
FX Information Structure Traceability also supports version review. FX logical Nodes that exchange information rely on compatible versions of the relevant FX logical information structures.
Definition
Traceability relationship connecting FX logical information structures to inherited logical sources, conceptual sources, Nodes, endpoints, interactions, Runtime Planes, governance constraints, lineage, and evidence expectations.
Source
Specialisation of Logical Data Structure Traceability from Part 2, Section 12.5, Logical Data Structure Definition and Logical Data Structure Instance from Part 2, Sections 8.2 and 8.3, Data Structure Definition and Data Structure Instance from Part 1, Sections 7.7 and 7.8, and Traceability from Part 1, Section 7.10; generalised from FX information-structure, provenance, lineage, and evidence material in the original FX Demo Reference Architecture.
Note
FX Information Structure Traceability does not prescribe a schema language, serialisation format, database structure, ontology language, generated code representation, wire format, or runtime payload.
Example
An FX Validation Result traces to its FX Transaction Candidate input, validation rule version, FX Validation Node, FX Validation Result Endpoint, the Logical Data Plane, the FX Provenance Record, and the Evidence expectations for validation review.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.