====== 18.6 Data 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:d:data_plane|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:

  - Each included Data Plane Topic appears in the Topic Catalogue.
  - Each included Data Plane Topic identifies its purpose, carried [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], publisher [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], subscriber Nodes, QoS expectations, validation approach, and relationship to the FX Demo Logical Profile.
  - Placeholder Data Plane Topics are clearly marked as placeholders.
  - Data Plane Topics use approved IDL-derived generated types.
  - Publisher Nodes can create and publish representative messages where the baseline requires message flow.
  - Subscriber Nodes can receive and inspect representative messages where the baseline requires message flow.
  - Data Plane QoS settings match the documented expectations.
  - Data Plane validation [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supports any claims made for the Topic.
  - Data Plane implementation does not carry [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] lifecycle, command, or health messages unless the architecture explicitly defines an exception.
  - Phase 0 Data Plane scope remains consistent with the stated non-goals.

----

<WRAP centeralign>

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

</WRAP>