8.4 FX Transaction Intake Node Mapping
Go To Mapping from FX Logical Nodes to Implementation Artifacts
The FX Transaction Intake Node maps to the Phase 0 implementation artifact that receives or creates candidate FX transaction information and introduces that information into the Phase 0 implementation network.
The implementation artifact performs the Transaction Intake Role. It prepares or receives an implementation representation of an FX Transaction Candidate, applies the required intake conventions, assigns or preserves the required identifiers, records the intake context, and publishes the implementation representation through the selected DDS Topic that realizes the FX Transaction Intake Endpoint.
Table 8-2: FX Transaction Intake Node implementation mapping.
| Mapping Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical Node | FX Transaction Intake Node |
| Primary Node Role | Transaction Intake 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 | Receive or create candidate FX transaction information and publish it for validation. |
| Primary DDS interaction | Publish to the DDS Topic that realizes the FX Transaction Intake Endpoint. |
| Primary data artifact | IDL and a generated type representing an FX Transaction Candidate. |
| Supporting artifacts | Node configuration, logging helper, traceability metadata, and startup script support. |
| Traceability expectation | Implementation artifact traces to the FX Transaction Intake Node, Transaction Intake Role, FX Transaction Intake Endpoint, and FX Transaction Candidate. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.