20.7 Repository Layout Does Not Redefine Architecture [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 20.7 Repository Layout Does Not Redefine Architecture ======

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

[[fxdemo:04-part:20-phase-0-implementation-rules-and-constraints:start | Return to Phase 0 Implementation Rules and Constraints ]]

[[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure organises implementation artefacts. It does not define the architecture.

Directories, file locations, generated-code locations, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] locations, script locations, documentation locations, and build-output locations support implementation discipline and review. They do not redefine FX logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], interaction patterns, governance relationships, or [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

Repository organisation must support Traceability, generation discipline, review, and later Part 5 [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] planning.

<WRAP centeralign>

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

</WRAP>