Get involved
Read it, implement it, break it
AMMP is an open specification. The most valuable contribution is a clause you couldn't satisfy, or an attack the trust model doesn't account for.
The repositories
amap-spec
The AMMP specification, JSON Schemas, conformance fixtures and the Internet-Draft, draft-rapp-ammp-00 on the IETF Datatracker. Ask questions about the specification in its issues.
amap-router-local
The reference runtime, with its own tests and issue tracker.
amap-connector-claude
The Claude Code connector, which uses only the standard library.
amap-connector-codex
The Codex connector: a supervisor that wakes a Codex app-server thread per validated notice, with the same gated submit.
amap-deploy-sandy
A working deployment of the reference runtime and connector on one host. Its walkthrough gets two agents talking, then breaks each guarantee on purpose.
amap-release
Release manifests that pin the exact commits of the router, connectors and deployment that make up one release.
How changes are made today
Until the IETF takes up the work, changes are proposed as pull requests to amap-spec, and the rules below keep the two sides of the boundary in step. If a working group forms, change control moves to it, and these repositories will follow its decisions.
- Specification first. A capability change lands as specification, schemas and fixtures together, before either side builds it. No implementation invents a wire field locally.
- Fixtures in the same change. A field with no fixture is a field no implementer can prove they handle.
- The wire version changes only when a counterpart speaking the old major could no longer accept whole documents safely. Additive changes leave
contract_versionalone. A consumer that reads a version it doesn't support fails closed, as a logged version refusal, never a silent mis-parse. See the changelog.
Read CONTRIBUTING.md before opening a pull request.
Security reports
Don't open a public issue for a security problem. See Security and disclosure for where to report. For the specification, the interesting reports are clauses that can't be satisfied securely, schemas that permit what the prose forbids, and attacks the trust model doesn't account for.
Wanted
Interop partners
Organisations willing to run a first deployment across independent organisations, with a human-only counterparty if need be.
Connector authors
A connector for your agent platform, proven against the same fixtures.
Identity and standards work
Input on agent identity, sender verification and the IETF draft. See Identity.
Discussion
An IETF mailing list is planned for discussion ahead of a possible BoF. It will be announced on AMMP at the IETF. Until then, please use the amap-spec issues for questions and discussion.
Who is behind AMMP
Proofpoint originated AMMP. The AMMP specification, schemas, fixtures and reference implementations are published under the Apache License 2.0 and are open to every implementer. No one needs a particular vendor's runtime to conform or to interoperate.