harness-engineering-context

Organize repository documentation by defining root entrypoints like README.md, AGENTS.md, and ARCHITECTURE.md, then route everything through a canonical docs/ folder. This creates a single source of truth and enforces consistent documentation boundaries across the project.

Automate validation for repository structure and cross-links by applying executable checks that enforce source-of-truth boundaries. This ensures root entrypoints and the canonical docs layer remain accurate and interconnected without manual review.

Manage versioned execution plans by placing them under docs/exec-plans with defined lifecycle states. This tracks migrations and structural changes systematically while keeping the canonical docs layer up to date.

You need to restructure repository context systems when your project lacks clear root entrypoints or suffers from scattered documentation. Establishing a canonical docs layer resolves inconsistencies and enforces automated structure validation.

Yes, you can validate docs boundaries for projects with existing AGENTS.md files. The restructuring defines clear roles for AGENTS.md, README.md, and ARCHITECTURE.md, applying automated cross-link checks to ensure they point correctly to the canonical docs folder.