4.2 Top-Level Repository Structure [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.2 Top-Level Repository Structure ======

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

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

The top-level [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure should expose the main categories of Phase 0 implementation work. Each top-level directory should have a defined purpose and support one or more of the following: source control, generation, build execution, runtime execution, testing, documentation, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection.

A representative Phase 0 Repository structure is:

<code>
financial-systems-archetype-phase0/
    docs/
    idl/
    src/
    generated/
    config/
    scripts/
    containers/
    tests/
    logs/
</code>

The README file should explain the Repository's purpose, identify the current Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]], and point readers to the handbook, prerequisite checks, setup steps, build steps, run steps, stop steps, and [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]].

----

<WRAP centeralign>

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

</WRAP>