TRV-2026-1338Version 1 · Certified

Written 2026-10-14 18:12:37 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1338
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-14T18:12:37.796474Z
status: published
lens: g_space
sector: policy
headline: AI overlords say they want to democratise their technology. Here’s how | Richard Wilson and Clara Long
dek: What’s your “(p)doom” – the percentage chance that rogue AI will create an existential catastrophe? Judging by their recent warnings, it is rising among tech bosses. On 25 September, OpenAI paused training of its latest frontier models as reports of AI agents going rogue mounted. A day later, Australia’s Senate asked the bosses of OpenAI and Anthropic to appear before an inquiry after rogue OpenAI agents broke into US government websites and an Australian health portal. Both declined. Bill Gates, meanwhile, has…
gain_title: A civic-lottery assembly of Utah residents reached broad cross-partisan agreement on public controls for AI infrastructure, giving legislators a visible public mandate.
problem_title: (none)
trace_subject: (none)
gain_reading: A civic-lottery assembly of Utah residents reached broad cross-partisan agreement on public controls for AI infrastructure, giving legislators a visible public mandate.
gain_evidence: 38 residents selected by civic lottery
problem_reading: (none)
problem_evidence: (none)
quick_read: The authors describe a two-day Utah forum in September where randomly selected residents deliberated on the public's role in decisions about AI and datacentres. The forum followed a backlash against a very large datacentre proposal. Participants produced ten recommendations that drew strong agreement despite political differences.

The authors argue the example matters because AI risk tolerance is a political choice, not only an engineering one, and assemblies could give governments cover to require testing and safeguards. Whether decision-makers will act is unresolved, since the forum has no guaranteed hearing and wider assembly work is described as fragmented and largely ignored.
limitation: The Utah forum has no guaranteed hearing with decision-makers, and the authors admit assemblies alone cannot protect against the most severe AI misuse risks. The piece is an advocacy opinion by assembly organisers.
tag: Evidence-backed gain
key_points: Utah Common Ground convened 38 residents by civic lottery on 18 and 19 September to consider public influence over AI technology and infrastructure. | The ten recommendations included public hearings and independent environmental assessments for hyperscale datacentres, community AI literacy programmes and tighter transparency rules. | The authors cite more than 80 public participation projects on AI worldwide involving more than 200,000 people in over 95 countries. | The Bloom Project is building local and state US assemblies meant to feed a national citizens' assembly on AI in 2028.
rundown: The Utah forum was prompted by objections to a proposed datacentre more than twice the size of Manhattan. Critics raised energy use, stressed water supplies and the Great Salt Lake ecosystem, and residents felt shut out of the decision.

Beyond Utah, the article points to a Swiss citizens' assembly demanding privacy, transparency and human control, and a Belgian panel calling for AI that leaves nobody behind. It says this work is currently fragmented. The Citizens' Track on AI aims to link such assemblies to institutions, including UN processes and AI companies.

The authors also cite Taiwan moving from a citizens' panel to law in months on scam advertising, and say lobbyists cannot buy an assembly's outcome. They concede assemblies alone cannot protect against cyber-attacks, biological weapons or loss of control over AI.
sources:
- journalism | The Guardian | https://www.theguardian.com/commentisfree/2026/oct/14/ai-overlords-democratise-technology | 2026-10-14
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
a773b254dc5a9b872f6d518dd6cde7446b8b45cf5d546d8a168cd85b79170bc5
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1338 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.