Domain-adapter fabric

Replace the domain, not the room.

This is not a flight visualization. It is a domain-adapter protocol. The source domain is swapped three times — SERPRadio, NPS Sounds, and EventOps — and each becomes one governed VIBEnet signal. The ambient audio you hear and the field you see are the same renderer; only the experience profile’s grammar changes. SERPRadio is simply Adapter A: the source domain can be replaced without rebuilding the room.

Direct answer

What does this prove?

One event in, many truthful renderers out. A versioned domain adapter interprets raw operational facts — fares, weather, audio headroom, network health, safety posture — into a single governed signal. The room renders that signal as audio, projection, architectural light, or show-control cues without any consuming system inventing what the data means.

governed signals from the domain-adapter engine

SERPRadio

mobility intelligence · Adapter A

NPS Sounds

environmental intelligence · Adapter B

EventOps

live-event intelligence · Adapter C

serpradio-route-state@0.2.0 · directional grid and route vectors
nominal
route.nominal
hue 54° · intensity 0.524 · pulse 0.200
Raw observation
serpradio · route:JFK-MIA — source=hold · rendered=hold · publishable · pct 55
Domain adapter
Governed signal
nominal
Valence0.450
Energy0.440
Tension0.200
Experience
domain_mode 0 · directional grid and route vectors
Renderers
MadMapper · 7 OSC msgsArt-Net DMX [134, 0, 160, 170]QLab · /cue/VN-NOMINAL/start