A municipal monorepo spans parks, transit, and water-utility code, each with its own conventions and domain knowledge. The platform team wants a single coding-agent deployment in Antigravity to handle work across all three departments efficiently. What structure best fits this?

Antigravity supports creating subagents that specialize in a scoped part of a codebase, coordinated by a top-level agent that decides which subagent handles which request. For a monorepo spanning distinct departments with different conventions, this hierarchy lets each subagent build deep familiarity with one domain rather than one generalized agent trying to hold parks, transit, and water conventions simultaneously.

A single flat agent relying on instructions alone to keep departments separate is the earlier, less reliable pattern: instructions can drift or get overridden by a large enough context, and nothing structurally prevents cross-department mistakes. Three fully independent agents with no coordinator solves the specialization problem but loses the ability to route work correctly or share cross-cutting concerns like shared libraries. A bigger context window is a capacity fix, not a structural one — it lets the agent see more without making it any better at keeping departmental conventions from bleeding into each other.

Scope note: subagent boundaries work best when they mirror real ownership boundaries in the codebase. Operational check: verify each subagent's configured scope actually matches the department's directory structure before rollout.