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.
Most current multi-agent orchestration relies on manually-curated integrations and topic-based routing: agents subscribe to message channels, capabilities are wired by hand, and the system grows brittle as agent heterogeneity increases. The operational question — who can do what, at what cost, under which policy constraints? — remains unanswered in static configurations.
Federation of Agents (FoA, 2509.20175) proposes the structural fix: agents publish Versioned Capability Vectors (VCVs) — machine-readable, versioned profiles that capture functional capabilities, performance characteristics, operational constraints, and security labels in a structured format. The profiles are embedded in a high-dimensional space where capabilities become searchable artifacts. This converts capability discovery from manual wiring into semantic retrieval.
Three architectural choices make this scale. (1) Sharded HNSW indices enable sub-linear matching, preserving distinctions among related skills even at large agent counts. (2) Semantic routing at dispatch time couples capability similarity with policy checks and resource budgets (latency, bandwidth, energy) — agents are not just functionally matched but operationally feasible for the task at hand. (3) Dynamic task decomposition elicits candidate breakdowns from compatible agents and merges them via consensus into a DAG of subtasks — different from static role-based decomposition because the agents themselves contribute to the decomposition structure.
The deeper claim is about how multi-agent systems should expose themselves to each other. Static directories require human maintenance and grow stale. Capability vectors are machine-readable contracts that can be updated as capabilities evolve (hence "versioned") and queried semantically rather than by exact name. This aligns with emerging interoperability efforts like Model Context Protocol — capability schemas become the substrate of cross-system agent coordination.
For deployment, FoA targets edge IoT contexts where MQTT publish-subscribe provides reliable delivery under constrained networks — but the architectural pattern generalizes. Any agent ecosystem with heterogeneous capabilities and operational budgets benefits from capability-as-embedding over capability-as-keyword.
The structural implication: as agent counts grow, capability discovery becomes the rate-limiting step in coordination, not message-passing volume. Topic-based routing optimizes for delivery; semantic routing over VCVs optimizes for the prior question — which agent should receive this message at all.
Paper: Federation of Agents
Related concepts in this collection
-
What decisions must multi-agent routing systems optimize simultaneously?
Standard LLM routing only picks which model to use. But multi-agent systems involve four interdependent choices: topology, agent count, role assignment, and per-agent model selection. Does optimizing all four together actually improve performance?
MasRouter handles routing decisions per query; FoA's VCVs make the routing primitives themselves first-class artifacts
-
Where do traditional function calling systems actually break down?
Function calling seems simple but fails in ways that aren't obvious. This explores three independent failure points—retrieval, context bloat, and output rigidity—that together explain why even the best models struggle.
Floworks names retrieval as a bottleneck; FoA addresses it via semantic embeddings over capabilities rather than over individual function schemas
-
Can models decide better than retrievers which tools to use?
Traditional retrieval picks tools upfront based on initial queries, but do models themselves make better decisions about tool needs as they reason? This explores whether authority over tool selection should move from external systems to the LLM.
proactive retrieval addresses tool discovery from the agent's side; FoA addresses it from the ecosystem side via published profiles
-
When does adding more agents actually help systems?
Multi-agent systems often fail in practice, but the reasons remain unclear. This research investigates whether coordination overhead, task properties, or system architecture determine when agents improve or degrade performance.
FoA's semantic routing addresses the topology-dependent error amplification by routing to capability-appropriate agents rather than broadcasting
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
Original note title
capability-driven agent coordination via versioned capability vectors replaces topic-based routing with semantic discovery at scale