What problem does it solve?
Prevents agents from randomly exploring or modifying unrelated parts of a monorepo by providing a clear routing and boundary discipline so automated agents act within intended areas and respect architectural layers.
Core Features & Use Cases
- Monorepo Map: A routing table in the repository AGENTS.md that maps areas to paths and their AGENTS.md files so agents know where to look.
- Area Boundaries: Per-area Imports / Exports / Boundaries sections that document allowed dependencies and explicit "Never Touches" to avoid architectural shortcuts.
- Cross-Area Change Protocol: A stepwise workflow that identifies affected areas, starts changes from the innermost layer outward, respects import direction, and updates AGENTS.md as public surfaces change.
- Use Case: Safely add a new domain entity and propagate required repository adapters, API models, and frontend changes while preventing connectors from importing API internals.
Quick Start
Focus on the src/connectors area, read its AGENTS.md and Monorepo Map, and only implement changes that respect the declared imports, exports, and boundary rules.