30/100

Emerging evidence

Published recordLaborProblem Space (a documented problem)

Anti-AI populism is the future of American politics | Garrison Lovely

Truvace record
TRV-2026-2475raw data (JSON)
Version
v1Published
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourceJournalism
sha256
75b397b7e8f5…check it

The AI industry had a bad night last week. The Democrats’ sweeping midterms victory is a rebuke of Donald Trump, the industry’s most powerful champion. Almost everywhere they could, voters rejected datacenters: moratoriums and other restrictions passed in more than 30 localities across nine states. And, with wins in places such as Texas, Ohio and Georgia, an estimated 41% of planned datacenter capacity is in states with governors-elect backing moratoriums. To be sure, the election results were not primarily abou…

The problem

A columnist says voters passed datacenter moratoriums or restrictions in more than 30 localities across nine states, and an estimated 41% of planned datacenter capacity sits in states with governors-elect backing moratoriums.

What this doesn’t fix

The columnist says the election results were not primarily about AI; corruption, cost of living, Iran and immigration ranked as more important to voters in NBC exit polls.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-09

Cite this record

v1

Truvace Impact Record TRV-2026-2475, v1: “Anti-AI populism is the future of American politics | Garrison Lovely.” Truvace, 2026-11-12. /record/TRV-2026-2475 (accessed on the day you copy it). sha256 75b397b7e8f5134d…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv175b397b7e8f5…

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