Evidence & data system
The data model preserves the chain from physical observation and manufacturing evidence to lifecycle compute carbon and Critical Load.
Useful-work energy accounting is released as a method before it becomes a leaderboard.
The public package contains the paper, benchmark protocol, frozen-task schema, attempt-level run schema, measurement wrapper, metric calculator, evidence register, method note, release review and integrity manifest. Primary Critical Load telemetry remains an explicit future release gate.
The paper is only one layer of the release.
CL-WP-004 is accompanied by a transparent model, machine-readable source register, scenario outputs, method specification, reproduction code and release-integrity manifest. These assets support inspection and recomputation of the published screening results.
Three records keep measurement, context and decision separate.
Evidence record
Telemetry, manufacturing inventory, reported usage, model coefficient or environmental context with source, time, location and uncertainty.
Assessment record
Place baseline, scenario impacts, lifecycle intensity and constraint calculation for a defined site, region and workload boundary.
Decision record
Selected optimization option plus rejected alternatives and the constraints that governed the choice.
A result is reproducible only when its boundary is explicit.
| Field | Purpose |
|---|---|
| Place boundary | Site, grid zone, watershed and administrative region |
| Time boundary | Observation, manufacturing and validity interval |
| Compute unit | MW, GPU-hour, job, request, token or useful-compute denominator |
| Lifecycle boundary | Included semiconductor, hardware, facility, operation and EOL stages |
| Evidence class | Measured, reported, modelled, contextual or derived |
| Method version | Calculation, allocation and coefficient release |
| Uncertainty | Confidence, error and missing-data state |
One compute-carbon result carries the entire upstream evidence chain.
The lifecycle record does not collapse manufacturing and operation into one unexplained number.
| Record group | Representative fields | Evidence rule |
|---|---|---|
| Semiconductor | Fab, node, gases, abatement, wafer, yield, package, HBM | Carry CL-SCM method and primary/secondary evidence state |
| Hardware | Accelerator, board, server, rack, lifetime, utilization | Declare product boundary and useful-compute allocation |
| Facility embodied | Building, UPS, transformer, switchgear, battery, cooling plant | Declare service life, capacity and workload share |
| Electricity | IT kWh, facility kWh, PUE or bottom-up overhead, grid factor | Keep location-based, procurement-based and lifecycle factors distinct |
| Cooling | Cooling electricity, refrigerant type/leakage, equipment embodied carbon | Record whether energy is already captured by PUE |
| Shared services | Network GB, storage GB-hour, service allocation | Version model coefficients and service boundary |
| Lifecycle result | kgCO₂e/GPU-hour, kgCO₂e/job, gCO₂e/1k tokens or useful compute | Carry every upstream evidence ID and allocation rule |
Manufacturing evidence keeps its own high-resolution schema.
The semiconductor record preserves the variables that determine whether a chip-carbon result can actually be reproduced.
| Field group | Representative fields | Why it matters |
|---|---|---|
| Fab identity | Fab location, reporting period, process node, wafer diameter | Sets electricity, technology and manufacturing boundary |
| Process inventory | Electricity, process gases, abatement, chemicals, UPW | Captures direct and energy-related manufacturing impact |
| Yield allocation | Wafer starts, die area, gross dies, good-die yield | Determines embodied impact per usable die |
| Packaging | Substrate, backend process, HBM / memory, package type | Adds post-fab manufacturing impact |
| Evidence quality | Primary / secondary, confidentiality, uncertainty, source date | Prevents confidential gaps from disappearing into a single factor |
| Method record | Allocation rule, method version, evidence IDs | Allows the final lifecycle result to be challenged and reproduced |
Open what exists; label what does not.
The working release can export the research registry and schema. A public source-data repository and code repository are not yet claimed as released.
Working publication IDs, versions, types, status and programme links.
Working CL-E / CL-A / CL-D field structure. This is a specification, not a research dataset.
Source-level licensing, provenance and place evidence will be released after evidence lock.
No public code repository is claimed in this working release.