9.3 Control Plane Type Definitions

Go To Top

Return to DDS / IDL / Type Generation

Control Plane type definitions support Node coordination, runtime visibility, and operational Evidence. Phase 0 should define the minimum Control Plane structures needed to demonstrate that Nodes can start, report status, receive simple commands, stop, and produce observable Evidence.

At minimum, the Control Plane type model should support:

1. Node Identity
2. Node Role
3. Node Lifecycle state
4. Status timestamp
5. Status message or reason
6. Command identity
7. Command target
8. Command type
9. Command timestamp
10. Command parameters, where needed
11. Command result or acknowledgement, where needed

The Control Plane type definitions should support Lifecycle states such as Starting, Running, Degraded, Recovering, Stopping, Stopped, Failed, or Unknown, which apply to Phase 0 Node behavior.

The team should keep Control Plane structures focused on operational coordination and observability. Control Plane types should not carry business Data, financial transaction payloads, ACTUS computation results, or authorized release packages unless the architecture explicitly defines those topics as Control Plane interactions.