Appearance
story.not_owner
Tolerated by default Per workspace policyA system that does not own the story published a snapshot of it.
| Outcome | Set per workspace. By default accepted (202), listed under tolerated; a workspace can refuse it (409) or not check it |
| Source | policy: This bus's operational rules (identity, grants, size, idempotency, story ownership). Not a verdict of the SOM standard. |
| Checked at | Story ownership (see the order of checks) |
| Applies to | story.context messages |
What it means
SOM 1.0 does not say who may write a story; this bus does, per workspace. The first system to publish a story (its originating_system.system_id) owns it. The workspace can list hand-offs, such as ncs to cms: the next writer in a listed pair takes the story over with its first accepted snapshot. A snapshot from any other system breaks this rule. Each workspace chooses what happens: warn (the default: accepted, listed under tolerated), reject (refused with 409, nothing recorded) or off (not checked). A snapshot from a system that is not the owner never moves ownership, even when it is accepted.
What to do
Publish the story from the system that owns it. If your newsroom hands stories over between systems, ask a workspace admin to add the hand-off (from the owner's system_id to yours) in the portal, under Story ownership. For a test with a fresh owner, use a new story_id.
Related rules
Branch on the rule id, never on the violation's message text. All rules: rule catalogue.