This is what a month looks like
when every number carries a proof.

One complete month of a synthetic 21 MW fleet — never a real, named operation. Every diagnosis-grade number below is certified and checkable in a spreadsheet. It's stamped expired on purpose: a certificate speaks only for the fleet and date on its face, and this one's date has passed. Yours is computed from your fleet file — and only the current one matters.

Get your month — one file See how you check it →

The month, at a glance

Daily energized footprint vs. provable minimum.

Weekly aggregates below; the full daily series is in the downloadable pack. Every figure is a certified aggregate — no unit-level data, no machine lists.

Synthetic 21 MW fleet · June 2025 · MW, aggregate per week · EXPIRED
Week	Avg energized	Provable minimum	Certified excess	At $50/MWh (input)
Jun 1–7	23.8 MW	22.0 MW	1.8 MW	≈ $15,120
Jun 8–14	24.0 MW	22.0 MW	2.0 MW	≈ $16,800
Jun 15–21	23.9 MW	22.0 MW	1.9 MW	≈ $15,960
Jun 22–30	23.7 MW	22.0 MW	1.7 MW	≈ $18,360
Month	23.85 MW	22.0 MW	1.85 MW avg	≈ $66,240

Utilization band for the month: 91.8%–92.5% of energized capacity. Every provable-minimum figure carries its own witness in the pack.

One curtailment event · costed

June 18 — a 4 MW grid call.

synthetic · expired

shed target (program call)4.0 MW

certified minimal hashrate lost136,448 TH for the event window

rule-of-thumb comparison (block shed)≈ 221,000 TH — would have lost more

must-runs honoredyes · contract-backing set intact

# instance c4e087 · event 2025-06-18 · aggregate figures only, no machine list # certificate: shed target met · hashrate loss provably minimal · gap=0 · signed

The shed list itself — which specific machines — is a paid deliverable and never appears in a public specimen. What's public is the certified cost: how little you had to lose.

One maintenance wave · costed

Mid-month firmware rollout, under the floor.

synthetic · expired

machines to update512

certified waves (never breaching the hashrate floor)3 waves

largest wave≤ 182 machines

hashrate floor held throughoutyes · 0 breaches

# instance m2a1f9 · counts only, no sequence, no restart order # certificate: floor never breached · wave sizes provably minimal in count · signed

Counts and the proof they stay under your floor — public. The order machines come down and back up is a paid sequence, never shown here.

Take the whole month

The specimen pack — four formats, all aggregate.

The full daily series and every certificate and witness, in the format you like. The XLSX is formula-live so you can watch the aggregate numbers re-derive — aggregate only, per doctrine.

PDF Formula-live XLSX CSV JSON Coming soon

The downloadable pack is coming soon — aggregate-only, expired-stamped, every number with its certificate.

Synthetic fleet, expired month, public demonstration. Your month is computed from your fleet file — and only the current one matters. Every artifact carries this line and its expired stamp. Only lines marked CERTIFIED are warranted, and they are warranted completely; any aggregate shown for context is labeled as such.

This is what a month looks like when every number carries a proof. Yours takes one file.

Send your fleet mix — free audit See the full Fleet Book →

This is what a month looks likewhen every number carries a proof.

Daily energized footprint vs. provable minimum.

June 18 — a 4 MW grid call.

Mid-month firmware rollout, under the floor.

The specimen pack — four formats, all aggregate.

This is what a month looks like
when every number carries a proof.