A meta-repository gives agents a machine-readable map of a multi-repository system before they enter individual codebases. It records dependencies, service communication, cross-service conventions, and the decisions that explain current boundaries. section 10.1.1
Use it to reduce context fragmentation without forcing an immediate topology change:
- Document which services depend on one another and which protocols connect them. section 10.1.1
- Capture conventions such as message queues instead of direct HTTP, alongside the ADRs that justify them. section 10.1.1
- Let agents read the meta-repository first, then migrate only tightly coupled services when the evidence supports consolidation. section 10.1.1
Incremental adoption
A fourteen-repository system can begin with a meta-repository, then move its payment, invoice, and shared-auth services into a monorepo over time while leaving the remaining repositories connected through the shared map. section 10.1.1
Figure 10.2 Meta-Repository Pattern.

Use the figure to inspect how the meta-repository connects repositories, dependencies, conventions, and decision records. section 10.1.1

