On the bus in about 15 minutes.

• 202 accepted

  Valid SOM 1.0, in order for its story, from a system allowed to send it. Delivered to every subscriber.

• 200 duplicate

  The same message_id again. Safe to retry: nobody receives it twice.

• 409 refused

  An older snapshot after a newer one. Refused before any consumer sees it, with the rule behind it.

  sequence_number.not_increasing

1. Fill in the Request access form
2. Keep your REQ-… reference
3. Your sign-in arrives by email once approved

1. Sign in with the temporary password, set your own and add an authenticator app
2. Accept the invitation to your workspace
3. Apps → New app: name it and claim the system_id it stamps
4. Connect: choose the message types it may publish
5. Copy the client id, secret and workspace id. The secret is shown once

export CLIENT_ID=c…          # from Connect
export CLIENT_SECRET=sbs_…   # shown once: put it in your secret store
export WORKSPACE=w…          # shown with the credentials
export SYSTEM_ID=acme-ncs-01 # the system_id your app claimed

TOKEN=$(curl -s https://api.sombus.rnd-solutions.net/v1/oauth/token \
  -u "$CLIENT_ID:$CLIENT_SECRET" -d grant_type=client_credentials | jq -r .access_token)

curl -sO https://raw.githubusercontent.com/storyobjectmodel/som/7297fef9adc6d14a74bdd7550c78decaa099a1ad/examples/hurricane-run/hurricane-01.json
STORY=$SYSTEM_ID-$(date +%s)
CORRELATION_ID=$(uuidgen | tr A-Z a-z)   # one per story: reuse it for every message about it
jq --arg mid "$(uuidgen | tr A-Z a-z)" --arg cid "$CORRELATION_ID" \
   --arg story "$STORY" --arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" --arg sys "$SYSTEM_ID" \
  '{som_version: "1.0.0", message_id: $mid, correlation_id: $cid, message_type: "story.context",
    timestamp: $ts, originating_system: {system_id: $sys, system_type: "ncs"},
    topic: "som.story.context", payload: (. + {story_id: $story})}' hurricane-01.json > msg.json

API=https://api.sombus.rnd-solutions.net/v1/tenants/$WORKSPACE
curl -s -X POST $API/validate -H "Authorization: Bearer $TOKEN" \
  -H 'content-type: application/json' --data-binary @msg.json   # dry run: publishes nothing
curl -s -X POST $API/messages -H "Authorization: Bearer $TOKEN" \
  -H 'content-type: application/json' --data-binary @msg.json   # {"accepted":true,…}

1. Consumer: create a consumer connection before you publish (it receives only what is published after it is ready), then read your queue with the HTTPS pull API
2. Skill executor: start a test run and read each case, expected against actual
3. Producer: publish a whole story and check every verdict in Activity
4. Share a results statement with a publisher, or by link

curl -s -H "Authorization: Bearer $CONSUMER_TOKEN" \
  "https://api.sombus.rnd-solutions.net/v1/tenants/$WORKSPACE/consumers/$CONSUMER_ID/messages?wait=20"