18.4 Node Acceptance Criteria

Go To Top

Return to Acceptance Criteria

A Phase 0 Node satisfies acceptance when it implements the agreed Node pattern, participates in the expected topics, reports lifecycle status, handles Configuration and errors predictably, and produces reviewable logs.

Node acceptance requires:

1. The Node Catalogue identifies the Node name, Node role, purpose, implementation language, Configuration source, published Topics, subscribed Topics, generated types, lifecycle states, supported commands, logging behavior, and tests.
2. The Node loads and validates approved Configuration before completing startup.
3. The Node reports Starting during initialization where possible.
4. The Node reports Running after successful startup.
5. The Node reports Stopping and Stopped during controlled shutdown where possible.
6. The Node reports Failed when it cannot complete required startup or runtime behavior where possible.
7. The Node uses approved IDL-derived generated types for Topic messages.
8. The Node publishes or subscribes only to Topics documented for its role unless the team has approved an exception.
9. The Node handles supported commands according to its Node profile.
10. The Node rejects unsupported or invalid commands clearly.
11. The Node logs startup, Configuration source, DDS participation, lifecycle transitions, command handling, warnings, errors, and shutdown.
12. The Node exits with meaningful exit behavior when it cannot continue safely.
13. The Node implementation follows the file header and inline documentation rules defined in Section 7.10.