12.6 Data Plane Validation

Go To Top

Return to Data Plane Topics

The team should validate any Data Plane Topics that form part of the Phase 0 Baseline. Validation should confirm that Topics use approved names, approved IDL-derived types, expected publishers, expected subscribers, expected QoS profiles, and observable test behavior.

Data Plane validation should check:

1. Required Data Plane Topics exist.
2. Topic names follow the naming convention.
3. Topics use approved IDL-derived data structures.
4. Generated bindings compile or load successfully.
5. Publisher Nodes can create and publish representative messages.
6. Subscriber Nodes can receive and inspect representative messages.
7. Logs identify publication and subscription behavior where appropriate.
8. Tests or observer tools can confirm expected message flow.
9. Placeholder Topics remain clearly marked as placeholders.
10. QoS settings match the Topic Catalogue.
11. Validation Evidence supports the acceptance criteria.

Validation should remain proportional to the Phase 0 scope. If a Data Plane Topic only demonstrates typed message flow, the validation should prove typed message flow. If a Topic claims to represent a validation result, cash-flow request, Provenance record, or release candidate, the validation should prove the behavior claimed for that Topic.

The team should store Data Plane validation Evidence in the approved Evidence location. Evidence may include logs, test output, captured messages, generated-file manifests, build output, or reviewer notes.