18.6 Data Plane Acceptance Criteria

Go To Top

Return to Acceptance Criteria

The Data Plane satisfies Phase 0 acceptance when any included Data Plane topics follow the approved naming, typing, participation, QoS, validation, and placeholder rules.

Data Plane acceptance requires:

1. Each included Data Plane Topic appears in the Topic Catalogue.
2. Each included Data Plane Topic identifies its purpose, carried Data Structure Definition, publisher Nodes, subscriber Nodes, QoS expectations, validation approach, and relationship to the FX Demo Logical Profile.
3. Placeholder Data Plane Topics are clearly marked as placeholders.
4. Data Plane Topics use approved IDL-derived generated types.
5. Publisher Nodes can create and publish representative messages where the baseline requires message flow.
6. Subscriber Nodes can receive and inspect representative messages where the baseline requires message flow.
7. Data Plane QoS settings match the documented expectations.
8. Data Plane validation Evidence supports any claims made for the Topic.
9. Data Plane implementation does not carry Control Plane lifecycle, command, or health messages unless the architecture explicitly defines an exception.
10. Phase 0 Data Plane scope remains consistent with the stated non-goals.