storyobjectmodel.comexample workflows
What it looks like on the desk.
SOM is not a workflow system and it is not a tool. It carries story context to the tools you already run, old and new, agents included, so each of them can do its own job with the story in hand. It prescribes nothing about how you work.
So these are illustrations, not instructions. Every one of them is something newsrooms already do, shown as it goes when the context can travel: what is written to the story, what tools do with it on their own, what stays a human decision, and what is left behind afterwards. Your desk will differ in every particular, and none of this is required by the standard.
01
An unconfirmed figure, two destinations
A casualty number is circulating. One source, nobody official, and the digital desk wants to go now.
on the busThe duty editor makes the call in the tool they already use. The hold is written to the story, with the rule it was made against and the person who made it.
the toolsEvery subscribed tool sees it at once and applies the rules its own newsroom wrote. The graphic does not play. The ticker drops the figure. The clip cannot run. The web desk sees the figure marked rather than missing.
the personNothing else. They made the call once, in one place, and did not spend the next hour telling six teams about it.
afterwardsWhen the second source lands, the hold lifts in the same place and everything that was waiting is released together, with the clearance attributed and timed.
02
The fact changes after everything is built
The storm is reclassified, or the figure is revised, an hour after the package cut and the graphics rendered.
on the busThe change goes to the story once, at source, with what it was and what it now is.
the toolsEvery tool holding something built on the old fact sees that it is stale. The scripts, the graphic, the social cutdown and the page each raise it in their own way, and each decides for itself whether to hold, revise or withdraw.
the personReviews a list of what is affected rather than trying to remember it. The judgement stays human; the recall does not.
afterwardsA trail showing what was live on the old fact, for how long, and what each tool did about it.
03
A clip arrives from the public
A bystander clip lands. It might be the best pictures of the day, or it might not be what it claims.
on the busThe clip becomes an asset on the story with whatever came with it: where it came from, what credentials it carries, what is missing.
the toolsVerification tools read the story and post what they find as assertions: an authenticity check, a match against known material, a transcript. None of them publish anything and none of them act.
the personDecides. The verdict from a tool is evidence for that decision, never the decision itself, and the gate on the clip reads the verdict where it sits.
afterwardsThe reason the clip ran, or did not, on the record, and attached to the clip rather than to a chat thread.
04
A cleared asset goes somewhere new
Something approved for the bulletin is now wanted on the site, and then as a cutdown for social.
on the busThe clearance sits on the link between the asset and the destination it was cleared for, not on the asset itself.
the toolsEach destination reads the clearance for its own route. What was cleared for broadcast does not silently become cleared for everywhere.
the personClears the new route, usually in seconds, because the evidence is already there. If the words have changed since the original approval, the gate reopens rather than inheriting it.
afterwardsReach without laundering: one decision reused deliberately, not a permission that leaked.
05
Somebody asks about it six months later
A complaint, a regulator, a lawyer, or your own archive desk wants to know what was broadcast and what was known at the time.
on the busNothing new. The story already carries what was decided, by whom, against which rule, and which frames each decision applied to.
the toolsThe tools that were involved each published what they did at the time, in their own message family, on the same story.
the personAnswers the question from the record instead of reconstructing it from six systems and the memory of whoever was on shift.
afterwardsThis is the part that is hard to retrofit and almost free once the context travels: the audit trail is a by-product of how writes work, not a system somebody had to build.
06
An agent joins the desk
You have built something, or bought something, that can read a story and suggest work.
on the busIt subscribes like any other participant. It reads the story, and the Skills your newsroom has written are the rules it is held to.
the toolsIt declares what it finds, in its own family, attributed to it. It never sends work to another tool and never commands anything. If it has nothing useful to say, silence is a valid outcome.
the personApproves, edits or ignores. Anything an agent generates that reaches an audience becomes an asset with its authorship carried, so it can be told apart later.
afterwardsAn agent that is accountable in the same terms as everything else on the desk, rather than a clever black box nobody can audit afterwards.
The shape underneath
The same three moves appear in all six. A person makes a decision in the tool they already use, and it is written to the story once. Every tool reads the story and decides for itself what to do, against rules its own newsroom wrote. Nothing is orchestrated and nothing is commanded, so what each tool did is recorded as it happens rather than reconstructed afterwards.
That is the whole of it. The where it goes page covers which part of a story carries what, and the demos show two of these running with real production tools.
how to join