8.7 FX Contract State Node Mapping
Go To Mapping from FX Logical Nodes to Implementation Artifacts
The FX Contract State Node maps to the Phase 0 implementation artifact that establishes, updates, or reports FX Contract State from validated and semantically interpreted information.
The implementation artifact performs the Contract State Management Role. It consumes applicable validation and semantic interpretation outputs, applies the Phase 0 contract state logic, produces an implementation representation of FX Contract State, and publishes that state through the DDS Topic that realizes the FX Contract State Endpoint.
Table 8-5: FX Contract State Node implementation mapping.
| Mapping Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical Node | FX Contract State Node |
| Primary Node Role | Contract State Management Role |
| Primary Runtime Plane | FX Logical Data Plane |
| Supporting Runtime Planes | FX Logical Audit and Provenance Plane |
| Primary implementation responsibility | Establish, update, or report FX Contract State. |
| Primary DDS interactions | Subscribe to the required validation and semantic interpretation DDS Topics; publish to the DDS Topic that realizes the FX Contract State Endpoint. |
| Primary data artifacts | IDL and generated types representing the FX Validation Result, the FX Semantic Assertion, and FX Contract State. |
| Supporting artifacts | Contract state helper module, state rule configuration, logging helper, and traceability metadata. |
| Traceability expectation | Implementation artifact traces to the FX Contract State Node, Contract State Management Role, FX Contract State Endpoint, and FX Contract State. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.