FX Node Traceability

Return to Terms and Definitions

Discussion

FX Node Traceability relates an FX logical Node to its inherited logical source, conceptual source, FX Node Roles, responsibilities, endpoints, Runtime Plane participation, interactions, governance relationships, and Evidence expectations.

FX Node Traceability allows reviewers to understand why an FX logical Node exists, which responsibilities it performs, which endpoints it uses, which information structures it exchanges, which Runtime Planes it participates in, and which Evidence expectations apply.

FX Node Traceability also prepares implementation profiles to map FX logical Nodes to implementation artifacts without redefining the FX logical 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 Logical Node Traceability from Part 2, Section 12.3, Logical Node from Part 2, Section 6.2, Node from Part 1, Section 7.2, and 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 FX Cash-Flow Computation Node traces to the Cash-Flow Computation Role, FX Contract State Endpoint, FX Cash-Flow Obligation Endpoint, Logical Data Plane, Logical Audit and Provenance Plane, the calculation context, the model version, and the Evidence expectations for computed obligations.

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