What limits an AI hall, stage by stage

Binding stage after the plan for the alternative shown: Firm supply (grid import).

• Model accuracy against instrumented sites has not been established: 0 reconciled observations across 0 sites, covering 0 of 20 model outputs. Every figure in this report is modelled. The uncertainty ranges shown come from input uncertainty propagated through the model, not from the difference between this engine's predictions and site data — no such difference has been recorded yet.
• Synthetic hall: every input is invented for demonstration. It is not a customer, a company or a site, and nothing in it has been measured.
• The calibration ledger is empty: nothing in this scenario is measured or calibrated. Model accuracy against instrumented sites has not been established: 0 reconciled observations across 0 sites, covering 0 of 20 model outputs. Every figure in this report is modelled. The uncertainty ranges shown come from input uncertainty propagated through the model, not from the difference between this engine's predictions and site data — no such difference has been recorded yet.
• The engine labels any input an intake supplies as supplied by the client (class E5); in this synthetic hall that label describes how the engine treats an input, not a measurement.
• At least one date rests on an assumed lead time (E0). Treat this comparison as indicative: it shows which inputs decide the answer, not a commitment to any date.
• Grid reinforcement is not dated here: a connection date needs the network operator's offer.
• the capex total is a LOWER BOUND: no price exists for CDU commissioning and flushing (4 x unit, needed in 2 places); CDU hydraulic integration and controls (4 x unit, needed in 2 places)
• the weakest priced line is class E0, below E3: a decision needs every priced line at an engineering estimate or better
• the capex total inherits class E0 from its inputs, below E3
• 8 of 8 priced lines are library placeholders, not prices
• the grid electricity price is a placeholder (140 EUR/MWh), not the site's tariff
• A capex that is not complete, or that lists unpriced components, is a lower bound, not a complete price.
• The power path and the constraints are shown for the headline outcome (Hybrid DLC on retained plant, grid only); other architectures are compared under outcomes. Stage capacities are as found: the plan's reliefs raise several of them, so a stage's load after the plan may exceed its as-found capacity.
• Loads: the engine charges the existing site peak to the utility connection and transformers, the existing IT load to the UPS and the chilled-water plant, and only the new IT load to the busway; it models no switchgear. A null load is a load the engine does not charge to that stage.
• A constraint with no racks-allowed figure passes: the engine reports no finite limit for it in this architecture, so it does not limit the hall. How well supported that is shows in its evidence class, not in the figure being absent.
• Tied as found: Residual air load removal per rack also allows 0 racks. The engine names the first constraint in its fixed order as binding (Rack feed / tap-off rating), so relieving that one alone may not unlock racks.
• No outcome here is dated: weeks to capacity are given only when every lead time behind them is above class E0, and none is.
• The existing-racks row is the occupied positions at the hall's design density, a design value. The current IT load is a separate invented input: occupied positions multiplied by design density is not claimed to equal it, and the engine uses the two independently (the current IT load is charged to the UPS and the chilled-water plant).
• Capex pricing: Full DLC plus behind-the-meter supply rest partly on a supplied figure and partly on library placeholders. Hybrid DLC on retained plant, grid only; Full DLC, grid only rest entirely on library placeholders (not prices). An outcome with no racks has no capex figure.
• Every hall shown is invented for demonstration. No customer data is used.

Engine 0.9.0 (code digest 7e62aeae1056). Scenario data generated 2026-09-14 00:00 UTC; it is computed at build time and changes only when the engine does.