MCP، A2A، ACP: لا التصويت، لا التناقض، لا إدارة

Every major agent interoperability protocol—MCP, A2A, ACP, ANP, and ERC-8004—lacks primitives for voting and dissent preservation, according to a systematic gap analysis by researchers applying a six-dimension governance taxonomy derived from organizational theory and multi-agent systems literature.

The Six Governance Dimensions That Protocols Can't Cover

The taxonomy covers membership, deliberation, voting, dissent preservation, human escalation, and audit/replay. Against these, MCP, A2A, ACP, ANP, and ERC-8004 all score Absent on voting and dissent preservation. Deliberation? At best Partial. No protocol encodes the full set of primitives required for governed agent communities. That's not a minor oversight—it's a systematic blind spot in the current interoperability stack.

Why Extensible Gaps Aren't the Real Problem

The paper distinguishes two kinds of gaps: extensible (fixable through protocol extension mechanisms) and structural (requiring a new architectural layer). Voting and dissent preservation fall into the structural category. You can't bolt on a quorum rule or a dissent log via a capability advertisement—those primitives demand protocol-native semantics for state, identity, and resolution. The analysis also flags time-sensitivity: protocol evolution velocity matters. If a spec moves fast but doesn't address governance, you're left with a moving target that still can't express a simple majority vote.

The Missing Architectural Layer Above Standards

Enterprises deploying heterogeneous agent fleets need collective decision-making under governance constraints—think audit trails, escalation chains, and minority reports. Current protocols handle identity, tool access, and message exchange. They do not handle community governance. The paper argues that agent community governance constitutes a missing architectural layer above current interoperability standards, not a missing feature within them. Anyone building autonomous agent systems at scale should treat this as a design constraint, not a future feature request.

Source: Governance Gaps in Agent Interoperability Protocols: What MCP, A2A, and ACP Cannot Express
Domain: arxiv.org