Should coordination protocols wrap existing systems or replace them?
Explores whether new agent coordination standards should integrate with existing protocols through bridging, or establish themselves as replacements. This shapes which standards survive and how quickly ecosystems can adopt them.
The agent-protocol landscape is already crowded: MCP for model-to-tool access, A2A for agent-to-agent task collaboration, A2UI for interface delegation, DIDComm for secure DID-based messaging, ANP for discovery and negotiation, UCP for agentic commerce. Each covers a real slice of the space. The Foundation Protocol's design choice is to not add a competing slice but to provide the shared substrate these ecosystems keep re-creating in different forms — a graph-first control plane that lets them compose across boundaries while preserving identity, authority, and accountability. By separating a small protocol core from profiles, extensions, and bridges, it enables incremental adoption: you keep your existing protocols and bridge them in, rather than migrating.
This is a strategic pattern about how infrastructure standards win. Replacement demands that an entire ecosystem abandon working investments simultaneously, which rarely happens; bridging lets value accrue at the margin as each protocol connects. The counterpoint is that a wrapping layer can become a lowest-common-denominator abstraction that loses what made each underlying protocol sharp, and a bridge adds a translation surface that can itself fail or be attacked. But for a fragmenting agent ecosystem, composability beats purity. This matters because it predicts which coordination standards survive: those that reduce integration and governance overhead without forcing a rewrite.
Inquiring lines that read this note 88
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
Should multi-agent systems use structured protocols or natural language communication?- What architectural changes would enable better common-ground tracking?
- How do standardized artifacts improve coordination between multiple tools?
- Can deterministic function calls prevent agent failures better than protocol-mediated tool access?
- How do standardized artifacts prevent autonomous agent failure modes?
- What role does standardization play in multi-agent system ecosystems?
- How do standardized artifacts improve coordination between writing agents?
- How do standardized artifacts reduce inter-agent communication failures?
- Can architectural structure replace behavioral training for agent consensus?
- Can protocol bridges introduce new failure modes or security vulnerabilities?
- Does wrapping existing protocols create lowest-common-denominator abstractions that lose sharpness?
- What makes capability vectors a better coordination substrate than topic-based routing?
- How does protocol mediation affect determinism in agentic function calls?
- What makes protocols better than free-form prompting for tool coordination?
- Should new agent protocols replace existing ones or layer on top of them?
- What would unified agent-to-agent and agent-to-tool protocols actually look like?
- Can versioned capability vectors solve the discovery gap in existing protocols?
- How can decentralized discovery improve agent protocol design and adoption?
- Can structured protocols outperform pure emergence in autonomous multi-agent coordination?
- Can agents become genuine social actors even with perfect coordination infrastructure?
- Can public wikis enable agent coordination without requiring infrastructure breaches?
- How does storage-mediated coordination differ from direct agent messaging?
- Why do stateless protocols push coordination complexity into application code?
- Does the versatility-efficiency-portability tradeoff favor stateless or session-stateful protocols?
- Can researchers from different labs actually run each other's protocols?
- Why does structured protocol coordination outperform free-form agent-to-agent communication?
- What makes some agent infrastructure useful even without widespread adoption?
- How can formal communication protocols like FIPA-ACL improve agent transparency?
- Can verification of agent actions after execution substitute for formal communication protocols?
- Can structured artifacts replace natural language for multi-agent coordination?
- Are merchants actually adopting these protocols as an integrated stack?
- How do AI protocols win adoption through market contention versus specification?
- Can informal codified behavior compete effectively with formally standardized agent communication?
- What protocols enable agents to coordinate and complete transactions with each other?
- How do formal standards differ from market-driven protocol adoption in governance?
- What makes protocols more market-shaping than APIs enforced by dominant actors?
- Does protocol adoption require formal disclosure mechanisms to remain governable?
- Can a single protocol work across multiple AI agents and payment providers?
- Should merchants adopt new protocols or reuse existing standards instead?
- How do platform-specific standards differ from interoperable standards in agentic commerce?
- What incentives push platforms toward closed systems versus open standards?
- Why do rigid orchestration frameworks fail where generative environment specifications succeed?
- How should proportionality constraints be implemented in agentic systems?
- What five ecosystem conditions must coordination governance and evidence actually satisfy?
- What makes composable abstractions emerge under performance pressure in agent systems?
- How will the agent economy reshape compute infrastructure design?
- How do learned teamwork strategies compare to hand-coded coordination protocols?
- How do organizations govern metric definitions across multiple teams and systems?
- Can coordination theory apply to modern multi-agent artificial systems?
- How do centralized coordination systems trade efficiency against concentration risk?
- Why might agents concentrate into a few dominant ecosystems without portability?
- What frameworks exist for designing multi-agent orchestration systems?
- How do collaborative agent swarms coordinate tasks across specialized agents?
- How can RAG systems integrate with existing enterprise authentication and security protocols?
- Why does agent-to-agent interaction expose identity verification vulnerabilities?
- Which of the six proxy forms works best for different agent tasks?
- How do agent identity and attribution standards enable inter-organizational coordination?
- Why are new protocols being built instead of extending OAuth and OIDC?
- Should payments infrastructure adopt agent-specific protocols or reuse existing identity standards?
- How do siloed agents differ from truly interoperable service agents?
- Can NIST identity standards address the technical barriers to AI agent interoperability?
- What coordination failures emerge when multiple agents work together?
- Why do LLM agents struggle with protocol discipline in distributed settings?
- What makes a service visible to autonomous agent systems?
- How does coordination governance shift the hard problem from capability itself?
- Where does agent coordination governance become the binding constraint on capability?
- How does agent governance relate to traditional multiagent system design?
- How do institutional models and protocols scaffold accountability in agentic AI systems?
- Can ecosystem-level standards reduce trap detection burden?
- Can single-agent defenses prevent cascading failures in multi-agent systems?
- Which ecosystem conditions matter most for agent deployment success?
- What ecosystem conditions must exist for agents to function as economic participants?
- What five conditions must exist for agent ecosystems to generate value?
- Does encoding governance into runtime loops scale as deployment environments become more complex?
- Can a package repository act as persistent memory for agent coordination?
- How do ordinary web services enable persistence for distributed agent activity?
Related concepts in this collection 2
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Why do protocol-based tool integrations fail in production workflows?
Explores whether standardized tool protocols like MCP introduce non-determinism that undermines agent reliability, and what causes ambiguous tool selection in production systems.
tempers the wrap-and-bridge optimism by showing protocol mediation can introduce non-determinism the core layer must constrain
-
Can semantic capability vectors replace manual agent routing?
Explores whether embedding agent capabilities in high-dimensional space and matching them semantically can eliminate brittle, manually-maintained topic-based routing in multi-agent systems.
an alternative coordination substrate that, by contrast, replaces rather than wraps the routing layer
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Foundation Protocol: A Coordination Layer for Agentic Society
- Drop the Hierarchy and Roles: How Self-Organizing LLM Agents Outperform Designed Structures
- Toward an Organizational Science of Multi-Agent LLM Systems: Decoupling Who, How, and Which Algorithm
- A Technical Taxonomy of LLM Agent Communication Protocols
- Infrastructure for AI Agents
- AgentsNet: Coordination and Collaborative Reasoning in Multi-Agent LLMs
- A Comparative Study of MCP and A2A for Inter-Agent Coordination in LLM-Based Systems
- Worse Together: How Performance Breaks Down in Multi-User Multi-Agent Teams
Original note title
agent coordination protocols should wrap and bridge existing protocols rather than replace them