====== 3.4 Implementation Technology Baseline ====== [[fxdemo:05-part:start | Go To Top ]] [[fxdemo:05-part:03-phase-0-baseline:start | Return to Phase 0 Baseline ]] The implementation technology [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] identifies the technologies and tools that the team uses to create the Phase 0 executable Baseline. This includes the selected [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] tooling, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] generation approach, programming language choices, scripting environment, container tooling, [[dido:99_annexes:annex-b-terms-and-definitions:g:git|Git]] [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]], and development environment. The team should document each required technology with sufficient precision for another developer to reproduce the environment. [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]] expectations, installation assumptions, required command-line tools, environment variables, and [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] steps should be documented in the handbook or the supporting [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] documentation. The technology Baseline should distinguish required tools from optional tools. Required tools support Repository creation, [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Type]] generation, build execution, container operation, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] execution, logging, testing, and acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. Optional tools may improve developer productivity, but the Baseline should not depend on them unless the team later promotes them to required status. The technology Baseline should also distinguish runtime implementation choices from developer-support tooling. For example, [[dido:99_annexes:annex-b-terms-and-definitions:p:python|Python]] may support Repository setup, Validation, generation orchestration, and inspection utilities without becoming the normative runtime language for production Nodes. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.