Multi-Repository Development and Coordinated Delivery
A business outcome may require coordinated changes to an API, client, shared schema, infrastructure, deployment configuration, and documentation stored in different repositories. An agent working from one checkout can miss a dependent contr
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Design a coordinated change across an API repository, web client, shared schema, and deployment repository. Show discovery, authorization, checkouts, four PRs, compatibility windows, integration verification, merge order, release, a failed third PR, and rollback. Identify every non-atomic boundary.
4. Tradeoffs and alternatives
Cloning all repositories improves discovery and increases environment startup, storage, context volume, and credential exposure. Human-selected repositories reduce cost and can omit the dependency the human did not know existed. A read-only discovery index with on-demand qualified checkout is a practical middle path.
A monorepo can simplify source atomicity and cannot make deployment atomic. Polyrepos preserve ownership and independent release at the cost of coordination. Repository consolidation is an organizational architecture decision, not an agent-context workaround.
5. Current Mission Control Implementation
At study commit
d902fae,
Mission Control itself is a TypeScript and pnpm monorepo. Its domain model
supports multiple registered repositories under a Workspace, repository-scoped
policy, Factory Configuration, WorkOrders, worktrees, GitHub identity, and
source/head-SHA-bound evidence.
The studied evidence does not establish a production-qualified multi-repository WorkOrder, repository dependency graph, workspace manifest, cross-repository candidate digest, coordinated PR state machine, compatibility gate, or release-and-rollback proof. Existing one-repository execution and multi-repository registration are substrate, not proof of coordinated delivery.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence