Operating a Meta-Repo How to structure agent docs in tiers, prevent context drift, run parallel agents in worktrees, and build one yourself.

Having a meta-repo isn't the same as operating one.

Teams doing it well keep CLAUDE.md under 13KB, generate maps instead of writing them by hand, and gate rules like production code.

Agents won't fix a sloppy workspace. They'll just scale it faster.

The Meta-Repo Pattern Repo boundaries blind AI coding agents. Teams are building meta-repos, lightweight system maps with no application code.

AI coding agents start every session with no memory of your system.

Teams are building "meta-repos" — repos with no app code, just maps to orient agents across multi-repo codebases.

AI didn't invent the need for good docs. It made the penalty for missing them immediate.