8.12 FX Registry and Coordination Node Mapping
Go To Mapping from FX Logical Nodes to Implementation Artifacts
The FX Registry and Coordination Node maps to the Phase 0 implementation artifact that supports registration, capability advertisement, compatibility awareness, and command coordination.
The implementation artifact performs the Registry and Coordination Role. It receives or records Node identity, supported roles, supported Topics, supported information-structure versions, lifecycle state, compatibility metadata, and selected Control Plane commands or acknowledgements.
Table 8-10: FX Registry and Coordination Node implementation mapping.
| Mapping Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical Node | FX Registry and Coordination Node |
| Primary Node Role | Registry and Coordination Role |
| Primary Runtime Plane | FX Logical Control Plane |
| Supporting Runtime Planes | FX Logical Health and Observability Plane; FX Logical Audit and Provenance Plane |
| Primary implementation responsibility | Support registration, capability advertisement, compatibility awareness, and command coordination. |
| Primary DDS interactions | Use DDS Topics that realize the FX Control Command Endpoint, the FX Node Status Endpoint, or other registry-related communication artifacts where Phase 0 requires them. |
| Primary data artifacts | IDL and generated types representing the FX Control Command, the FX Command Acknowledgement, and FX Node Status. |
| Supporting artifacts | Registry helper module, coordination helper module, configuration artifacts, logging helper, and traceability metadata. |
| Traceability expectation | Implementation artifact traces to the FX Registry and Coordination Node, Registry and Coordination Role, FX Control Command Endpoint, FX Node Status Endpoint, FX Control Command, FX Command Acknowledgement, and FX Node Status. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.