FX Endpoint Traceability

Return to Terms and Definitions

FX Endpoint Traceability relates an FX logical Communication Endpoint to its inherited logical source, conceptual source, participating FX logical Nodes, Communication Roles, FX information structures, Runtime Plane classification, governance constraints, and Evidence expectations.

FX Endpoint Traceability supports reviewing the movement of FX information. It identifies which FX logical Nodes produce information, which Nodes consume information, which information structures the endpoint carries, which Runtime Plane frames the exchange, and which policy, governance, audit, provenance, or Evidence expectations apply.

FX Endpoint Traceability also protects the distinction between FX logical Communication Endpoints and implementation mechanisms. Part 4 maps FX logical Communication Endpoints to selected implementation artifacts, but the FX logical endpoint remains the architectural relationship to trace.

Traceability relationship connecting an FX logical Communication Endpoint to inherited logical sources, conceptual sources, participating Nodes, Communication Roles, information structures, Runtime Plane classifications, governance constraints, and evidence expectations.

Specialization of Logical Endpoint Traceability from Part 2, Section 12.4, Logical Communication Endpoint from Part 2, Section 7.2, Communication Endpoint from Part 1, Section 7.6, and Traceability from Part 1, Section 7.10; generalised from FX endpoint, topic, and interaction traceability material in the original FX Demo Reference Architecture.

FX Endpoint Traceability does not imply a DDS Topic, REST resource, RPC method, message queue, event stream, file, database table, or network route.

The FX Cash-Flow Obligation Endpoint traces to the FX Cash-Flow Computation Node, FX Policy and Release Node, FX Audit and Provenance Node, the FX Cash-Flow Obligation information structure, the Logical Data Plane, and the Evidence expectations for computation review.