52/100

Moderate evidence

ProblemPublished recordClimateProblem Space

AI-Driven Carbon-Neutral Computing Sustainability: A Data-Driven Framework Integrating Machine Learning and Environmental–Economic Systems

Truvace record
TRV-2026-2624raw data (JSON)
Version
v2Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
af0c3d4d07b4…check it

While artificial intelligence (AI) can improve energy efficiency in carbon neutrality applications, its high energy consumption and rebound effect weaken the actual emission reduction effect. To address the issues of high energy consumption and the rebound effect of AI weakening emission reduction, this paper proposes a green AI-driven environmental economic computing framework. First, an energy consumption perception index is introduced, and carbon emissions are monitored in real time using Carbontracker versio…

The problem

In experiments on a green AI framework, knowledge distillation had a rebound index of 0.75 and a net energy-saving rate of only 9.1%, so rebound erodes most of the expected savings.

Sources

1 on file
  1. Sustainabilitydoi:10.3390/su18115526
    Peer-reviewed2026-06-01

Cite this record

v2

Truvace Impact Record TRV-2026-2624, v2: “AI-Driven Carbon-Neutral Computing Sustainability: A Data-Driven Framework Integrating Machine Learning and Environmental–Economic Systems.” Truvace, 2026-11-12. /record/TRV-2026-2624 (accessed on the day you copy it). sha256 af0c3d4d07b48581…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2af0c3d4d07b4…

    Reworded the problem so it stands on its own; no facts changed.

  2. Publishedv139e1c9a051fd…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2624 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.