Quirin Schlegel

Loading

It signs the sender, not the sentence — A2A joins the Agentic AI Foundation and Article 50(2) still has no carrier

Google's Agent2Agent protocol became a hosted project of the Agentic AI Foundation on 17 August 2026, putting both halves of the agent stack under one neutral governance body. A2A version 1.0 already ships Signed Agent Cards - canonicalised JSON, cryptographic signature, client-side verification - so the protocol is not naive about trust; it answers who sent a message and says nothing about what produced its content. The specification defines no provenance, watermarking or C2PA semantics, and the extensions documentation's own data-only example is GDPR compliance data in an Agent Card. AI Act Article 50(2) puts the machine-readable marking duty on providers of AI systems generating synthetic text; Article 50 has applied since 2 August 2026 and the marking obligation lands 2 December 2026. A standards foundation is not a provider of an AI system and owes nothing under Article 50, so the spec's silence is permanent and the deadline is not. In a chain it is 50(4) that bites: the deployer disclosure for AI-generated text published to inform the public, whose exception is human editorial review - which an autonomous agent chain by construction does not have.

19 August 202615 verified claims10 sources

Google moved A2A to the Agentic AI Foundation on 17 August. Both halves of the agent stack now sit under one neutral roof — and neither half can tell you whether a machine wrote the text passing through it.

A2A joins MCP, goose, AGENTS.md and agentgateway. One governing board, one technical committee. Axios puts AAIF past 250 members.

Adoption is real: at its first anniversary in April, A2A counted 150+ organisations, up from 50+ a year earlier, with five production SDKs.

Now the correction.

A2A v1.0 shipped Signed Agent Cards — canonicalised JSON, cryptographic signature, client-side verification. That answers "is this agent who it claims to be". It answers nothing about the content in the Artifact it returns.

The extension mechanism exists too: AgentExtension objects in AgentCapabilities, an A2A-Extensions header, four scopes. The spec's own example of a data-only extension is GDPR compliance data in an Agent Card. The hook is there. Nothing hangs on it for provenance.

Now the European part.

Article 50(2): providers of AI systems generating synthetic audio, image, video or text shall ensure the outputs are marked in a machine-readable format and detectable as artificially generated. Article 50 has applied since 2 August 2026. The marking obligation lands 2 December 2026.

The reasonable reading is that neutral governance will eventually put provenance in the spec. But Article 50 binds providers of AI systems — a standards foundation is not one. The spec can stay silent for a decade and your December date does not move.

And 50(4) is what bites in a chain. Deployers publishing AI-generated text to inform the public must disclose it, unless the content went through human editorial review. An autonomous agent chain, by construction, did not.

What I'd do Monday:

1. Declare a provenance extension URI in your Agent Card. Data-only, not required. Invent it if you must — a declared field beats a December scramble. 2. Treat every Artifact arriving over A2A as unmarked. Default to marking on republish. 3. Record which remote agent produced each Part, beside the task ID. Article 30 asks. Article 50(4) asks. 4. Name the human performing your editorial review, or stop claiming the exception.

The stack got a signature for the sender. It still has none for the sentence.

Which of your agents could prove, this morning, that a human wrote its last output?

#AgenticAI #EUAIAct #AIEngineering #AIGovernance #Berlin

Evidence

What this rests on

Every factual claim in the edition above, stated on its own and checked before publication. If one of these is wrong, the argument is wrong — so they are listed where you can check them.

On 17 August 2026 Google's Agent2Agent protocol (A2A) became a hosted project of the Agentic AI Foundation, placing it under the same neutral governance as the Model Context Protocol.
Why it mattersThe two protocols an EU team is most likely to have in production now share a governing board and a technical committee. That makes the foundation the natural place to look for compliance-shaped features — and the wrong place to wait.
agenticaifo2026agentic · axios2026exclusive · techzineglo2026google
The Agentic AI Foundation hosts A2A alongside the Model Context Protocol, goose, AGENTS.md and agentgateway, and runs eight working groups including Governance, Risk & Regulatory Alignment and Observability & Traceability.
Why it mattersThere is a named venue for regulatory alignment work. If you want a provenance extension to exist, that is where the proposal goes, and it is worth knowing before December.
agenticaifo2026agentic
The Agentic AI Foundation was formed on 9 December 2025 with three anchor projects: the Model Context Protocol contributed by Anthropic, goose from Block, and AGENTS.md from OpenAI.
Why it mattersDates the governance body a practitioner is being asked to trust. It is eight months old.
linuxfounda2025linux
The Linux Foundation's formation release names 47 members across three tiers: 8 platinum (Amazon Web Services, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, OpenAI), 18 gold and 21 silver.
Why it mattersThe only membership figure with a primary source behind it. Anything quoted as a starting number should be checked against this one.
linuxfounda2025linux
At A2A's first anniversary on 9 April 2026 the protocol counted more than 150 supporting organisations, up from more than 50 at its April 2025 launch, with 22,000+ GitHub stars and five production-ready SDKs (Python, JavaScript, Java, Go, .NET).
Why it mattersEstablishes that this is production infrastructure rather than a proposal. A gap in a spec that nobody ships is a curiosity; a gap in a spec five SDKs implement is a deadline.
linuxfounda2026aa
A2A version 1.0 introduced Signed Agent Cards: deterministic JSON canonicalisation, cryptographic signature, and client-side verification against the agent's public keys, so that a card cannot be tampered with in distribution.
Why it mattersThis is the protocol's answer to trust, and it is an answer about the sender's identity. Reading it as an answer about content is the error the edition corrects.
linuxfounda2026aa · aaproject2026agentagen
A2A's AgentCard, Message, Part and Artifact objects carry free-form metadata key-value maps described in the specification as flexible fields for additional context or parameters.
Why it mattersThere is somewhere to put a provenance assertion. There is no agreement on what to put there, which is a different problem and a solvable one.
aaproject2026agentagen
The A2A specification defines no semantics for content provenance, watermarking, C2PA or Content Credentials, and no mechanism for marking content as artificially generated.
Why it mattersAn artifact crossing an A2A boundary arrives with no protocol-level indication that a model produced it. If you republish it, that is your Article 50(4) problem, not the sender's.
aaproject2026agentagen · aaproject2026aa
A2A extensions are declared as AgentExtension objects inside AgentCapabilities with a URI, description, required flag and params, negotiated via an A2A-Extensions HTTP header, and default to inactive; four extension scopes exist (data-only, profile, method and state machine).
Why it mattersThe route to shipping a provenance field today, without waiting for the spec: declare a data-only extension, not required, so extension-unaware clients are unaffected.
aaproject2026aa
The A2A extensions documentation's own worked example of a data-only extension is GDPR compliance data carried in an Agent Card; the documented example extensions are Secure Passport, Timestamp, Traceability and Agent Gateway Protocol.
Why it mattersThe mechanism was designed with European compliance data explicitly in mind. Nothing has been hung on it for content marking.
aaproject2026aa
AI Act Article 50(2) requires providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content to ensure the outputs are marked in a machine-readable format and detectable as artificially generated or manipulated.
Why it mattersThe duty is on the provider of the AI system, machine-readable, and it covers text. An agent that drafts prose is inside it.
euaiactexpl2026article
AI Act Article 50(4) requires deployers publishing AI-generated or AI-manipulated text to inform the public on matters of public interest to disclose that it is artificially generated, with an exception where the content has undergone human review or editorial control.
Why it mattersThe exception is the practical hinge. An autonomous chain with no named reviewer cannot claim it, so the disclosure is not optional for that pipeline.
euaiactexpl2026article
The AI Act's Article 50 transparency obligations started to apply on 2 August 2026.
Why it mattersThe obligations are live now, not pending. Only the marking-format element still has runway.
europeancom2026commissio · euaiactexpl2026article
The European Commission published the Code of Practice on Transparency of AI-generated Content on 10 June 2026 as a voluntary instrument supporting the Article 50 transparency obligations.
Why it mattersThe nearest thing to an agreed marking format, and it lives outside the agent protocols entirely. Read it before inventing a field.
europeancom2026code
A2A was unveiled by Google in April 2025 and transferred to the Linux Foundation in June 2025, with more than fifty partners supporting it at launch, before moving to the Agentic AI Foundation in August 2026.
Why it mattersTwo governance moves in sixteen months. Governance is settling faster than the data model is.
techzineglo2026google

Sources

A2A Projectprimary source
A2A Extensions
Original Archived PDFretrieved 19 August 2026 · published 19 August 2026
Linux Foundation via PR Newswireprimary source
A2A Protocol Surpasses 150 Organizations, Lands in Major Cloud Platfor
Original Archived PDFretrieved 19 August 2026 · published 9 April 2026
A2A Projectprimary source
Agent2Agent (A2A) Protocol Specification
Original Archived PDFretrieved 19 August 2026 · published 19 August 2026
Agentic AI Foundationprimary source
Agentic AI Foundation (AAIF)
Original Archived PDFretrieved 19 August 2026 · published 17 August 2026
EU AI Act Explorersecondary
Article 50- Transparency Obligations for Providers and Deployers of Ce
Original Archived PDFretrieved 15 October 2026 · published 1 January 2026
European Commissionprimary source
Code of Practice on Transparency of AI-generated Content
Original Archived PDFretrieved 19 August 2026 · published 10 June 2026
European Commissionprimary source
Commission starts enforcing AI Act rules and new transparency requirem
Original Archived PDFretrieved 19 August 2026 · published 31 July 2026
Axiossecondary
Exclusive: AI agents inch toward interoperability
Original Archived PDFretrieved 19 August 2026 · published 17 August 2026
Techzine Globalsecondary
Google transfers A2A to the Agentic AI Foundation
Original Archived PDFretrieved 19 August 2026 · published 17 August 2026
Linux Foundationprimary source
Linux Foundation Announces the Formation of the Agentic AI Foundation
Original Archived PDFretrieved 19 August 2026 · published 9 December 2025

Every source for this edition, as one PDF BibTeX — all editions

Corrections

What changed after publication

None for this edition. The membership figures are handled with care rather than repeated: Axios describes the Agentic AI Foundation as growing from fewer than 40 members, while the Linux Foundation's own formation release names 47 - 8 platinum, 18 gold and 21 silver. The 250+ current figure is Axios's alone and is carried as attributed context, not as a verified claim. The absence of provenance semantics in A2A is stated from the specification and the extensions documentation directly, not inferred from commentary.