Two agents from different teams in the same organization need to coordinate: Agent A (owned by the Platform team) generates infrastructure change plans, and Agent B (owned by the Security team) must approve those plans before they are executed. Neither team controls the other's agent. Which coordination design MOST effectively enables this cross-team agent coordination?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Two teams' agents communicating without a shared contract is like two international delegations negotiating without a common language or rules of procedure. The shared coordination contract (schema + neutral surface) is the treaty: both agents know what a valid proposal looks like and what a valid approval looks like, GitHub provides the neutral ground, and neither team owns the other's agent. The schema lives in a shared repo as a neutral party to prevent either team from unilaterally changing the protocol.
Full explanation below image
Full Explanation
Cross-team agent coordination requires loose coupling (neither agent directly calls the other's internals) and a shared, versioned coordination protocol that neither team unilaterally controls.
Option A (Agent A directly calls Agent B's API) creates tight coupling between teams. Platform team is now dependent on Security team's API stability, versioning, and availability. Security team must design and maintain an API for external agent callers. If Security team changes their API, Platform team's agent breaks. This is the service coupling anti-pattern applied to agent systems.
Option B is correct for several reasons: (1) Loose coupling — neither agent calls the other directly. Agent A writes to a shared GitHub surface; Agent B reads from it and writes back. They communicate through the shared surface, not through direct API calls. (2) Versioned shared schema — the coordination contract (plan proposal schema and approval response schema) is explicitly defined, versioned, and owned by a neutral party (e.g., a shared platform governance repo). Either team can evolve their agent independently as long as they conform to the schema. (3) GitHub as neutral coordination surface — GitHub Issues and PRs provide visibility, auditability, access control, and notification infrastructure that neither team owns exclusively. (4) Structured communication — requiring structured responses (approve/reject with mandatory reason field) prevents ambiguous coordination.
Option C (routing without shared schema) is loose coupling but with uncontrolled data format. Without a schema, Agent B must guess or discover the format of Agent A's outputs. Schema drift causes silent failures when Agent A changes its output format.
Option D (merge into one shared agent) is an organizational anti-pattern. Platform and Security teams have different priorities, release cadences, and governance requirements. Merging their agents creates ownership ambiguity, governance conflicts, and a single shared agent that neither team can fully control.