Infrastructure

Fleet

Four surfaces. One witnessed snapshot.

Four nodes answer one HTTP control plane — three on a Thunderbolt star, one at the edge. This page never reaches them. It reads the one snapshot the fleet publishes, co-signed by an independent 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.

Snapshot — witnessed fleet status checking…

surfaces
snapshot pulse
snapshot age
witness pk_fp
witnessed

The hub publishes this snapshot; an independent edge node signs its digest against the beacon chain. The cards below render that record — nothing here probes a machine directly.

Nodes

Who’s on the mesh.

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.

Hub · Orchestrator

Node 01

Apple silicon · desktop class

Primary inference, compilation, and orchestration. Runs the entropy beacon and the self-healer.

checking…
Reasoning

Node 02

Apple silicon · workstation class

Large-model reasoning. Dedicated Thunderbolt link to the hub, measured at 9.16 Gb/s.

checking…
Orchestrator

Node 03

Apple silicon · laptop class

Spoke on the Thunderbolt star. Hits the fleet HTTP surface over the mesh.

checking…
Control plane

Node 04

ARM64 Linux · SBC class

Edge observatory. Fleet control-plane node. Reachable over the private mesh.

checking…
Topology

Star, not triangle.

The hub carries the routing; the reasoning and laptop nodes are spokes. 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.

9.16
Gb/s hub ↔ reasoning
0.42
ms RTT
0.33
Gb/s hub ↔ laptop
90 s
Self-healer tick
Control plane

One HTTP surface.

Every node answers the same small HTTP surface: report health, run a whitelisted command, queue an async job — pure Rail on three of the four. 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.