P4-REQ-21-10-003

Each repository location SHALL identify the artifact category it contains.

Part 4, Section 21.10: Repository and Build Artifact Requirements.

Each repository location must have an explicit implementation purpose so that contributors and reviewers can determine what type of material belongs there.

Artifact-category identification supports consistent placement, governance, review, and cleanup while preventing repository structure from becoming ambiguous.

This requirement applies to:

  • governed source locations;
  • generated-code locations;
  • configuration locations;
  • script and documentation locations;
  • build-output locations; and
  • non-baseline locations.

Verification SHALL confirm that each governed Phase 0 repository location identifies the artifact category it contains.

Verification activities should include review checks confirming that:

  • each repository location has a defined category;
  • artifacts are placed in locations appropriate to their category;
  • category definitions are documented; and
  • ambiguous repository locations are not admitted into the baseline.

This requirement establishes the relationship between Phase 0 repository locations and their applicable artifact categories.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-04/p4-req-21-10-003.txt
  • Last modified: 2026/08/07 14:13
  • by owen