4.1 Repository Design Principles [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.
====== 4.1 Repository Design Principles ======

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

[[fxdemo:05-part:04-repository-layout:start | Return to Repository Layout ]]

The Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] should make the implementation easy to understand, reproduce, review, and extend. The team should organise the Repository around clear [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] types and responsibilities rather than around individual developer preferences.

The Repository layout should support the following principles:

  - Separate handwritten source files from generated Artifacts.
  - Separate architecture-facing documentation from developer-facing documentation.
  - Separate source definitions from build outputs and runtime outputs.
  - Separate reusable implementation code from demonstration-specific [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]].
  - Keep scripts, Configuration files, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] definitions, tests, and documentation in predictable locations.
  - Ensure that every top-level directory has a clear purpose.
  - Avoid hidden [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]] on local machine paths, shell profiles, IDE settings, or personal tooling.

The Repository should help the team answer basic questions quickly: where does the source code live, where do IDL definitions live, where does the generated code go, where do scripts live, where does the Configuration live, where do logs go, and which Artifacts should [[dido:99_annexes:annex-b-terms-and-definitions:g:git|Git]] track?

----

<WRAP centeralign>

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

</WRAP>