Going live, and exporting your house

The shared bus is a sandbox: synthetic content, for testing. When you go live, RND runs a private bus for your newsroom, built from the house you tested. It is never shared: no other publisher's traffic, connections or data are on it, and you don't deploy or operate it yourself.

	Status
Export your house as a bus config	Available now, in the portal
Your private production bus, run by RND	Next: not available yet. Ask RND when you are ready

Export your house

Sign in to the portal, choose your house and open Routing map. Owners and admins see Export as a bus config; Download bus config saves a YAML file named after your workspace, such as daily-planet.bus.config.yaml. Every download is in the workspace's audit log. Other roles don't see the button.

The file is what your private bus will be built from, so you can read exactly what would go live.

What the file holds

Part	From your house
producers	Each active producer connection: its system_ids and the message types it may publish
consumers	Each active consumer connection: its message types, topic prefix and sources (source_producers, source_system_ids), and how many deliveries a message gets before its dead-letter queue
Identities	Your organisation's connections' AWS principals that have proved control, and clients of your own identity provider with that provider's settings (bus.jwt_issuers)
bus.story_ownership	Your story ownership setting: the mode and the hand-off pairs
skills	Your house's configured skill instances: each one's skill and version, instance label, values and authority scale, and the consumer (the vendor's executor) that runs it. Left out when your house has registered none
Comments	Each connection's app and organisation, above its entry, and which executor runs each configured instance

Producer and consumer ids are the connection ids you see in the portal, so a consumer's sources and your logs keep their names. The file routes messages exactly as your house does: who publishes each message type and who receives it is the same as your Routing map.

Every connection in the house is exported the same way, whichever organisation owns its app. Revoked connections are left out, since they route nothing, and listed at the top of the file.

What it never holds

• Client secrets, their hashes, tokens and usage keys.
• Messages, payloads, verdicts and story timelines.
• Another organisation's identities: the AWS principals and identity-provider clients of apps other organisations connect to your house are theirs. The file lists the connections they belong to.
• Queue readers: the AWS principals that read consumer queues, set by RND or registered by you on the connection. The connections that have one are listed, and RND adds them when it builds your private bus.

The gap list

A few things your house can do can't be written in the file yet. They are listed at the top of every export, each with the connections it affects, never dropped silently:

Gap	What RND will need to settle
Client credentials issued by the bus	Credentials belong to the environment that issued them, so sandbox credentials don't work on your private bus. How each connection gets production credentials is to be agreed
Pull API credentials	Consumers that read over HTTPS need production credentials too; how they get them is to be agreed
Per-connection quotas	How your private bus is throttled is to be agreed
One identity provider registered twice with different settings	Which settings apply is to be agreed with both organisations

Your skills in the file

Every active configured instance on your Your house: skills page is in skills, with the values you registered. When a file is loaded, each one is checked the way a registration is: the skill and version must be in the SOM skill library this bus implements, every value must be one of the skill's fields, and the authority scale must cover the authorities the values name. A consumer must be one of the file's consumers.

A configured instance bound to an executor whose connection isn't in the file, because it is revoked or left out, is exported without its consumer and listed at the top of the file, so you can bind it again.

Next

Your private production bus is next in line, not available yet. How going live works, how each connection gets production credentials, and what the agreement covering your private bus says are still to be agreed. Ask RND when your house is ready.