FUURAA AI Evidence Atlas · Evidence dossier 02
Open protocols, capability discovery and multi-agent research are advancing, but credible evidence also shows that adding agents can increase communication overhead, duplicated work and coordination failure. Benefits appear task-dependent and require explicit roles, shared state, verification and recovery.
The economic promise of agents depends on systems that can discover one another, divide work, exchange context and verify commitments across organisations. Coordination quality—not agent count—will determine whether a multi-agent system compounds capability or compounds error.
This dossier covers agent-to-agent protocols, tool interoperability, task allocation, shared state, commitment tracking, verification and failure recovery. It does not treat protocol support as proof that an agent or tool is trustworthy.
Credible evidence supports more than one interpretation, or outcomes vary materially by context.
This evidence dossier synthesises public records. It is not investment, medical, legal or safety certification advice, and it does not claim that FUURAA has completed the systems discussed.Claim-to-evidence map
Primary evidence records
CooperBench found that paired coding agents performed worse on average than a single agent completing both tasks, exposing a coordination penalty.
FUURAA interpretationMulti-agent architecture should be justified by measured division-of-labour gains, not by agent count.
The benchmark identifies vague communication, broken commitments and incorrect expectations about teammates as recurring failure modes.
FUURAA interpretationAgent teams need explicit shared state for promises, dependencies, conflicts and verification.
Google transferred the A2A specification and tooling to a Linux Foundation project supported by multiple enterprise technology companies.
FUURAA interpretationNeutral stewardship can reduce vendor lock-in and make cross-company agent collaboration more credible.
A2A is designed to help agents discover capabilities and exchange tasks without sharing their internal memory or implementation.
FUURAA interpretationFuture agent marketplaces will need trustworthy capability descriptions, versioning and verification.
MCP defines a common protocol for connecting language-model applications with external data sources, resources and tools.
FUURAA interpretationStandard connectors can lower integration costs, but each connection still needs explicit trust and permission design.
A common connection format improves compatibility but cannot determine whether a server, tool output or requested action is safe.
FUURAA interpretationRegistries, provenance, sandboxing and least-privilege controls must surround protocol adoption.
Testable questions
Does the multi-agent design beat a single-agent baseline after communication, verification and recovery costs are included?
Can every output be traced to task ownership, evidence and the agent that accepted responsibility?
How does the system behave when one agent is unavailable, malicious or confidently wrong?
Decision relevance
Research: publish simple baselines and coordination overhead, not only best-case aggregate performance.
Engineering: make roles, state transitions, commitments, evidence and recovery paths observable.
Procurement: protocol compatibility should not replace tool assurance, permission review or supplier accountability.
Related FUURAA analysis
Stanford research reported that pairing coding agents can reduce performance, exposing coordination—not language or coding alone—as a critical bottleneck.
↗
NIST’s 2026 AI Agent Standards Initiative puts interoperability, open protocols, security and agent identity at the centre of trusted adoption.
↗
Singapore’s updated governance framework combines risk boundaries, human accountability, technical controls and transparency with practical deployment cases.
↗
Stanford’s 2026 AI Index describes rapid adoption, investment and capability gains, but also a jagged technical frontier and limited deployment of agents in business functions.
↗Revision record
Version 1.0 establishes the initial public synthesis. Future revisions will record changes in evidence position, sources, scope and unresolved questions. Earlier records are not silently erased.
Corrections, missing primary evidence and material counter-evidence can be submitted through the FUURAA contact route. Inclusion is subject to source verification and editorial review.Continue through the Evidence Atlas