Scale and Availability Caveats
A design point at one machine is not a fleet, and a peak performance is not an availability; Kronos keeps these caveats attached to its numbers.
Two caveats that change everything
Two honest caveats sit behind almost every performance number. Scale: a result for one machine does not automatically hold for a fleet, and a fleet raises questions a single unit does not. Availability: a peak or design-point performance is not the same as sustained, high-duty-cycle operation over years. Kronos keeps both caveats attached.
The scale caveat
- A single FOAK breeder is a proof of principle, not a supply chain
- Fleet-level outputs assume repeated builds that have not happened
- A comparison between our single machine and a rival fleet is not like-for-like
The availability caveat
- A design point describes performance under design conditions, not annual average
- Duty cycle and availability are genuinely open — a top open question for the breeder
- A capacity figure is not an energy-delivered figure without availability
These caveats are unglamorous and they are where optimistic projections most often quietly go wrong — by treating a peak as an average, or one machine as many. We state them so a reader does not have to supply them, and so our own numbers stay honest about what they describe.