12.5 Intake FX Transaction Candidate
Go To Phase 0 Interaction Pattern Realization
The Intake FX Transaction Candidate pattern realizes the introduction of candidate FX transaction information into the Phase 0 implementation network.
The implementation participant performing the Transaction Intake Role receives or creates an FX Transaction Candidate, applies intake conventions, assigns or preserves identifiers, records source context, and publishes the generated type representation to the DDS Topic that realizes the FX Transaction Intake Endpoint.
Table 12-3: Intake FX Transaction Candidate implementation realization.
| Realization Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical interaction pattern | Intake FX Transaction Candidate |
| Primary implementation participant | Transaction intake implementation participant |
| Primary Runtime Plane | FX Logical Data Plane |
| Supporting Runtime Plane | FX Logical Audit and Provenance Plane |
| Primary DDS Topic | Data.FX.TransactionCandidate |
| Primary IDL / generated type | FxTransactionCandidate generated type |
| Expected processing outcome | Implementation publishes candidate FX transaction information for validation. |
| Logging and exception handling | Intake success, malformed input, missing required intake context, publication failure, and retry conditions follow the logging and exception-handling baseline. |
| Audit and provenance expectation | Intake records preserve source context, timestamp, producing participant, and candidate identifier, where required by Phase 0. |
| Traceability expectation | Interaction traces to FX Transaction Intake Node, Transaction Intake Role, FX Transaction Intake Endpoint, FX Transaction Candidate, and implementation participant. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.