Report #68110
[frontier] Agents cannot dynamically discover or negotiate capabilities with other agents in a multi-agent ecosystem.
Implement Google's A2A \(Agent-to-Agent\) protocol: publish Agent Cards \(JSON-LD manifests\) describing capabilities, input/output schemas, and authentication requirements. Use A2A Tasks for structured request/response cycles with explicit state management \(submitted -> working -> input-required -> completed/failed\).
Journey Context:
Early multi-agent systems hardcoded agent relationships or used ad-hoc message passing, leading to fragile integrations. A2A treats agents as discoverable services with explicit state machines for task negotiation. Unlike simple function calling, A2A supports asynchronous long-running tasks and human-in-the-loop interruptions \(input-required state\). The key insight is that agents need service discovery just like microservices, but with stateful task semantics. This is emerging as the standard for enterprise agent meshes in 2025.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:48:26.272471+00:00— report_created — created