12.2 Placeholder Data Plane Topics

Go To Top

Return to Data Plane Topics

Phase 0 may include placeholder Data Plane Topics when the team needs to demonstrate Topic structure, type generation, publisher/subscriber wiring, or future FX demonstration flow without implementing full domain behavior.

A placeholder Data Plane Topic should still follow the same discipline as any other Topic. The Topic Catalogue should identify:

1. Topic name.
2. Purpose.
3. Placeholder status.
4. Carried Data Structure Definition.
5. Publisher Node or Nodes.
6. Subscriber Node or Nodes.
7. Expected QoS profile.
8. Validation approach.
9. Future intended use.
10. Conditions for replacing, extending, or retiring the placeholder.

The team should clearly mark placeholder Topics so reviewers do not mistake them for completed domain capabilities. Placeholder status should appear in the Topic Catalogue, Node Catalogue, relevant tests, and, where applicable, acceptance Evidence.

A placeholder Topic should still use an approved IDL-derived type. The type may remain simple, but it should not bypass the governed type-generation workflow. Even simple placeholder Topics should demonstrate that the team can define, generate, build, publish, subscribe, and validate typed Data Plane messages.