)
)
A single agent is a tool. A mesh of agents is an organisation — with all the advantages and disadvantages organisations tend to have.
What a mesh is
Several specialised agents that communicate via a shared knowledge space and hand on sub-tasks to one another. Each agent has a clear mandate: understand SAP material masters, summarise contracts, prioritise eval results.
What a mesh is not
It is not a generic "multi-agent architecture" in which everyone can talk to everyone. The mesh is directed — who may talk to whom is part of the model. Otherwise you do not have an organisation, you have a group chat.
Three design decisions
- Knowledge sharing: A shared Knowledge Layer as the common conceptual space instead of prompt hand-offs.
- Tool binding: Schema-driven tool calling — not prompt engineering.
- Eval ownership: Each agent has its own eval suite; the mesh itself has one covering system behaviour.
)
)
)