storyobjectmodel.comjoining

What joining actually is.

Nothing about your product comes out. One system is enough to start. Tier 1 is subscribe and publish and takes days; Tier 2 carries bidirectional structured context; Tier 3 lets your tool decide autonomously against the story. Change control is in writing.

Tools around a shared story bus Five newsroom tools sit above a single bus. Each one publishes to it, subscribes to it, or both. One live story object rides the bus, and a rulebook of Skills written by the newsroom sits above the tools. There is no orchestrator and no central application: each tool reads the story and decides for itself. THE RULEBOOK Skills your newsroom writes · declare, never act · silence is a valid outcome Planning subscribes Rundown publishes · subscribes Graphics subscribes Transcription publishes Social publish subscribes THE STORY one live object · decided, cleared, held THE BUS publish and subscribe · JSON envelope · media never travels here No orchestrator and no central application. Each tool reads the story and decides for itself.

Who publishes, who subscribes, and who does both. An arrow into the bus is a system writing to the story; an arrow up into a tool is that tool reading it.

The schemas are served at storyobjectmodel.com/schema/1.0/, and the worked examples in the repository show what a conformant message looks like. To talk an integration through, email hello@storyobjectmodel.com.

Taking part

The working group is open. Anyone implementing the model or affected by it is welcome; the existing consortium is its foundation, not its boundary. How changes are made is set out in GOVERNANCE and CONTRIBUTING. To follow the work, use the form on the home page.

read the specification