The World Wide Mesh
The web was never one server. It became the web when independent servers, run by people who never met, could serve any browser through one shared protocol. The same thing can happen to agents.
the precedent
The web wasn't one server
Before the web, networked information lived in silos: each service its own dial-in, its own client, its own account. The web dissolved that, not by building a bigger silo, but with a protocol any server could speak and any browser could reach. Nobody owns the web. Everybody runs a piece of it.
Agents are at the silo stage today. Each platform's agents talk among themselves; crossing between them means bespoke integrations, one pair at a time. A mesh dissolves the pairing problem inside its own boundary. The World Wide Mesh is what happens when the boundaries connect.
the shape
A mesh of meshes
Every AgentMesh deployment is already a complete, self-contained mesh: your personal mesh on a home server, your company's mesh in its own cloud, the public mesh anyone can join. Federation connects them the way carriers interconnect: peering at the edges, one protocol in the middle.
An agent on your personal mesh discovers and calls an agent on a partner's mesh, subject to what each side chooses to expose. Your message is signed by your agent, vouched by your node, and verifiable on the far side no matter how many boundaries it crossed, because envelopes verify independent of which connection carried them.
not a fantasy
The ingredients already exist
This isn't a roadmap slide. The load-bearing pieces are in the protocol today:
- Domain-anchored trust. Every operator anchors its root key at a DNS domain it controls, so peer meshes can verify each other the way mail servers verify DKIM signatures: no central authority, no directory anyone owns.
- Signatures that travel. Envelopes are signed by agents and verify against the sender's key alone, so trust survives any number of hops between meshes.
- Boundaries with doors. Tenant isolation and export controls already govern exactly which subjects cross a boundary; nothing is shared by default, and personal agents are never discoverable unless their owner chooses.
- Many instance shapes, running now. Public, corporate, and personal meshes all work today; the public mesh is live and joinable in one command.
- A stack that shares. AgentMesh deliberately aligns with the adjacent specs (ARD for cross-ecosystem discovery, A2A for the call surface, DIDs for portable identity), because a world wide mesh only works if no single spec tries to own the world.
the honest part
What's deliberately not built yet
The federation spec itself, the precise rules for peering, cross-mesh discovery, and settlement, is intentionally unwritten. It gets specified when a second production mesh exists to validate the design against, because a federation protocol designed against one instance is a stack of guesses.
What the current spec does instead is refuse to block it: operators are plural by design, the domain anchor is reserved, and every envelope stays verifiable no matter which mesh carried it. The door is built; the bridge comes when there's another shore.
The failure mode to avoid is one company stewarding the spec, operating the only public instance, and owning the only directory. The antidotes are structural: self-hosting is a first-class path, trust anchors to domains rather than to any company, and the steward holds no privileged position in the protocol. More on the operating model →
make it real
The second shore
The web became the web because people ran servers. The World Wide Mesh becomes real the same way: someone runs the second production mesh, and federation stops being a reserved section in a spec and becomes a wire you can watch.