Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2616 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T08:04:33.731798Z status: published lens: p_space sector: climate headline: Rapid artificial intelligence deployment increases near-term pressure on global carbon budgets dek: Limiting warming to 1.5 degrees Celsius depends on cumulative carbon dioxide emissions, not only on whether annual emissions eventually balance. Artificial intelligence is increasingly promoted as a tool for reducing emissions, but its supporting digital infrastructure produces emissions before many system-level benefits are realized. Here, we evaluate this timing mismatch using a probabilistic numerical cumulative carbon accounting model calibrated to International Energy Agency artificial-intelligence and ener… gain_title: (none) problem_title: A modelling study calibrated to International Energy Agency scenarios estimates that under rapid AI expansion, AI infrastructure would add a median 2.85 gigatonnes of CO2 before annual savings exceed annual emissions in late 2031. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: A modelling study calibrated to International Energy Agency scenarios estimates that under rapid AI expansion, AI infrastructure would add a median 2.85 gigatonnes of CO2 before annual savings exceed annual emissions in late 2031. problem_evidence: the accelerated Lift-Off pathway yields a median cumulative carbon debt of 2.85 gigatonnes of carbon dioxide before annual savings exceed annual infrastructure-related emissions in late 2031 quick_read: A modelling study by Yassine Charabi of Kuwait University, published in Communications Earth & Environment, estimates that fast AI expansion produces emissions well before its climate benefits arrive. Across 10,000 Monte Carlo runs of the International Energy Agency's high-growth Lift-Off scenario, the median cumulative carbon debt reaches 2.85 gigatonnes of CO2 before annual savings pass annual infrastructure emissions in late 2031 (median breakeven 2031.8). The timing matters because warming tracks cumulative emissions. The author argues that emissions released early in the build-out use up part of the remaining 1.5 degree budget, and that later savings avoid future emissions rather than removing CO2 already emitted. Erasing the debt would depend on large-scale carbon dioxide removal, which the paper calls unproven. The results are scenario projections, not measurements. The debt is shallower under the IEA Headwinds and High Efficiency pathways and intermediate under Base. It grows if only a small share of AI infrastructure serves mitigation-related uses, and breakeven is not reached within the modelled horizon under low coupling. limitation: The model treats all AI infrastructure growth in aggregate rather than separating mitigation-oriented applications from other compute, and its marginal-emissions adjustment draws on a limited set of mainly U.S. electricity markets. tag: Evidence-backed problem key_points: Operational electricity use accounts for 1.96 Gt CO2, about 69% of the 2.85 Gt total under average-grid accounting. | Adjusting for AI loads being served by more carbon-intensive marginal power adds 0.87 to 0.91 Gt CO2, the largest single amplifier in the model. | Hardware refresh every three years adds only about 0.02 Gt CO2 of embodied emissions, in pulses in 2024, 2027 and 2030. | In 2030, efficiency gains save 154 TWh while Lift-Off growth adds 318 TWh versus Base, a Jevons Ratio of 2.06. | Data centres in 2024 ran at an average power usage effectiveness of 1.32 in North America, 1.81 in Africa and 1.92 in the Middle East, a 37 to 45% energy overhead in warmer regions. | Each year of delay in adopting AI-enabled system savings adds about 0.45 Gt CO2; a three-year delay lifts the debt to about 4.20 Gt and a five-year delay to about 5.10 Gt. | Shifting AI workloads to times of high renewable output or low marginal emissions would, in the model, shrink the debt and bring breakeven forward. rundown: The model combines operational emissions, embodied hardware emissions and delayed system-level savings from AI used in power systems, industry and transport. It starts from a 2024 baseline of 460 TWh of AI-related data-centre electricity demand and a grid carbon intensity of 0.46 tCO2 per MWh, and evaluates four IEA pathways: Headwinds, Base, High Efficiency and Lift-Off. Rebound effects drive much of the result. Under Lift-Off, extra AI demand in 2030 is about twice the electricity saved through efficiency, so efficiency gains alone do not reduce total demand. Siting also matters: warmer climates need more cooling energy for the same computing work, deepening the carbon debt compared with temperate regions. The paper says adoption timing is important, with each year of delay adding about 0.45 Gt CO2, and that coordinating AI loads with the power grid could cut exposure to high-emission periods. It notes AI may still enable substantial long-run emissions cuts, but near-term deployment decides whether that benefit arrives within this decade. sources: - peer_reviewed | Communications Earth & Environment | https://doi.org/10.1038/s43247-026-03746-y | 2026-06-08 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 341a2070586d6ef367753e2275ac6f8aaee2bc262f64e0cd0976174f07e5d5dd
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2616 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace