Supply, allocated, utilized are three different numbers. Most protocols report one and call it capacity. The distance between them is not a hardware problem, it is a coordination problem, and this is a working model of it. Every figure below is computed in your browser by the open-source engine, not read from a slide.
A proof market has a supply of machines. It commits some of that supply to work. Some of what it commits actually runs. Report only the first number and the market looks full. Report all three and the coordination loss becomes visible. The vocabulary here is Fermah's own: Seekers submit Proof Requests, the Matchmaker assigns them to Prover Nodes.
The instrument at the top settles on the horizon average. This plays the same run out over time, for the regime and load you set above. Coordinated runs climb and hold near the top. Operator-gated runs stall below the line and stay there.
These three regimes run over an identical supply. Nothing is added between them. Removing the operator from the critical path and placing work on the guarantee spectrum lifts utilization from the low forties to the low nineties, and the number of proofs produced roughly doubles.
Supply is byte-for-byte identical in all three rows. The only thing that changes is how the market coordinates. That is the whole claim: the ceiling is coordination, not compute.
This is a model, not Fermah's live telemetry. It is small enough to read in one sitting and deterministic, so every figure on this page is reproducible from a seed. The page embeds the exact engine published in the repository, so what you see here is what the code produces.
src/engine.js.Alongside this dispatch I opened a pull request to Fermah's own documentation, filling the empty components diagram in their architecture page with a Seekers, Core and Prover Nodes schematic that matches the workflow their docs describe. Vocabulary on this page was checked against that same documentation.
The simulation is an independent model built by this desk, not published by Fermah and not a source of live network data. It reproduces the coordination dynamics Fermah describes so they can be inspected and driven, and every number is generated in your browser by the embedded engine. Fermah's counters and the 40% figure are theirs; the model is calibrated to sit in that range, not to assert it.