42/100

Emerging evidence

Published recordPolicyGeneral

Halt super-intelligent AI with non-proliferation treaty, Ed Davey to say

Truvace record
TRV-2026-1160raw data (JSON)
Version
v2Revised
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
4b15c9b3cb8d…check it

Ed Davey is to call for a global nuclear-style non-proliferation treaty to halt the development of super-intelligent AI when he makes his keynote speech at the Liberal Democrat conference, accusing Andy Burnham of relying on Donald Trump and “tech bros” to solve the problem. When he addresses the faithful on the final day of the gathering in Brighton, the party leader will call for a global pause on super-intelligent AI, comparing it to a nuclear arms race that could result in technology that could “destroy us a…

The problem

Davey is expected to call for a new global movement to work together to protect humanity from the risks of super-intelligent AI, saying that the IAEA was built by nations “working together to control a technology that could destroy us all”, but warning that the future of AI is being decided by “a tiny number of the richest and most powerful in California and in Beijing” with no guardrails to slow down development.

Sources

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

Cite this record

v2

Truvace Impact Record TRV-2026-1160, v2: “Halt super-intelligent AI with non-proliferation treaty, Ed Davey to say.” Truvace, 2026-11-04. /record/TRV-2026-1160 (accessed on the day you copy it). sha256 4b15c9b3cb8d9792…

Change history

2 versions

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

  1. Revisedv24b15c9b3cb8d…

    Editorial pass: filed as context: no real AI gain or problem (gain absent, problem unsupported).

  2. Publishedv1a8d32a7264c5…

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