Document Hierarchy
Purpose
Avoid competing sources of truth.
When to Use
Use when adding, moving, or adapting docs.
Inputs
README, rules files, architecture docs, generated docs, indexes.
Steps
- Identify canonical docs.
- Identify derived or generated docs.
- Link instead of duplicating where possible.
- Update indexes when hierarchy changes.
Gates
The repository has one clear entry path and no accidental duplicate authority.
Evidence
Updated indexes, links, and hierarchy notes.
Anti-Patterns
Creating a second "main" guide with conflicting rules.
Related
documentation-sync, authority-chain