====== 12.4 Report FX Node Status ======

[[fxdemo:04-part:12-phase-0-interaction-pattern-realization:start | Go To Phase 0 Interaction Pattern Realization ]]

The Report FX Node Status pattern realizes operational condition reporting for Phase 0 implementation participants.

An implementation participant publishes or records FX Node Status when it starts, becomes ready, runs normally, degrades, recovers, stops, fails, or receives a status request. The status report identifies the implementation participant, the related FX logical Node, lifecycle state, status reason, timestamp, and provenance or traceability reference, where required for Phase 0.

<WRAP table-caption>
**Table 12-2:** Report FX Node Status implementation realization.
</WRAP>

^ Realization Concern ^ Phase 0 Implementation Treatment ^
| FX logical interaction pattern | Report FX Node Status |
| Primary implementation participants | Reporting implementation participant; health and observability participant |
| Primary Runtime Plane | FX Logical Health and Observability Plane |
| Supporting Runtime Planes | FX Logical Control Plane; FX Logical Audit and Provenance Plane |
| Primary DDS Topic | Health.FX.NodeStatus |
| Primary information | FX Node Status |
| Expected processing outcome | The implementation records or publishes the participant's operational condition. |
| Logging and exception handling | Startup, shutdown, warning, degraded operation, failure, recovery, and status-publication errors follow the logging and exception-handling baseline. |
| Traceability expectation | Status reporting traces to the reporting implementation participant, the FX logical Node, the Health Reporting Role, the FX Node Status Endpoint, and the FX Node Status. |

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>