Go To Phase 0 Interaction Pattern Realization
The Compute FX Cash-Flow Obligations pattern realizes Phase 0 computation of projected or derived FX cash-flow obligations.
The implementation participant performing the Cash-Flow Computation Role consumes FX Contract State and related context, applies the selected Phase 0 calculation approach, produces FX Cash-Flow Obligation, and publishes it to the cash-flow obligation DDS Topic.
Table 12-7: Compute FX Cash-Flow Obligations implementation realization.
| Realization Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical interaction pattern | Compute FX Cash-Flow Obligations |
| Primary implementation participant | Cash-flow computation implementation participant |
| Primary Runtime Plane | FX Logical Data Plane |
| Supporting Runtime Plane | FX Logical Audit and Provenance Plane |
| Input DDS Topics | Data.FX.ContractState; semantic or transaction-related Topics as required by Phase 0 |
| Output DDS Topic | Data.FX.CashFlowObligation |
| Primary IDL / generated types | FxContractState; FxCashFlowObligation |
| Expected processing outcome | Implementation publishes projected or derived cash-flow obligation information with input reference, calculation context, model reference where applicable, producing participant, and timestamp. |
| Logging and exception handling | Missing input, unsupported contract state, calculation error, publication failure, and retry conditions follow the logging and exception-handling baseline. |
| Audit and provenance expectation | Computation records preserve input references, calculation context, model or rule version, producing participant, timestamp, and output reference. |
| Traceability expectation | Interaction traces to FX Cash-Flow Computation Node, Cash-Flow Computation Role, FX Cash-Flow Obligation Endpoint, FX Cash-Flow Obligation, and implementation participant. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.