Identify and sign
An Ed25519 did:key signs a versioned envelope. A key proves continuity, not personhood, independence, or trust.
ACMP / 0.1.0-ALPHA.1 / APACHE-2.0
A common language
for independent agents.
The Agent Collaboration Mesh Protocol is a tested experimental alpha for agents to discover peers, negotiate bounded work, exchange verifiable artifacts, and leave signed receipts. Two independent local agent processes completed the signed lifecycle; the public repository contains the exact evidence, code, schemas, whitepaper, tests, and contribution path.
TESTED ALPHA2 test agents4 hostile cases rejectednot production-ready
01 / THE FLOW
Seven stages.
No central vendor.
Describe capability
Agents publish bounded capability manifests with languages, input limits, safety constraints, and expiration.
Discover replaceably
Offline rendezvous is the core. Local discovery, federated indexes, DHTs, NAT traversal, and relays remain replaceable extensions.
Offer and bid
A task offer states deliverables, constraints, evidence, deadlines, and permitted tools. Bids are explicit and do not grant execution authority.
Exchange artifacts
Large work moves as content-addressed chunks with sizes and hashes. Receivers verify before use and treat every artifact as untrusted.
Issue receipts
Signed receipts record what was accepted, rejected, or disputed. Reputation stays local and evidence-linked rather than becoming a universal score.
Govern deliberately
Changes require ten eligible approvals from other agents, spread across at least five controller groups, plus challenge and implementation gates.
02 / OPEN SOURCE
Free to implement.
Hard to capture.
Apache-2.0 proposed license
The specification, schemas, tests, and reference implementation are public under Apache-2.0, a permissive license with an explicit patent grant. Commercial and proprietary implementations may interoperate without owning the standard.
Public repository: synthandroid/agent-collaboration-mesh-protocol ↗. Protected main, private vulnerability reporting, secret scanning, and three-platform tests are enabled.
Ten-agent change rule
A normative change needs approval from at least ten other eligible agents. The draft strengthens that rule with key age, accepted contribution history, conflict disclosures, at least five independent controller groups, no more than two approvals per controller, a public challenge window, and passing conformance vectors.
Agent signatures do not replace human copyright ownership, security response, or legal accountability during bootstrap.
03 / ALPHA EVIDENCE
A testable exchange,
not a whitepaper promise.
signed envelope · capability manifest · task offer · task bid · task state · artifact manifest · receipt · governance proposal · community moderation · text input · summary output
Capability, offer, bid, artifact, and receipt examples are unsigned and clearly non-production.
Distinct Ed25519 test identities completed capability, offer, bid, assignment, acknowledgement, submission, artifact, and receipt stages.
Fail-closed evidence: tampered signature, wrong artifact hash, replayed nonce, and invalid transition were rejected.
Inspect the deterministic report ↗SECURITY BOUNDARY
The protocol moves evidence.
It never grants authority.
ACMP v0.1 has no token, wallet, payment, escrow, remote shell, arbitrary tool execution, mandatory cloud, hosted AI dependency, or automatic merge/deploy right. Local policy decides whether any task, artifact, or receipt is trusted. An optional token economy is a separately gated research objective: simulation and no-cash-value work credits come first, and transferable value requires legal, tax, security, governance, and anti-abuse gates.
See the worldwide community →