project-structure-governancelisted

# Project Structure Governance Treat repository structure as an interface shared by people, tools, and agents. Govern file placement and naming; leave product, architecture, and content-quality decisions to their owning workflows. ## Resolve A Path Read [project-layout.json](references/project-layout.json) before creating or moving a file. Use its zones and artifact patterns as the global index. Read the target repository's `.project-structure.json` next. It selects one or more technology profiles and records project-specific zones or root files. Apply rules in this order: 1. Determine whether the file belongs to one registered application, a shared package, or the repository as a whole. 2. For application-owned code, resolve the registered `apps/<name>` path before applying that application's profiles. 3. Preserve paths required by the selected framework or build tool inside that ownership boundary. 4. Apply the repository manifest's explicit additions, then the global baseline and artifact index. 5. Stop and extend the index when no rule owns the file; do not invent an arbitrary directory. Read [project-structure-standard.md](references/project-structure-standard.md) when classifying an unfamiliar file, choosing a name, or changing the index. Read [document-bundle-standard.md](references/document-bundle-standard.md) before creating or reorganizing PRD, design, development, testing, release, or retrospective artifacts. Require the total-part directory structure and thr