TRV-2026-2292Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2292 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-28T06:45:35.280528Z status: published lens: p_space sector: policy headline: UK government met 137 businesses over AI datacentres – but no environmental groups dek: The UK’s policy on datacentres and AI was developed without any meetings with environmental groups, an investigation has found. The nonprofit organisation Spotlight on Corruption said a “considerable revolving door” shaped the government’s development of “AI growth zones”, a central plank of the former prime minister Keir Starmer’s AI and economic policy, with 38 ministers, senior civil servants and special advisers hired to positions in AI companies between July 2024 and September 2026. Meanwhile, even as top o… gain_title: (none) problem_title: The UK's AI datacentre policy was shaped by 137 business meetings while senior officials met no environmental organisations and only two community groups, despite serious environmental implications. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: The UK's AI datacentre policy was shaped by 137 business meetings while senior officials met no environmental organisations and only two community groups, despite serious environmental implications. problem_evidence: senior officials met only two community groups and no environmental organisations | The government totally failed at the most senior level to speak to environmental NGOs or community groups when developing its flagship policy on AI datacentres. quick_read: A nonprofit, Spotlight on Corruption, filed 40 freedom of information requests to 18 government bodies about how the UK developed its AI growth zones policy. It found senior officials met 137 businesses but no environmental groups and just two community groups between July 2024 and June 2026. The findings matter because the plan involves very large datacentres with potential environmental costs, and local opposition is growing. The report's picture is limited to disclosed meetings, since some contacts may not have been recorded, and the government says it wants to work with environmental groups and communities. limitation: Many business meetings may not have been disclosed, because the policy was led by a special adviser whose role faced less stringent transparency requirements. tag: Evidence-backed problem key_points: Spotlight on Corruption sent 40 freedom of information requests to 18 government agencies over 12 months. | Of 38 senior officials who left government between July 2024 and September 2026 for AI companies, nine came from the science and technology department. | Civil society meetings were held days before the policy launch, so they had no meaningful input, according to the report. | Canada, Germany and Australia consulted more widely and set stricter environmental criteria, the report says. rundown: The investigation examined policymaking on AI growth zones, which promised to build large datacentres across five regions to boost the economy and create jobs. It said a revolving door between government and AI companies, including OpenAI and Anthropic, shaped the policy. Guardian investigations have questioned the policy's assumptions, unaudited financial figures and job projections, and found little realism in plans to power sites with purpose-built renewables. Government departments also appear to differ on how much electricity the plans will need. A government spokesperson said datacentres should deliver local benefits while prioritising clean power and responsible water use. Officials said community benefits are generally handled through local planning and that councils hosting growth-zone sites in England will keep additional business rates. sources: - journalism | The Guardian | https://www.theguardian.com/uk-news/2026/oct/27/uk-government-environmental-groups-ai-datacentres-expansion-plans-investigation | 2026-10-27 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- d2ea6e1924b4235e316e664dd7af96fd272238714b77bc889dc3abc69c72413a
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2292 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.
ace