====== FX Node Traceability ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

FX Node Traceability relates an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] to its inherited logical source, conceptual source, FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], responsibilities, endpoints, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] participation, interactions, governance relationships, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.

FX Node Traceability allows reviewers to understand why an FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] exists, which responsibilities it performs, which endpoints it uses, which information structures it exchanges, which [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] it participates in, and which [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations apply.

FX Node Traceability also prepares implementation profiles to map FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]] to implementation artifacts without redefining the FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]].

===== Definition =====

//Traceability relationship connecting an FX logical Node to inherited logical sources, conceptual sources, roles, responsibilities, endpoints, Runtime Planes, interactions, governance relationships, and evidence expectations.//

===== Source =====

Specialization of [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_traceability|Logical Node Traceability]] from Part 2, Section 12.3, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] from Part 2, Section 6.2, [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] from Part 1, Section 7.2, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1, Section 7.10; generalised from FX node and role traceability material in the original FX Demo Reference Architecture.

===== Note =====

FX Node Traceability identifies logical responsibility. It does not prescribe process ownership, deployment ownership, operational ownership, implementation packaging, or runtime topology.

===== Example =====

The [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_computation_node|FX Cash-Flow Computation Node]] traces to the [[dido:99_annexes:annex-b-terms-and-definitions:c:cash-flow_computation_role|Cash-Flow Computation Role]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_contract_state_endpoint|FX Contract State Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation_endpoint|FX Cash-Flow Obligation Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]], the calculation context, the model version, and the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations for computed obligations.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>