3.5 Repository Baseline

Go To Top

Return to Phase 0 Baseline

The Repository Baseline defines the initial structure, naming discipline, generated Artifact locations, script locations, Configuration locations, source locations, test locations, and documentation locations for Phase 0.

The team uses the Repository Baseline to ensure that every developer works from the same structure. Developers should not create new top-level directories, naming patterns, generated file locations, or script conventions without an explicit reason and a corresponding update to the handbook or Repository documentation.

The Repository Baseline should separate handwritten source files from generated Artifacts. It should also separate architecture-facing documentation, developer-facing documentation, Configuration, IDL definitions, build scripts, test Artifacts, logs, and runtime outputs. This separation protects reviewability and prevents generated or temporary Artifacts from becoming confused with Governed source material.

The Repository Baseline also defines what Git should track and what Git should ignore. Source definitions, scripts, Configuration templates, documentation, tests, and reproducible generation inputs should normally enter Version Control. Local environment files, transient logs, build outputs, generated temporary files, and machine-specific settings should normally remain outside Version Control unless the team explicitly decides otherwise.