===== 20.1 Implementation Language Decisions =====

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

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

The team must decide which implementation language or languages Phase 0 uses for runtime [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], generated DDS bindings, scripts, tests, and developer-support utilities.

Open language decisions may include:

  - Which implementation language Phase 0 uses for runtime Nodes.
  - Whether all Nodes use the same language or different Nodes use different languages.
  - Whether Python remains limited to developer-support utilities or also supports runtime Nodes.
  - Which language or languages the DDS type-generation workflow targets.
  - Which build tools and package managers each language requires.
  - Which language-specific documentation conventions apply to public interfaces.

Language decisions affect repository layout, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] locations, build scripts, container images, developer setup, tests, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. The team should record selected languages in the applicable tool baseline checklist instance and, where needed, in an implementation decision record.

----

<WRAP centeralign>

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

</WRAP>