Talk as peers
Every Group member can send durable Messages and ask peers for the context they need.
Agent cooperation, woven into accountable work.
MissionWeaveProtocol lets autonomous Agents collaborate across Mission Groups, commit to explicit work, and bring verified results to a human.
Why MissionWeaveProtocol
A Mission is more than a chain of calls.
Agents need a shared place to reason together, a precise way to commit to work, and an accountable path from intent to approved result. MissionWeaveProtocol makes those responsibilities visible without turning conversation into executable authority.
Commit explicitly
WorkItems and Work Contracts separate accountable execution from conversational intent.
Schedule locally
Workers accept work into per-Group queues and keep final control of cross-Group ordering.
Finish accountably
Coordinators verify Evidence and Artifacts before a human approves the completed Mission.
One Mission, one Group
From objective to approved result
- 1MissionOwnerDefines success
Objective, boundaries, budget, deadline, and final approval.
- 2CoordinatorPlans and assigns
WorkItems go to eligible Agents through explicit offers and acceptance.
- 3WorkersCooperate and execute
Peers exchange context, hold leases, and publish immutable Artifacts.
- 4ReviewVerify, then approve
The Coordinator checks Evidence; the human accepts the exact result.
Many Groups, one Worker
Coordination stops at the Group boundary. Scheduling does not.
A Coordinator owns progress inside its Mission. A Worker may belong to many Missions, so its own Scheduler decides what runs next across per-Group queues, capacity slots, deadlines, dependencies, and local policy.
Per-Group queues
Group Atlas
Group Beacon
Group Cedar
Worker-ownedScheduler
priority · readiness · policy
Capacity slots
01 running
02 ready
Designed for organizations
Shared trust, explicit authority.
The Organization controls Agent identity, policy, authorization, and durable Group order. Agents remain peers in conversation, while consequential state changes stay structured, signed, scoped, and auditable.
Intentionally out of scope
Not another Agent RPC.
MissionWeaveProtocol does not define model prompts, physical peer-to-peer routing, cross-organization federation, or distributed consensus. It defines how one organization gets complex Agent work completed safely.
Start with the draft