Go To Mapping from FX Logical Nodes to Implementation Artifacts
The FX Validation Node maps to the Phase 0 implementation artifact that validates candidate FX transaction information against the Phase 0 validation expectations.
The implementation artifact performs the Structural Validation Role. It subscribes to the DDS Topic that realizes the FX Transaction Intake Endpoint, consumes the implementation representation of an FX Transaction Candidate, applies the Phase 0 validation logic, produces an implementation representation of an FX Validation Result, and publishes that result through the DDS Topic that realizes the FX Validation Result Endpoint.
Table 8-3: FX Validation Node implementation mapping.
| Mapping Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical Node | FX Validation Node |
| Primary Node Role | Structural Validation Role |
| Primary Runtime Plane | FX Logical Data Plane |
| Supporting Runtime Planes | FX Logical Audit and Provenance Plane; FX Logical Health and Observability Plane |
| Primary implementation responsibility | Validate candidate FX transaction information and publish validation results. |
| Primary DDS interactions | Subscribe to the DDS Topic that realizes the FX Transaction Intake Endpoint; publish to the DDS Topic that realizes the FX Validation Result Endpoint. |
| Primary data artifacts | IDL and generated types representing the FX Transaction Candidate and the FX Validation Result. |
| Supporting artifacts | Validation helper module, Node configuration, logging helper, exception-handling convention, and traceability metadata. |
| Traceability expectation | Implementation artifact traces to the FX Validation Node, Structural Validation Role, FX Transaction Intake Endpoint, FX Validation Result Endpoint, FX Transaction Candidate, and FX Validation Result. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.