11.6 Control Plane Validation

Go To Top

Return to Control Plane Topics

The team should validate Control Plane behavior as part of Phase 0 acceptance. Validation should confirm that Nodes publish expected status messages, receive supported commands, reject unsupported commands, and produce logs consistent with their reported behavior.

Control Plane validation should check:

1. Required Control Plane Topics exist.
2. Control Plane Topics use approved IDL-derived types.
3. Required Nodes publish Starting status.
4. Required Nodes publish Running status after successful startup.
5. Nodes publish Stopping and Stopped status during controlled shutdown, where possible.
6. Nodes publish Failed status when startup or runtime failure prevents normal operation, where possible.
7. Nodes receive and process supported commands.
8. Nodes reject unsupported or invalid commands clearly.
9. Status messages include required Identity, Role, state, timestamp, and reason fields.
10. Logs and status messages tell a consistent story.
11. Tests or observers can collect Evidence of the expected Control Plane behavior.

Validation should include positive and negative cases. Positive cases show normal startup, status reporting, command handling, and shutdown. Negative cases show invalid Configuration, unsupported commands, malformed messages, unavailable DDS setup, or controlled failure behavior.

The team should store validation Evidence in the approved Evidence location. Evidence may include logs, captured status messages, command outputs, test reports, container logs, generated manifests, or reviewer notes.