Control centre
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
What is on the page
| zone | shows | rule |
|---|---|---|
| map | every node on its network band, its uplink, the site server, the listeners; alive / grey / no agent | from the network watch and the inventory, never hand drawn |
| arcs | contracts as they happen, in their colour, through the uplink that carried them, landing on the apps that hear | from the bus event stream; the publisher, every node that hears it back and the listener flash the colour |
| chips | one per contract value seen (person-in-scene, suitcase, …) with its count | click to hide or show that contract on the map and in the ledger |
| ledger | attention opened and closed, HEARD pairs, MOVED network, grey and back | one list, newest first, filter by node; click a line for its images, crops and masks |
| strip | the attention crops as they come, the contract colour as the tag; or the camera pictures | newest left, scrollable, click a card for its evidence |
| drawer | the 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 point | opened on click, never a nav item |
| top line | nodes up / total, uplinks up, messages per minute, open attention | the four numbers that say if the kit is healthy |
How a contract travels
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
| contract | path: network → uplink | rule latency p50 / p90 s | bus transport p50 / p90 ms | heard Δ p50 s |
|---|---|---|---|---|
| person-in-scene | hq-lan → hq-fibre (6 cameras) | 1.64 / 3.51 | 6 / 21 | 28 |
| person-in-scene | aerial → phone | 1.90 / 2.09 | 4 / 7 | 30 |
| object-seen=suitcase | aerial → phone | 2.60 / 3.32 | 27 / 78 | 30 |
| object-seen=suitcase | camera port → starlink-site | – | 40 / 40 | 4.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).