What it checks
- Artifact structure and canonical JSON bytes
- Protocol revision and registered extensions
- Deployment bindings and effective bounds
- Evidence and typed denials
[ABP] Agent Blueprint Protocol
Agent Blueprint Protocol provides language-neutral artifacts for agent capabilities, deployment bindings, and task records. Elixir and TypeScript verifiers report protocol facts. Verification is non-authorizing and never grants permission to act.
Each artifact has a defined shape and a public specification.
| Artifact | Purpose |
|---|---|
| Blueprint Core | Describes identity, ports, capability requirements, bounds, and extensions. |
| Deployment Manifest | Binds one Blueprint release to environment-specific descriptors and bounds. |
| Federation TaskEnvelope | Records a task's identity, state, and terminal commitments for transport. |
Protocol validity never grants authority. A consuming host makes its own decisions.
Run the TypeScript verifier from npm. For Elixir, add the dependency below to mix.exs, then run mix deps.get.
npx @agent-blueprint-protocol/verifier@1.0.0
{:agent_blueprint_protocol, "~> 1.0.0"}
mix deps.get
Start with a quick verification, then read the contract and its extension profile.
Installation, first verification, typed results, and conformance.
Run a Livebook that uses the Elixir package and its examples.
Read the protocol and inspect the registered federation extension.