18.5 Control Plane Acceptance Criteria [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.
====== 18.5 Control Plane Acceptance Criteria ======

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

[[fxdemo:05-part:18-acceptance-criteria:start | Return to Acceptance Criteria ]]

The [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] satisfies Phase 0 acceptance when it provides observable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] that required [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]] started, reported status, responded to commands where applicable, and stopped or failed in a controlled way.

Control Plane acceptance requires:

  - Required Control Plane Topics exist and use approved names.
  - Control Plane Topics use approved IDL-derived [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definitions]].
  - Required Nodes publish status to the approved Node Status Topic.
  - Status messages identify Node identity, Node role, lifecycle state, timestamp, and reason or message.
  - Nodes publish expected lifecycle transitions during startup and shutdown.
  - Nodes report Failed, Degraded, or Recovering where applicable.
  - Supported commands can be published to the approved Node Command Topic.
  - Nodes receive, validate, and act on supported commands where applicable.
  - Nodes reject unsupported or invalid commands clearly.
  - Control Plane QoS settings match the documented expectations.
  - An observer, test harness, DDS diagnostic tool, or captured-message mechanism can inspect Control Plane behavior.
  - Logs and captured status messages provide consistent Evidence of Node behavior.

----

<WRAP centeralign>

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

</WRAP>