====== 7.8 Repository Structure as Phase 0 Implementation Organization ====== [[fxdemo:04-part:07-phase-0-technology-selection-and-implementation-context:start | Go To Phase 0 Technology Selection and Implementation Context ]] Phase 0 uses an approved repository structure to organize implementation artifacts. The repository structure identifies locations for [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] files, generated code, hand-authored source code, configuration files, Quality of Service (QoS) profiles, scripts, documentation, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] tables, and supporting artifacts. It also distinguishes governed artifacts from generated artifacts, local build artifacts, temporary artifacts, and non-baseline exploratory material. The repository structure supports implementation, organization, and traceability. It does not define the architecture. It organizes the artifacts that realize the architecture. The repository structure must support the No-Code-Before-Handbook constraint, generated-file discipline, traceability review, and later Part 5 deployment and evidence planning. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.