11.3 Node Command Topic [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.

====== 11.3 Node Command Topic ======

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

[[fxdemo:05-part:11-control-plane-topics:start | Return to Control Plane Topics ]]

The [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] Command Topic carries simple operational commands to Phase 0 Nodes. It allows the team to demonstrate basic runtime coordination without introducing a full orchestration framework.

The recommended topic name is:

<code>
Control.Node.Command
</code>

A Node Command message should identify:

  - Command identity.
  - Command type.
  - Target Node, target Node Role, or broadcast target.
  - Timestamp.
  - Issuer or source, where applicable.
  - Correlation identifier, where needed.
  - Command parameters, where needed.
  - Expiry or timeout, where needed.

Phase 0 may support command types such as:

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

The team should define which commands each Node supports. A Node should reject unsupported commands clearly and should report the rejection through logs, status messages, command acknowledgements, or test Evidence as appropriate.

The Node Command Topic should not become a substitute for security, orchestration, scheduling, or policy enforcement. Phase 0 command handling should remain simple and should prove only that Nodes can receive, validate, act on, or reject controlled instructions.

----

<WRAP centeralign>

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

</WRAP>