Three machines measured. Three partly measured. Three taken on trust.
Nine pieces of owned equipment, one hosted twin, and a nervous system that mostly doesn't exist yet. Every number carries the evidence label it earned — nothing gets upgraded to fact by repetition.
Where work belongs — not a claim that every link is deployed. Touch any node to read its record.
Filter by how much of each row was actually measured.
Immutable bytes get one identity. Nearest verified copy wins.
Six places where the record disagrees with itself. They stay visible on purpose.
Not one filesystem. The distinction is the whole design.
Share names, artifacts, leases, and receipts. Execute repositories and hot working state from each host's local NVMe, RAM, or VRAM.
Git owns complete commits. Builds run from local checkouts, so a job names repo@commit, never a pathname. That ends cwd roulette without dragging development onto a network share.
Immutable bytes are addressed by SHA-256, stored durably once on the NAS, and cached anywhere they're useful. Models, binaries, replay films, datasets, checkpoints, releases.
Placement follows compatibility and data locality before benchmark vanity. If the 500 GB movie already sits on the forge node, move the job — not the movie.
Leases stop two workers from grabbing one resource. They grant no trading, capital, cognition, Court, or R authority. Ever.
Build and runtime identities, not an assertion of owned hardware.
| Runtime ID | Access | Function | Hardware evidence |
|---|---|---|---|
| node-control | local | Cockpit and controller | Owned equipment record |
| node-court | internal | Clean court | Owned equipment record |
| node-forge | internal | Cognition lab / build furnace | Owned equipment record |
| node-body | internal | Live body | Owned equipment record |
| node-foundry | internal | WSL build / GPU node | Owned equipment record |
| node-twin | hosted | Production twin | Live 2026-08-08 — hosted Ubuntu, 8 logical CPUs, ~24.6 GB RAM, 500 GB virtual disk, no NVIDIA GPU |
PROBAGI / SOURCE PROOF
Three machines — the forge node, the body node and the archive array — report CPU, memory, GPU and storage from a live probe dated 2026-08-08. The hosted production twin is separately live as of the same date.
fleet-live-probe-2026-08-08
The control, court and foundry nodes have core hardware measured live but each carries at least one operator-supplied or unreconciled figure: a GPU core count, a Thunderbolt volume that did not appear to the storage probe, and a WSL memory cap standing against a larger reported physical kit.
fleet-mixed-measurement-2026-08-08
Three nodes — compatibility, UI and portable — are recorded from dated operator statements on 2026-08-06 and have not been live-probed. They are labelled OPERATOR in the document and are not upgraded to measured fact.
fleet-operator-reported-2026-08-06
The document keeps places where the record disagrees with itself visible rather than silently picking a winner, including a usable-memory shortfall on the compatibility node and an unproven memory-timing claim on the UI node.
fleet-open-contradictions-2026-08-08
The four laws describe intended source, artifact, compute-placement and lease behaviour. The document states plainly that the nervous system connecting these nodes mostly does not exist yet; no claim is made that every link is deployed.
fleet-namespace-laws-design
Machine names, runtime IDs, LAN aliases, mount paths and external drive names were replaced with role labels by a checked transform that asserts zero surviving identifying tokens in both the artifact and this proof rail. Hardware models, byte counts, dates and evidence labels are unchanged from the measured source.
fleet-sanitization-2026-08-13