- Ship Condition
- Green
- Engineering Online
- Canvas 2D static instruments
- Current Sprint
- Bridge Station Mk V
- Commander Status
- At station
- Shared Fleet State
- Awaiting Fleet Motion
- Data Source
- Awaiting Fleet Motion
- Command Authority
- Awaiting Fleet Motion
- Fleet Position
- No state observed
- Route
- No route observed
- Observed Contacts
- No contacts observed
- Selected Vessel
- No selection observed
- Active Station
- Live Console
- Last Commit
- Runtime static build
Bridge Station composes live instruments without replacing them. Fleet Motion and Periscope run side by side in the Live Console, and a selection change in either instrument pulses the other via Fleet Motion's browser-local canonical state. Radio Console runs alongside them for ambience — it shares the panel, not the fleet-state contract; it has no read or write path into Fleet Motion's canonical state. It does have its own independent, optional FleetCore connection (event-driven chatter instead of scripted, when Bridge itself is loaded with ?live=1) — a separate channel to the same server, not a path through Fleet Motion's state. Selecting a contact from the roster above writes into that same shared state, the same additive path Periscope's own contact selection already uses — Bridge still never mutates anything beyond selection.selectedShipId. Command authority itself is granted by the server per-connection, the same for everyone — there is no token field or URL param controlling it anymore.