Three surfaces. One witnessed snapshot.
Three nodes answer one HTTP control plane: two on a Thunderbolt link, one at the edge. This page never reaches them. It reads the one snapshot the fleet publishes, signed by the Pi witness at a pulse, and tells you exactly how old that record is. A chip only earns a state after this page has read a fresh snapshot; what can’t be checked from the public edge stays hollow.
…The hub publishes this snapshot; the edge node (the Pi witness, which Ledatic also runs) signs its digest against the beacon chain. The cards below render that record — nothing here probes a machine directly.
Each chip is the witnessed snapshot’s word, anchored to the pulse it was signed at — not a direct probe. A surface that didn’t answer when the snapshot was taken says so. A snapshot that has aged past its budget stops claiming anything except its own age.
Apple silicon · desktop class
Primary inference, compilation, and orchestration. Runs the entropy beacon and the self-healer.
checking…Apple silicon · laptop class
The other end of the Thunderbolt link. Hits the fleet HTTP surface over the mesh.
checking…ARM64 Linux · SBC class
Edge observatory. Fleet control-plane node. Reachable over the private mesh.
checking…The hub carries the routing; the laptop is the spoke on Thunderbolt, and the Pi sits at the edge on Wi-Fi. A triangle topology was tried and failed: L2 loops on the bridge caused ARP to break silently across the fabric. Star-only from then on.
Every node answers the same small HTTP surface: report health, run a whitelisted command, queue an async job — pure Rail on both Macs. No tmux. No ssh fan-out. Shared state is file-based, so a binary swap is a drop-in upgrade.
That surface is private. From the public edge, the witnessed snapshot at the top of this page is exactly what can be checked — so that is all this page claims.