ResearchPublicationsDataPeopleInstituteSupport
CL-WP-005 / WORKING METHODS PAPER / v0.9

The Physical Cost of Useful AI Work.

Task-normalized energy accounting for multi-step and agentic AI workflows.

Abstract. Invocation-level metrics such as joules per token and joules per response are useful for serving diagnostics, but they can misstate the physical cost of completing a user-valued task when workflows include retries, tool calls, long context, validation and failure recovery. CL-WP-005 defines a quality-gated accounting method in which all measured attempt energy is retained and normalized to accepted task outcomes. This release establishes the method, measurement boundaries, open evidence synthesis, benchmark schema and reproducibility assets. It does not claim a completed Critical Load primary GPU/node benchmark.

Research thesis
The reporting unit should move from the machine output to the quality-accepted task the user actually values.

Measure energy against work that actually clears the quality gate.

CL-WP-005 defines Energy per Accepted Task (EAT) as the primary reporting unit for multi-step AI workflows. Failed attempts and retries remain in the numerator rather than disappearing from the accounting boundary.

EATPRIMARY UNIT

Total measured energy across attempts divided by accepted tasks.

RetryVISIBLE COST

Energy consumed after first attempts is separately reported.

B0-B3BOUNDARIES

GPU, CPU+GPU, node and facility are never silently mixed.

ParetoDECISION VIEW

Quality, energy and latency remain visible rather than collapsed into one score.

Critical Load contributionThe method joins a physical measurement record to an application-level acceptance record, so an apparently low-energy workflow cannot be called efficient if it repeatedly fails the task.

Open measurements establish the physical layer; the Critical Load contribution is the accounting and release discipline.

The release builds on peer-reviewed and open measurement work while keeping every external result labelled as external evidence.

EvidenceWhat it establishesRole in CL-WP-005
TokenPowerBench / AAAI 2026GPU/node/system measurement framework and public inference recordsPhysical measurement foundation + worked open record
ML.ENERGY v346 models · 7 tasks · 1,858 configurations on H100/B200Shows task/configuration dependence of inference energy
A-LEMS / 2026 preprintEnergy per Successful Goal and orchestration-overhead accountingGoal-level evidence; prevents false novelty claims
Sustainable Web Agents / AAAI 2026Higher energy does not necessarily imply better task performanceMotivates explicit quality-energy comparison
NVIDIA NVML / AIPerfCumulative GPU energy counters and telemetry collectionPrimary campaign implementation path

External evidence is not relabelled as a Critical Load measurement. The machine-readable evidence register records source, date, evidence class, key fact, URL and Critical Load use.

Quality gates come before energy comparison.

A task is frozen before measurement: input, acceptance rule, scoring method and maximum-attempt policy are declared in advance.

Primary reporting unitEAT = Σ measured attempt energy / accepted tasks

Failures and retries stay inside the energy numerator. Unaccepted tasks are not treated as delivered useful work.

01

Freeze

Lock task inputs, acceptance criteria, model/runtime and retry policy.

02

Measure

Record cumulative energy deltas and diagnostic telemetry for every attempt.

03

Score

Apply the predeclared quality rule without changing the threshold after results are seen.

04

Aggregate

Include failed attempts, retries, tool use, latency and accepted outcomes.

05

Compare

Report the quality-energy-latency frontier and matched orchestration baseline.

Companion metricsAttempt success rate · Retry energy share · Orchestration Overhead Index · Energy/response · Energy/token · Latency · Tool-call count.

A GPU measurement cannot be silently promoted into node or facility energy.

BoundaryMeasured scopeUse
B0GPU only · cumulative energy counter or integrated powerAccelerator-attributable comparisons on the same platform
B1CPU + GPU · component energy measured separatelyHost-aware workload comparison
B2Full node · PDU/BMC/node meterPreferred operational deployment comparison
B3Facility · metered and explicitly allocatedFacility-level planning when the wider boundary is actually measured
Boundary rule. Multiplying GPU energy by an assumed PUE may be useful as a modelled scenario, but it is not a measured B3 result and must never be presented as one.

The method is usable now, even before the first Critical Load primary leaderboard exists.

Suitable forBenchmark and engineering decisions

Benchmark design, model/workflow routing, reasoning-policy tests, engineering regression, procurement measurement requirements and energy-aware capacity planning.

Not yet suitable forCritical Load empirical rankings

Universal model rankings, universal agent-efficiency claims, facility-energy claims without facility measurement, or statements that Critical Load has completed its own primary benchmark campaign.

Decision principlePrefer the workflow that reaches the required quality with the best transparent energy/latency trade-off under the declared measurement boundary—not the workflow with the smallest invocation-level number.

What is published now—and what remains for v1.0.

Published

Research question, UAWM method, evidence synthesis, boundary taxonomy, task/run schemas, executable measurement wrapper, metric code, validation logic and open release package.

Pending

Critical Load-owned repeated GPU/node telemetry, statistical uncertainty from the primary campaign, scoring audit on complex tasks and independent systems/energy + task-domain review.

The publication class is therefore Working Methods Paper v0.9. The pending empirical campaign is a visible release gate, not an omitted limitation.

Cite the method at the strength it actually supports.

Critical Load Research Group (2026). The Physical Cost of Useful AI Work: Task-normalized energy accounting for multi-step and agentic AI workflows. CL-WP-005 / R01 / R03 / CL-P01. Working Methods Paper v0.9, 19 September 2026. DOI pending.

The external measurement foundation remains directly traceable.

The web summary does not replace the evidence register. Core references are linked below; the downloadable CSV records evidence class, key fact, source date and intended use.

SourceRoleOpen
TokenPowerBench · AAAI 2026GPU/node/system measurement foundationPaper ↗
ML.ENERGY Leaderboard v3.0Large inference-energy benchmark landscapeSource ↗
A-LEMS · Energy per Successful GoalGoal-level energy and orchestration evidencePreprint ↗
Promoting Sustainable Web Agents · AAAI 2026Energy-quality evidence for agentic workflowsPaper ↗
NVIDIA AIPerf telemetryImplementation reference for GPU telemetryDocs ↗
CL-WP-005 evidence registerMachine-readable source trailCSV →