H.1.4 Repository Topology

Repository topology is a navigational and policy interface, not an organization chart copied into directories.

• Choose stable top-level concepts and naming rules from how people discover, own, build, test, and change the code.
• Separate directory placement, language module boundaries, build packages, deployment units, and team responsibility instead of assuming they coincide.
• Treat paths consumed by tools, automation, policies, documentation, or external users as interfaces with a relocation cost.
• Plan moves with redirects, aliases, ownership transfer, generated-file updates, and cleanup rather than preserving a poor layout forever.
• Evaluate topology through navigation, boundary clarity, dependency direction, change flow, and maintenance cost—not one universal tree shape.