Govern the pipes once. Govern every client.
A2A tasks and artifacts are typed events with named consumers — the standard's event-bus requirement expressed as an interop protocol. Ledger at the task boundary and inter-agent work becomes provable.
Every agent that speaks the protocol inherits governance from the boundary — no per-framework adapter, no SDK dependency, no redeployment of the agents themselves.
Protocol boundaries are where tool calls and tasks already flow. A governing gateway makes that boundary an ownership gate and an append-only ledger — the two hardest substrate requirements, solved at the layer designed for interception.
Cross-vendor agent ecosystems only work if the work is provable across trust boundaries. A ledgered protocol boundary is how two organizations’ agents cooperate and both sides keep a record they trust.
The pattern for agent protocols: Gateway governance: a governing proxy at the protocol boundary ledgers every call or task and enforces ownership gates for any compliant client — one integration governs an entire ecosystem, framework by framework, without touching any of them.
Why A2A fits: A2A tasks and artifacts are typed events with named consumers — the standard's event-bus requirement expressed as an interop protocol. Ledger at the task boundary and inter-agent work becomes provable.
The full requirements live in the open standard (CC BY 4.0) — the substrate shapes, the acceptance tests, and the conformance ladder your record is measured against.
A governed protocol boundary lets every system behind it claim a real, inspectable ledger — and the gateway operator can publish its own conformance record to the registry with probe logs. As always: self-assessed, open to challenge, never “certified.”
Integration pattern: documented (this page). The A2A adapter, mapping, or worked example is being built in the open — progress, scope, and acceptance criteria live in the public GitHub issue. This page will not say “supported” before that issue closes with a working example. Holding our own pages to the standard’s claims discipline is not modesty; it is the product.
For gateway vendors, protocol implementers, and platform teams standardizing on agent protocols: governance-at-the-boundary is a product surface, not a feature — and the reference pattern is open. We co-develop the pattern in public and route ecosystem-level governance inquiries to the implementers who ship it.
Different stack? Browse all 45 integrations — or run the free audit from any MCP-capable tool.