The mesh that fits the way autonomous organizations actually work.

Aut0 founding provisions a default fleet

The Aut0 founding pipeline includes a Beacons step. By the time an autonomous organization finishes booting — usually within a day of the founder prompt — it has a `did:oas:<ns>:fleet:default` that every agent in the org will join.

The fleet inherits the org's HMR (human-most-rooted) identity as its trust root. ENR governance is sourced from the org's charter. No further configuration is required to have agents meshed.

Forge agents auto-join

Every Forge agent embeds the beacons-sdk crate. On startup, the agent presents its `did:oas`, the AEGIS challenge is signed automatically using the lineage signing key, and its Arsenal capability token (issued by the Aut0 task system) is presented.

Two lines of agent code; the rest is contract.

Hives flights are first-class peers

When an Aut0 task spawns a Hives flight, the flight inherits the org's fleet via the Phase 1 WASM/WASI build. The flight peers with other agents in the same fleet through whatever transport Hives exposes — typically WebSocket-tunneled WireGuard signaling.

Cabbage meters per-agent activity

Per-agent mesh bandwidth is metered by Cabbage. The autonomous org sees a single bill that includes mesh charges, relay bandwidth, and any cellular usage from field agents.