GUIDE 02 / FLEET ROLLOUT

Roll out across a fleet

From a pilot cohort to thousands of machines: baseline first, observable waves after, stop gates between them and a named owner for the rollback.

Stage 01 · Baseline

1. Record what you haveExport the current hashrate, power draw, temperature bands and error rates per worker. This is what you will compare against - without it every later number is an opinion
2. Fix the site limitsAmbient temperature, breaker headroom, generator ceiling if you have one. These decide which profile you are allowed to use
3. Name the rollback ownerOne person, by name, who can decide to stop and revert without a meeting

Stage 02 · Pilot cohort

1. Pick 1-5 machinesSame model, same board, same rack position type as the bulk of the fleet
2. Install through the toolkitGroup scan, select the cohort, install firmware, confirm
3. Run 24-48 hours untouchedLonger if you have day/night ambient swings
4. Compare against the baselineAccepted hashrate, J/TH, chip temperature spread, rejected shares, fan duty. Any of these going the wrong way is a stop

Stage 03 · Observable waves

1. Wave one: 10-20% of the fleetOnly what survived the pilot, same settings, same file
2. Hold the gateWatch a full day. Fleet aggregate and worst-worker both have to stay inside the band you accepted
3. Scale the waveDouble it while the numbers hold. Stop and revert the moment they do not
4. Keep one control layerCentral monitoring, one decision gate per wave, one owner. Not a spreadsheet per shift