P4-REQ-21-10-010

Return to Requirements

Repository layout SHALL NOT redefine the architecture.

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

Repository layout is an implementation organization mechanism. Directory structure, file placement, generated-code locations, and build-output locations do not define logical Nodes, Communication Endpoints, information structures, Runtime Planes, or interaction patterns.

This constraint preserves separation between architectural definition and repository organization.

This requirement applies to:

• repository directories;
• source and generated-code locations;
• configuration and script locations;
• documentation locations;
• build-output locations; and
• repository naming conventions.

Verification SHALL confirm that repository layout does not redefine architectural elements.

Verification activities should include review checks confirming that:

• repository directories are treated as implementation organization;
• logical architectural definitions remain governed by Parts 1, 2, and 3;
• directory boundaries do not implicitly redefine Node or Runtime Plane boundaries;
• file placement does not redefine Communication Endpoints or information structures; and
• repository changes remain implementation-governance concerns.

This requirement preserves the separation between the FX Demo architecture and the Phase 0 repository organization selected to support implementation work.

Related requirement identifiers:

• P4-REQ-21-10-001
• P4-REQ-21-10-008
• P4-REQ-21-10-009
• P4-REQ-21-2-004

Related source section:

• 21.10 Repository and Build Artifact Requirements

Draft