TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0090Certified recordJournalism

US leads record global surge in gas-fired power driven by AI demands, with big costs for the climate

The US is leading a huge global surge in new gas-fired power generation that will cause a major leap in planet-heating emissions, with this record boom driven by the expansion of energy-hungry datacenters to service artificial intelligence, according to a new forecast. This year is set to shatter the annual record for new gas power additions around the world, with projects in development expected to grow existing global gas capacity by nearly 50%, a report by Global Energy Monitor (GEM) found. The US is at the f…

Climate · P Space — documented harm · certified 2026-07-12 · v5 · article view · machine-readable

Current reading — problem

Building new gas-fired power plants to meet electricity demand from AI datacenters is forecast to cause a major leap in planet-heating emissions and lock in decades of pollution.

What this doesn’t fix

Forecast based on projects in development; actual buildout and emissions depend on whether uncertain AI energy demand materializes and on policy choices

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0090, v5: “US leads record global surge in gas-fired power driven by AI demands, with big costs for the climate.” Truvace, 2026-07-13. /record/TRV-2026-0090 (accessed at citation time). sha256 e69b3aa847c3132d

Calibration history

Every change to this record since certification, in the open.

  1. Revisedv5e69b3aa847c3

    Model backfill: grounded claim, summary, sector, and trace validation

  2. Certifiedv427e058d5597b

    Restored after model confidence scale normalization

  3. Retractedv3b8828d3ab410

    Model backfill: source did not support a publishable AI-impact claim

  4. Revisedv2533a73b3c5ea

    Reading revised

  5. Certifiedv167749a4afde7

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0090 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.