The Story Is the Standard

This week in Amsterdam, a new standard takes flight.

HyperContent™ is working on two open standards right now, and helping with earlier work on a few more. The two in focus sit at opposite ends of a story’s journey. The Story Object Model, from the IBC Accelerator’s Smart Stories team, gives every tool in a newsroom one shared understanding of what a story is. Really Simple Licensing gives publishers a machine readable way to set the terms on which AI systems use that story. One governs how a story is made. The other governs how it is bought.

The first is what brought us to Amsterdam. HyperContent is one of the vendors demonstrating the Story Object Model at the IBC Accelerator Zone. We brought one of the first AI native workflow tools onto the Smart Stories team. We took part in three workflow demos. And we represented a part of the chain most story object systems never reach.

Most of them live between newsgathering and transmission. The story is planned, produced, versioned, and sent to air. HyperContent picks it up after that. If the story object stops at air, it has done half its work.

I want to explain why that second half matters, why the two standards belong in one conversation, and why someone who spent his newsroom years on the production side of the chain is now standing in Hall 14 talking about feeds, newsletters, and AI answers. The short version: this is the same move the industry has made before. It has paid off every time.

The pattern that keeps working

A standard is how a separation becomes portable.

MOS separated newsroom control from any one vendor’s device. SOM separates story context from any one vendor’s tool. Really Simple Licensing separates rights from the page. HyperContent separates the experience from the story.

Each of these made the market bigger. Not by picking a winner. By letting more people build on the same thing. That is the whole argument. Everything below is evidence.

MOS, when the ground moved

I came to MOS at an awkward moment. Newsroom stacks were moving off the desktop. The old world was ActiveX plugins sitting inside thick clients. The new world was the browser. That is not a cosmetic change. It is the floor moving under a room full of vendors who all had to keep working together.

I helped the MOS community evolve the plugin model so HTML5 editors could sit inside the rundown the way ActiveX components used to. The interface changed completely. The contract did not.

That is the lesson I carry into every standards conversation now. The founding is the easy part. A standard proves itself when the technology underneath it shifts and the agreement holds anyway.

What MOS actually was

MOS looked like a technical breakthrough. It was a commercial one wearing technical clothes.

Before MOS, buying a newsroom meant buying a vendor’s whole worldview. After MOS, competing vendors could serve the same customer without any one of them owning that customer. Broadcasters bought best of breed. The rundown became the hub. The tools became plug-ins. Producers worked in one place and the machinery followed them.

Composition beat the monolith. It usually does.

What MOS did not do

MOS moved objects. It did not move meaning.

Nearly three decades later, a rundown, a media asset manager, and a graphics system each hold a fragment of the same story. A planning tool holds another. None of them share an understanding of what the story is. They pass identifiers back and forth and hope the humans hold the meaning together.

That was tolerable when the tools were passive. You told them what to do and they did it. It stops being tolerable the moment the tools start acting on their own. An agent needs to know what a story means, what its rules are, and where its facts came from. Passing an object reference does not carry any of that.

SOM: the same move, one layer up

The Story Object Model makes the story itself a first class object. Every tool subscribes to it. Context, provenance, and machine readable editorial guidelines, the team’s Skills reference architecture, travel with the story rather than living in one vendor’s database.

Human control stays exactly where it belongs. The machinery follows. That part is unchanged from MOS.

What changes is who the subscribers are. Today they are applications. Tomorrow they are agents. SOM has to survive that shift the way MOS survived the jump from ActiveX to the browser. If it does, the market gets bigger again.

Why we are in the room

HyperContent starts from one premise. The story is fixed. The shape changes.

To hold that line you need the story and its editorial rules structured and intact before anything downstream touches them. SOM is what makes that possible for every vendor, not just for us. So we have a direct interest in it working.

Then we take the story object past transmission. Into feeds. Into video. Into newsletters. Into AI answers. Same story, different shape. The editorial voice stays intact because the rules travel with the object.

Keys, not code. Connecting a destination is configuration, not a sprint. The meaning travels with the story, and each surface receives the shape it needs.

The demand side

The second standard we are focused on works at the other end of the story’s journey, and it follows the MOS logic exactly.

Really Simple Licensing is machine readable licensing terms for AI content use, including pay per crawl and pay per inference. Think of it as MOS for the demand side. Many buyers, many sellers, and no bespoke deal negotiated every single time.

The rails price access, on terms the publisher sets. HyperContent shapes what the buyer receives. Because here is the part the industry keeps missing: agents are an audience. Not a threat to route around. A destination to serve. Sell the answer, not the scrape.

Earlier work

Behind those two is work at an earlier stage: agentic workflow standards. Right now every vendor rebuilds the same agent integration from scratch. That is wasted effort, and it is a repeat of the pre-MOS world where every connection was bespoke. Agents should not require it. HyperContent intends to help advance agent handoffs that carry story context and editorial rules with them. The MOS lesson is plain. Standardize the handoff and a market forms.

The bet

Every open media standard is a bet that the industry is bigger than any single vendor. That bet has paid off every time it has been placed. MOS proved it. SOM and RSL are proving it now.

The agentic era is the same bet, made again, with higher stakes and a wider field.

If you are at IBC, come find us. Hall 14, Accelerator Zone. Our Smart Stories showcase is Saturday 12 September at 16:00. Come see the work, and come watch a story arrive intact somewhere it was never designed to go.

That is the whole idea. The story is the standard. Everything else is shape.