10.7 Node Command Handling [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 10.7 Node Command Handling ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:10-node-implementation-pattern:start | Return to Node Implementation Pattern ]]

A Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] may support simple commands through the approved [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] command topic. Command handling allows the team to demonstrate basic runtime coordination without introducing full operational management.

Phase 0 command handling may include:

  - Start.
  - Pause.
  - Resume.
  - Restart.
  - ReportStatus.
  - Stop.

The team should define which commands each Node supports. A Node should reject unsupported commands clearly rather than ignoring them silently. The Node should log received commands, validation results, accepted actions, rejected actions, and final command outcomes.

A command message should identify:

  - Command identity.
  - Command type.
  - Target Node or target role.
  - Timestamp.
  - Issuer or source, where applicable.
  - Parameters, where needed.
  - Correlation identifier, where needed.

Command handling should not bypass [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] discipline. For example, a ''Stop'' command should lead to ''Stopping'' and ''Stopped'' status if the Node can shut down normally. A ''ReportStatus'' command should cause the Node to publish current status without changing its Lifecycle state.

Phase 0 command handling should remain simple. It should prove that Nodes can receive and act on controlled instructions. It should not attempt to implement a full orchestration, scheduling, security, policy, or enterprise operations framework.

----

<WRAP centeralign>

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

</WRAP>