TRV-2026-1556Certified recordJournalism

Victoria was ‘ruthless’ in its quest to become the datacentre capital of Australia. Why has it hit the brakes?

In the private dining room of Government House, Jacinta Allan was assiduously taking notes as waiters served a three-course meal made with local ingredients and accompanied by Victorian wines. Sitting around the table at the meeting in March were leaders of artificial intelligence companies and datacentres, hand picked by the governor’s office for a discussion about the future of the industry. The peak body for datacentres spoke about the investment opportunities presented by its members. Academic researchers an…

Climate · Problem Space — documented harm · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — problem

Fast-paced datacentre expansion close to homes, such as the M3 site in Footscray, generated community opposition that the government itself acknowledged as legitimate, forcing a policy reversal and raising investment-flight concerns.

What this doesn’t fix

Whether the new rules will drive investment out of Victoria is disputed. The industry body warns it could happen and the government says there is no evidence, so the economic effect remains unproven.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1556, v1: “Victoria was ‘ruthless’ in its quest to become the datacentre capital of Australia. Why has it hit the brakes?.” Truvace, 2026-10-16. /record/TRV-2026-1556 (accessed at citation time). sha256 4e5372113b3342cc…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv14e5372113b33…

    Certified into the record

Verify this record
How to verify without trusting this page

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