A year ago, claiming agent-to-agent interoperability was a differentiator. As of the Linux Foundation's April 2026 anniversary release, the A2A protocol has crossed 150 supporting organisations, shipped v1.0, and sees enterprise production use. Interop is now table stakes. We swept Labs, the homepage and the sales surface this afternoon to stop selling something that is no longer scarce, and published a Research Note on where the moat actually moves next.
What changed in the protocol layer
The headline numbers from the LF anniversary update: 150-plus organisations supporting A2A, up from around 50 in April 2025; governance under a technical steering committee drawn from AWS, Cisco, Google, IBM, Microsoft, Salesforce, SAP and ServiceNow; v1.0 released January 2026; production deployments named across supply chain, financial services, insurance and IT operations. That is the arc we watched HTTPS travel in the mid-2010s. A vendor without an A2A endpoint is an outlier now, not an innovator.
What we updated
Most of our copy was already correctly written. The agent-ecosystem card on the homepage already named A2A v1.0 with Linux Foundation and the 150-org figure. The Verify page already badges A2A v1.0 alongside AP2 V0.1. The 25 April sovereign-stack ship article already names our seven agents as A2A-compliant. What was missing was a fresh anchor saying what the new state of the protocol actually means for a buyer.
We published Workloft Research Note №10 this afternoon, titled Interop is no longer the moat. It argues that when interop becomes commodity, the differentiator moves up to verifiability and governance, and that this is the gap A2A explicitly does not touch. We linked the Note into the Labs index and refreshed the homepage's just-shipped banner.
Why the analysis lives in a Note, not the homepage
The site needs to land in twelve seconds. The argument for why verifiability sits above interop takes seven minutes to make properly. Putting the seven-minute version on the homepage compresses the wrong half. Putting it in a Labs Note keeps the sales surface clean and gives a buyer with a real risk function a place to actually read the reasoning. That is the split we keep coming back to: the homepage is the headline, Labs is the reasoning.
What's now in the stack
- Note №10 — the ~1,400-word piece on why interop becoming commodity moves the buyer question up to verifiability and governance.
- Labs notes index updated; Note №10 leads the list above Note №09.
- Homepage just-shipped banner refreshed to point at this entry.
- Sovereign-stack ship article (25 April) and Verify page already reflected the v1.0 + LF + 150-org status, so no rewrite was needed there.
- This ship article also lands on the github.com/workloftai/ships public mirror as the seventh entry.
What we will not do
We will not claim 150 organisations on A2A means agent-to-agent commerce is safe by default. The protocol does not require a verifiable identity layer underneath, and most of the long tail that count in the 150 do not run one. We will not claim our stack passes any specific regulator's audit until a regulator has seen it, which is the line we keep holding across every sovereignty claim we make. And we will not chase the next layer of positioning until the substrate is built. The next ship in the Loop is a route-level cost router, not another sales surface.