Measured
Directly observed or recorded evidence tied to a source and time. For CarbonLayer, an/api/inference receipt’s createdAt timestamp and request fields record API activity; they are not an environmental measurement.
CarbonLayer / evidence status
Methodology v1.0 is available as a framework for evidence boundaries and claim classification. Specific coefficients remain under verification. Read the Methodology v1.0 status or jump to the evidence-status glossary.
Framework status
Available framework; coefficients pending final verification.
00
Use these labels to read the evidence behind a claim. Impact classifications remain measured, modeled, estimated, or unavailable; simulated describes prototype behavior and is separate from those impact classifications.
Directly observed or recorded evidence tied to a source and time. For CarbonLayer, an/api/inference receipt’s createdAt timestamp and request fields record API activity; they are not an environmental measurement.
A value derived from assumptions, coefficients, or synthetic inputs rather than a direct observation. CarbonLayer’s seeded regional values passed through its synthetic grid-intensity calculation are modeled inputs, not measured per-inference emissions.
Prototype behavior or output, distinct from impact classifications. POST /api/inference returns a simulated route target and latencyMs; modelProviderCalled: false means no model provider call is made. These latency values are prototype route metadata, not production measurements.
An impact result is withheld when required evidence is missing. CarbonLayer’s per-inference carbon impact is unavailable because serving-energy allocation and a verified emissions factor are absent. Unavailable impact data is not zero.
Reading this record
Direct observation with a stated period and provenance.
A coefficient, assumption, floor, synthetic value, or attribution input.
A calculated result derived from named measured and/or modeled inputs.
Required evidence, a defensible range, or a verified source is missing.
Receipt facts are kept separate from this legend. A real API response does not turn simulated output, route metadata, or an environmental estimate into a measured result. “Simulated” describes prototype behavior; it is not one of the four impact classifications.
01
The Evidence-Based Framework (Pending Final Coefficient Verification) is available as Methodology v1.0. It describes the intended product boundary, evidence requirements, uncertainty treatment, and rules for withholding unsupported outputs.
It is a framework, not an impact result or independent verification. The researcher- reported summary is the current evidence input for this copy update; the full ledger and PDF are absent and the summary has not been independently verified here. No accounting basis is selected, and specific coefficients remain under verification.
Claim rule
02
The scope is operational inference-impact modeling: relating a bounded inference dispatch to the workload and infrastructure evidence needed for an environmental estimate. This page does not certify a facility, model provider, grid mix, product claim, or compliance position.
Real recorded receipt facts
Simulated or unavailable
The system boundary starts at the recorded inference dispatch and ends only when a defensible allocation to energy and environmental factors can be evidenced. Physical routing, provider/model telemetry, facility operation, and the embodied or lifecycle impacts of equipment are not represented when their evidence is absent.
The /api/inference decision receipt is separate from the cost-and-latency Playground. The Playground supports model-based scenarios and an optional direct provider call for one request when configured; it does not route production workloads or provide measured environmental impact.
03
Primary functional unit
One inference dispatch. This is the unit to which request attribution and a future supported allocation would attach.
Activity data
Token counts, input/output workload fields, model identifier, request timestamp, and any supported request metadata describe activity. A token count alone is not an energy value and cannot be converted into one without an approved factor.
Aggregation period
A future report must state the time period, aggregation boundary, inclusion/exclusion rules, and whether a range is per dispatch or time-bounded. No period or aggregation may be inferred from a single receipt.
No token-only inference
04
Inputs are labeled by how they enter the method. A recorded field is not automatically an environmental measurement, and a modeled assumption is not observed data. The register below is the v1.0 evidence contract; missing source URLs and ranges are intentional disclosures, not completed inputs.
Input class
Receipt activity
Source / period
CarbonLayer API receipt
Request timestamp; exact period is receipt-specific
Treatment
Recorded fact; not environmental evidence
Input class
Serving energy
Source / period
Instrumented serving stack or provider telemetry
Not supplied
Treatment
Unavailable until meter/telemetry provenance and allocation are supplied
Input class
Grid/environmental factor
Source / period
Researcher-reported candidate ledger summary; full ledger not supplied
Accounting basis not selected
Treatment
Candidate values use different accounting bases; no grid coefficient is approved or published
Input class
Water factor
Source / period
AWS region-specific operator-reported withdrawal figures (summary only)
Final source and period verification pending
Treatment
Potential direct/evaporative withdrawal layer only; not a per-inference factor
Grid-source metadata is not approval of an environmental factor. Carbon impact remains unavailable until an accounting basis is selected, documented, and verified. The researcher-reported summary says candidate location-based, hourly, marginal-proxy, and lifecycle figures differ; the full ledger is absent, no basis is selected, and no candidate constants are reproduced here.
Water evidence boundary
05
Each input used in a future calculation must be traceable to a source record and to the dispatch or aggregation period it represents. Retrieval time is not the same as observation time. A source can be current in the cache and still be unsuitable for a historical calculation or an approved environmental factor.
Observation period
When the underlying electricity, meter, workload, or water observation occurred. It must match the dispatch or reporting period; a retrieval timestamp cannot fill in a missing observation period.
Retrieval time
When CarbonLayer obtained a record, kept distinct from its observation time and from a reproducible source identifier.
Validity treatment
The applicable freshness window, expiry behavior, stale-data handling, and why an input is accepted or withheld for the stated period and boundary.
The current /api/grid-intensity contract exposes these separate fields:source category, fetchedAt, and expiresAt. Its cache window is five minutes and expired cache rows are discarded. These timestamps describe retrieval and cache validity, not the grid observation period. The contract has no observation-period or source-record identifier, and marks the response simulatedwith impactDataStatus: unavailable. A recent lookup therefore does not establish provenance or a measured environmental impact.
Classification and missing inputs
Modeled floor and reproducibility
Source URLs not supplied
06
Methodology v1.0 makes the evidence framework available. The stages below identify the evidence required for an impact result; they are not a verified set of coefficients or a claim that the missing ledger selected an accounting basis. Each impact-producing stage remains unavailable until its inputs and allocation are documented and verified.
07
The researcher-reported summary describes materially different carbon candidates by accounting basis, but the complete ledger and source PDF are absent. No basis has been selected or independently verified here, so candidate constants are omitted. The ledger also does not establish an inference-to-kWh conversion.
Grid accounting basis
unavailableNot selected
Energy per inference
unavailableUnavailable
Carbon per inference
unavailableUnavailable
Water per inference
unavailableUnavailable
Direct / evaporative withdrawal layer
unavailablePotential; pending verification
Indirect watershed impact
unavailableUnavailable; no proxy
Baseline / savings
unavailableUnavailable
Receipt fields
Request facts recorded separately
Carbon remains unavailable until the accounting basis is selected, documented, and verified. Water estimates remain unavailable until a defensible layer and allocation are verified. No environmental saving or combined receipt is implied.
07A
Hypothetical example only
Every date, count, label, and latency value below is illustrative. It is not production evidence, proof of provider activity or physical routing, a measured latency result, or measured environmental impact.
Suppose a project selects February 3 through February 4, 2026, UTC. The through date is included in full, and the following midnight is the exclusive end. That makes the selected interval [2026-02-03T00:00:00Z, 2026-02-05T00:00:00Z), exactly 48 hours. The immediately preceding equal-duration interval is [2026-02-01T00:00:00Z, 2026-02-03T00:00:00Z), also 48 hours. The prior period ends exactly where the selected period starts, so the intervals are contiguous and do not overlap. Each interval includes its start and excludes its end.
Selected period · hypothetical
Feb 3–4, 2026 UTC
[2026-02-03T00:00:00Z, 2026-02-05T00:00:00Z)
48 hours
Immediately preceding period · hypothetical
Feb 1–2, 2026 UTC
[2026-02-01T00:00:00Z, 2026-02-03T00:00:00Z)
48 hours
For any supported measure, change means selected period minus previous period. For example, two selected-period records minus two previous-period records equals a change of zero. A change is available only when both periods contain records and the values needed for that measure are valid. If either period has no records, changes are withheld; missing or invalid values also leave the affected measure unavailable.
Read counts as simulated record metadata
Missing and invalid fields remain visible as data-quality warnings
These values are unavailable for both periods and their changes. Unavailable does not mean zero.
No environmental amounts or deltas are calculated or implied here. Missing environmental evidence does not become an impact result.
08
Uncertainty comes from serving energy, workload allocation, provider/model telemetry, physical routing, facility overhead, grid factors, water factors, observation periods, and the quality or staleness of each source. A future release must show input ranges or scenarios, the propagation method, the resulting output range, and which assumptions remain modeled.
Missing is unavailable, not zero
Point-value and netting rule
Measured
Direct observation with stated period, provenance, and an operating/instrumented serving stack or external source.
Modeled
Seeded coefficient, assumption, floor, synthetic grid value, or modeled attribution input.
Estimated
A calculated environmental output from named measured and/or modeled inputs, with its range and assumptions shown.
Unavailable
A required factor, range, source, boundary, or verification record is absent or cannot be defensibly formed.
09
Before evaluating workload-simulator inputs, provide baseline evidence for latency, cost, carbon, and water. Supply the source, scope, and period for each baseline; do not treat simulator targets or illustrative values as observations.
Provide representative measured observations for the workload and measurement point, with the aggregation period and latency distribution used. Keep simulated route targets labeled as modeled.
Provide applicable provider/model pricing or billed-cost records, rate version, units, workload assumptions, and period. Distinguish invoice evidence from modeled prices.
Provide the selected accounting basis, energy allocation evidence, factor source and version, location and time coverage, units, and formula. CarbonLayer currently publishes no per-inference carbon baseline or impact.
Provide the water boundary and layer, facility/process record or verified factor with source and version, location and period, units, and allocation rule. CarbonLayer currently publishes no per-inference water baseline or impact.
Evidence request, not current measurement
10
Methodology v1.0 is available as the public framework; coefficient verification remains pending. Future revisions must identify changes to the boundary, functional unit, source record, factor, allocation method, uncertainty treatment, or publication rules.
Any future estimates may be reassessed when required evidence and defensible input ranges become available. Reassessment does not turn a modeled value into a measured result, and no independent verification of the researcher-reported summary is implied.
Excluded until supported
Embodied/lifecycle impacts, physical routing claims, facility-meter claims, provider model telemetry, unsupported PUE allocation, and unverified source factors.
Not a claim
This release is not an SCI score, compliance certification, independent audit, or statement that a particular facility or provider produced a measured impact.
11
The current prototype reports request attribution, token count when supplied, timestamp, and simulated route and latency metadata. The route target and latency values are illustrative, not measured results or evidence of physical routing. Its receipt boundary remains explicit:simulationStatus: simulated, modelProviderCalled: false, andimpactDataStatus: unavailable. The API receipt is real; its simulated model and dispatch fields are not measurements.
Prior site-audit corrections
robots.txt was a full disallow:User-agent: * and Disallow: /. The audit also found that the 404 pages were not byte-identical. These are audit corrections about site behavior, not methodology evidence and not proof of an environmental result.Researcher-reported grid summary
The summary describes different location-based, hourly, marginal-proxy, and lifecycle candidates. The full ledger and source PDF are absent, no basis is selected, and the reported material is not independently verified here. Candidate constants are omitted.
Researcher-reported water summary
The summary says regional AWS operator-reported withdrawal figures may support a direct/evaporative layer after verification. A Microsoft fleet average is not regional evidence; indirect watershed impact and per-inference water remain unavailable. The figures are not independently verified here.
Repository seed and synthetic grid adapter
Internal modeled inputs and synthetic fallback behavior. These can explain prototype behavior but cannot establish a measured per-device environmental result.
Full ledger and source PDF
Neither is attached to this task. This page uses only the researcher-reported summary, does not reproduce candidate constants, and does not treat the summary as independent verification.
For the current receipt contract, read the API docs. For the concise boundary note, read the training and carbon math. Those pages describe prototype behavior; they do not provide evidence for unavailable impact values.