SOM

The SOM tab holds your organization's SOM bus connection: where the bus is, how Nuvelics signs in to it, and which messages Nuvelics reads. There is one bus connection per organization, so this tab is one form rather than a list. This page is the steps; what the SOM bus carries is in The SOM bus, and what you see of it in the app is under SOM.

Who can use itCopy Anchor Link

Owners and admins (som:manage). The tab is missing for Members and Viewers, who can still read SOM activity under SOM.

Set up the connectionCopy Anchor Link

If your organization has no connection yet, the form is empty. Fill it in and choose Save; you see SOM configuration saved.

1. Under Roles, turn on SOM Consumer to read messages from the bus. SOM Producer is shown but cannot be changed: publishing Nuvelics' own stories to the bus is not available yet. While the integration is not paused, at least one role must be on, or you are told Turn Consumer on, or pause the integration instead.
2. In Bus brokers, enter one or more Kafka bootstrap brokers as host:port, separated by commas and without a scheme, for example bus.example.com:9094,bus-2.example.com:9094. Whether the connection is encrypted is the Encryption setting, not part of this value. A malformed list is refused: Enter one or more brokers as host:port, comma-separated.
3. Under Topics to subscribe, choose Add topic for each topic to read. Wildcards work, for example som.story.*. At least one topic is required (Add at least one topic).
4. Leave Encrypt the connection (TLS) on unless your bus does not support TLS.
5. Choose the Authentication: SASL, which signs in with a username and password, or No authentication for a bus with no credential gate. For SASL choose the SASL mechanism, PLAIN, SCRAM-SHA-256 or SCRAM-SHA-512, and enter the Username and Password. The credentials are stored encrypted and are never shown again.
6. Optional: turn on Execute skills (see below).
7. Choose Save.

Execute skillsCopy Anchor Link

Execute skills, under Enrichment skills, runs enrichment (a fact check) on each story snapshot received from the bus, plus every enabled story check whose Channels include SOM snapshots (when skills are on), and publishes the results back to the bus. It runs language-model and search work on every message the organization receives, which costs money per message. It only processes stories received from the moment you turn it on; stories received while it was off are never processed afterwards. It needs SOM Consumer on and a subscribed topic covering som.story.context. If you turn the consumer off, the selection is cleared on the next save and cannot be set again from there.

Read the connection statusCopy Anchor Link

At the top, Bus connection shows what Nuvelics' connection to the bus is doing. Opening the tab does not open a connection or change anything. The status is one of:

• Connected: Nuvelics is connected using the settings below.
• Connecting: the connection is opening, normally within a few seconds.
• Checking: it is checking the settings you just saved.
• Paused: the integration is paused, so no connection is open.
• Not reported yet: normal right after setup; the first result usually appears within a minute or two.
• Status stale: no recent report; if it does not clear within a few minutes, contact support.
• Not connected: Nuvelics could not use the bus. The card shows the recorded detail and a hint by cause. If the bus rejected the credentials, confirm the username with your bus operator and enter a new username and password. If it could not reach any broker, check the broker addresses and ask your network operator to allow the connection. If the credentials were accepted but the bus does not grant what was asked, check your topics against what your bus operator granted the account.

Change the connectionCopy Anchor Link

Edit any field and choose Save. Some changes need the credential again:

• Replace the credential by entering a new username and password together. Entering a username alone is refused: Enter the password to change the username.
• Changing the brokers, turning off TLS or switching to PLAIN without it needs the password again: Re-enter the password to change the brokers, turn off TLS or switch to PLAIN without it.
• Switching to No authentication requires clearing the SASL credentials first.

Otherwise leave the Username and Password blank to keep the stored ones. The System ID and Consumer group ID, under Bus identifiers, are derived when the connection is created and cannot be edited; share them with your bus operator.

If another person saved first you are told "This SOM configuration changed since you loaded it — reload and try again."

Pause the integrationCopy Anchor Link

Turn on Pause integration under Availability and save. Pausing stops Nuvelics connecting to the bus and nothing else: the brokers, topics, skills and stored credential are kept. Clear it and save to resume with the same settings.

Remove the integrationCopy Anchor Link

At the bottom, Remove SOM integration ends it for good. This cannot be undone: it destroys the stored SASL credential, so you would need to obtain the bus password again, and it removes the broker, topic and skill settings. Messages already received and audit records are kept.

1. Choose Remove integration.
2. Type your organization's slug to confirm. Remove integration stays disabled until it matches exactly.
3. Confirm.

You see SOM integration removed. To stop only for a while, use Pause integration instead.

Other ways to manage the connectionCopy Anchor Link

• API: SOM configuration.