Operating manual
Tag: Multi-Agent Systems
A focused reading path for Multi-Agent Systems: related field notes, evidence trails, and operating questions from the archive.
- the-agent-stack-is-getting-protocols-before-it-gets-accountability.md
Accountability Starts After the Agent Handoff
MCP and A2A can move work between agents. Accountability starts when the receiving system can prove who authorized the work, what changed, what evidence survived, and who owns rollback.
open artifact → - protocols-are-saturating-the-operators-gap-is-governance-not-transport.md
Agent Protocols Need an Operator
MCP, A2A, and ACP are solving transport. But authority, review, memory, and handoff — the governance layer no spec hands you — is what makes a stack safe.
open artifact → - your-ai-shouldnt-be-one-assistant-it-should-be-a-room-full-of-desks.md
Your AI Needs a Room of Desks
One generalist assistant is the wrong unit of deployment. The right unit is a small, named fleet — each desk owns a queue, a memory, and a hand-off. Operator sits in the loop.
open artifact → - where-agent-to-agent-communication-actually-stands.md
Where Agent-to-Agent Communication Actually Stands
Agent-to-agent communication in 2026: what MCP and A2A solve, what frameworks do, what research says, and the gaps builders fill.
open artifact →