A county government is rolling out Antigravity coding agents across every department and wants a single, centrally managed policy layer controlling what all of them are permitted to do. Where should this policy be configured?
Select an answer to reveal the explanation.
Short Explanation
Think of it like setting one countywide procurement policy instead of letting every department write its own purchasing rules and hoping they all land in the same place. Agents CLI is that single policy layer — it governs the whole fleet of Antigravity deployments centrally, so a rule set once instead of trusting a dozen departments to independently arrive at the same standard.
Full Explanation
Agents CLI is designed to build, scale, govern, and optimize a fleet of deployed agents, which includes acting as the centralized policy layer across multiple Antigravity deployments rather than requiring each department to manage its own policy independently.
Writing each department's policy independently in its own rules file produces inconsistent standards across the county, since nothing keeps parks, transit, and water from drifting into different interpretations of the same intended rule. Treating the first-deployed agent's system instructions as the reference configuration conflates one department's specific settings with a countywide policy, and any change made there won't propagate anywhere else. A shared document that departments manually replicate depends entirely on every team correctly and consistently implementing it, with no mechanism to enforce or verify that they actually did.
Scope note: centralizing policy through Agents CLI still allows department-specific exceptions where genuinely warranted, but those exceptions should be explicit rather than the default state. Operational check: after publishing a centralized policy update, spot-check two different departments' deployed agents to confirm both actually reflect the new rule.