TRV-2026-2116Certified recordPeer-reviewed

The Environmental Cost of AI Hype: Corporate AI Catering, Pollution Emissions, and Sustainability Governance

The long development cycle and high investment requirements of artificial intelligence (AI) conflict with the short-term incentives prevailing in capital markets, leading some firms to cater to market expectations through promotional rhetoric rather than substantive investment, possibly at the expense of long-term sustainability commitments. This study examines whether such AI catering affects corporate pollution and under which conditions. Using Chinese A-share listed firms with firm-level emission records from…

Climate · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

Substantive AI input, meaning actual AI investment predicted by observable inputs, is associated with lower pollution emission intensity among Chinese listed firms.

Current reading — problem

AI catering, or AI disclosure exceeding what substantive AI input predicts, is associated with higher corporate pollution emission intensity, partly through lower environmental investment and weaker environmental disclosure quality.

What this doesn’t fix

The evidence is an association drawn from Chinese A-share listed firms from 2016 to 2024 and explains only part of the link through the tested channels, so it does not establish universal causal effects.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2116, v1: “The Environmental Cost of AI Hype: Corporate AI Catering, Pollution Emissions, and Sustainability Governance.” Truvace, 2026-10-21. /record/TRV-2026-2116 (accessed at citation time). sha256 b68896032d0e5d4e…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1b68896032d0e…

    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-2116 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.