Control centre

one page · the live network map · the contracts on it · the greys explained · the attention crops · built 2026-10-03

Forty pages became one. The site server serves a single screen that answers the four questions an operator has: which node is on which network and is it alive, which contracts are moving between nodes and how late, what the cameras see, and when something is grey, why and what to do, right where it sits. Everything deeper opens in a drawer on click; nothing is a destination of its own any more.

Open it

The control centreOn the tailnet, from any network you stand on: HQ, the site, the pickup, a hotspot. Sign in to Tailscale on the phone or the laptop and open it.http://100.123.255.51:8900/
NetworksWho is on which network, how, through which uplink, the transfers./networks on this site · live
The classic navigationThe forty pages, kept until the one page has proven itself.…:8900/classic
The twinEvery attention raised by a rig lands on the twin as a pin in its contract colour, with the crop in the popup.twin.regista.ai

What is on the page

zoneshowsrule
mapevery node on its network band, its uplink, the site server, the listeners; alive / grey / no agentfrom the network watch and the inventory, never hand drawn
arcscontracts as they happen, in their colour, through the uplink that carried them, landing on the apps that hearfrom the bus event stream; the publisher, every node that hears it back and the listener flash the colour
chipsone per contract value seen (person-in-scene, suitcase, …) with its countclick to hide or show that contract on the map and in the ledger
ledgerattention opened and closed, HEARD pairs, MOVED network, grey and backone list, newest first, filter by node; click a line for its images, crops and masks
stripthe attention crops as they come, the contract colour as the tag; or the camera picturesnewest left, scrollable, click a card for its evidence
drawerthe node's own page, its why and what to do, its latency tables; or a message's evidence: the live view, the pipeline strip, the crops, the position, the twin at that pointopened on click, never a nav item
top linenodes up / total, uplinks up, messages per minute, open attentionthe four numbers that say if the kit is healthy

How a contract travels

camera→rig (RVC2 bridge · OAK4 probe app · host stack)→ attention row →bus (site server)→shell: HEARD · listeners · latency→control centreandmission desk→ crop filed →pool→twin pin

Every rig that subscribes says what it listens to in its hello row; the map draws one box per listener and lands the arc on the ones whose filters match. Every attention carries the publisher's position at that instant (its own GPS, or its host's); the mission desk fetches the crop through the control centre, files it in the pool's dataset layout, and the twin draws the pin.

First numbers · 2026-10-03

contractpath: network → uplinkrule latency p50 / p90 sbus transport p50 / p90 msheard Δ p50 s
person-in-scenehq-lan → hq-fibre (6 cameras)1.64 / 3.516 / 2128
person-in-sceneaerial → phone1.90 / 2.094 / 730
object-seen=suitcaseaerial → phone2.60 / 3.3227 / 7830
object-seen=suitcasecamera port → starlink-site–40 / 404.8

Rule latency is first-seen to raised on the device; transport is envelope time to the shell's clock (clock skew included; the server's own condition rows show 0.9 s of it); heard Δ is another asset of the site raising within the window. The tool: mos-edge-fixed/bin/mos-contract-latency.py. The second run of the suitcase journey measures every hop with the rig moving between networks.

Where it is written

mos-edge-fixed · mos_fixed/center.html, control.py (the watch, the proxy to the shell), deploy/netwatch/ (the agent), deploy/oak/mos-oak-bridge.py (the RVC2 surface) · host-mode · pipeline/host/tools/bus_live.py (the shell) · dev-setup · bin/mos-mission-desk.py, contracts/event/machine-message.md (hello.listens) · mm-gis · serving/twin.html (the attention layer).