Modularity organizes a codebase into self-contained components with independent compilation, caching, and build boundaries. It is a throughput mechanism, not merely a clean-code preference: agents spend less time waiting on shared build I/O and more time reasoning and coding. section 10.3.1
Use modular boundaries to reduce contention and make change impact visible:
- Give each module its own compilation unit and cache key. section 10.3.1
- Compile independent modules in parallel instead of making agents share build-system I/O. section 10.3.1
- Pair module architecture with target-level dependency tracking so agents can navigate changes and estimate blast radius. section 10.9
Parallel agent work
When Agent A modifies module X, only X recompiles; Agent B working on module Y remains unaffected. This turns a shared build bottleneck into independent, parallel work. section 10.3.1















