===== 20.7 September 2026 Demo Dependencies =====

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:20-risks-and-open-decisions:start | Return to Risks and Open Decisions ]]

The team should identify dependencies that may affect the September 2026 demonstration. Phase 0 provides the first executable baseline, but the demonstration may require additional capabilities, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], documentation, or stakeholder preparation.

Demo dependencies may include:

  - Final tool selections.
  - Working repository baseline.
  - Successful prerequisite validation.
  - DDS/IDL type-generation workflow.
  - Container build and run workflow.
  - Required Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]].
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status reporting.
  - Control Plane command handling.
  - Any required [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]] placeholder or message flow.
  - Logs and observability.
  - Acceptance Evidence package.
  - Demo script or operator guide.
  - Reviewer or stakeholder briefing material.
  - Hardware, operating system, or network assumptions for the demonstration environment.

The team should track demo dependencies actively. A dependency should not remain implicit if failure to resolve it could block the demonstration.

----

<WRAP centeralign>

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

</WRAP>