ResearchPublicationsDataPeopleInstituteSupport
CL-MN-001 / METHOD NOTE / v0.5

Critical Load methodology

A place is constrained by the first physical infrastructure limit or environmental budget that reaches its limit.

Power
221 MW
Grid
203 MW
Water
176 MW
Carbon
184 MW
Cooling
194 MW
Land
240+ MW
Environment
189 MW
CL is a binding-limit model. Each constraint is independently estimated, then the minimum defines the available compute capacity for the stated place and time boundary.

Every value carries an evidence class.

ClassMeaningExample
MeasuredDirect physical observationGPU cumulative energy counter
Observed / reportedOperational or provider recordCloud usage, facility PUE
ModelledEstimated using versioned coefficientsInstance energy, facility embodied allocation
ContextualLocation/time environmental factorGrid factor, basin stress
DerivedCritical Load calculation carrying upstream IDslifecycle gCO₂e / GPU-hour, water-limited MW

Observe → contextualize → allocate → constrain → decide.

01

Observe

Physical telemetry, usage, manufacturing and site records.

02

Contextualize

Grid, watershed, climate, procurement and regulatory boundary.

03

Allocate

Move shared manufacturing and infrastructure impact to workload units.

04

Constrain

Estimate supportable compute under each physical or environmental budget.

05

Impact

Compare the place baseline with the proposed compute scenario and preserve the local deltas.

06

Decide

State the supportable envelope, binding limit, project conditions and alternatives.

Carbon starts before the accelerator exists and continues beyond electricity use.

CL-LC defines a compute lifecycle boundary spanning semiconductor manufacturing, hardware integration, facility construction, electricity, cooling, shared services, replacement and end of life.

LayerIncluded carbon sourcesTypical denominator
SemiconductorFab electricity, process gases, abatement, chemicals, UPW, wafer/die yield, packaginggood die / packaged device
HardwareBoards, servers, racks, memory, storage and supporting electronicslifetime useful compute
FacilityBuilding, steel/concrete, UPS, transformers, switchgear, batteries, cooling plantcapacity × time × utilization share
OperationIT electricity, facility overhead, backup generation and location-specific electricity contextworkload energy / GPU-hour / job
CoolingCooling electricity when measured bottom-up, refrigerants, embodied cooling equipmentfacility or workload allocation
Shared servicesNetwork and storage attributable to the compute serviceGB transfer / GB-hour / service share
Replacement / EOLComponent replacement and end-of-life treatment within the declared boundarylifetime useful compute

“Green electricity” is not automatically zero lifecycle carbon.

Critical Load keeps three electricity statements separate: physical location-based electricity, procurement or market-based claims, and lifecycle emissions of the generation assets themselves.

Physical

Location-based

What the local electricity system supplied in the stated time and place boundary.

Contractual

Procurement-based

PPA, certificates and other contractual attributes remain a distinct claim rather than replacing the physical record.

Lifecycle

Generation assets

Manufacturing, construction, maintenance and end-of-life emissions of electricity infrastructure where the study boundary requires them.

Method principleAs operational electricity gets cleaner, upstream semiconductor, hardware and facility carbon can become a larger share of the compute lifecycle result.

Shared infrastructure must be allocated before it can become compute carbon.

SEMICONDUCTOR + HARDWARE

Useful-compute allocation

Lifetime, utilization, GPU-hours, delivered FLOPs or another declared useful-work denominator.

FACILITY

Capacity-time allocation

Facility embodied carbon is assigned by capacity, service life, IT load share and utilization.

NETWORK + STORAGE

Service allocation

Traffic, storage-hours or a documented service allocation connects shared infrastructure to the workload.

Lifecycle compute carbon intensityILC = Csemiconductor + Chardware + Cfacility + Celectricity + Ccooling + Cnetwork/storage + Creplacement/EOL

Each term is first normalized to the same useful-compute denominator and time boundary.

Boundary rules prevent the same carbon from being counted twice.

×2
PUE and bottom-up cooling cannot both claim the same cooling electricity.

If facility electricity is estimated as IT energy × PUE, cooling electricity is already inside the facility total. A bottom-up cooling-energy record replaces that portion; it does not add to it.

×2
Lifecycle electricity factors and generation-infrastructure carbon must share one boundary.

If a lifecycle electricity factor already includes generation-asset construction, those assets are not added again as a separate term.

×2
Product PCFs must disclose whether packaging and memory are already inside the product boundary.

Semiconductor, package and system records are reconciled before aggregation.

CL-SCM carries fab evidence into the lifecycle model.

Fab process inventory → wafer basis → good-die allocation → advanced packaging → product carbon → lifetime useful compute. CL-SCM is the upstream manufacturing method feeding the broader CL-LC lifecycle carbon model.

Carbon-limited loadLcarbon = stated carbon budget / lifecycle compute carbon intensity

Only after the full lifecycle intensity is normalized to the same time and capacity boundary does carbon enter the Critical Load minimum operator.