- Scope
- Australian AI infrastructure; Commonwealth, Tasmanian and Melbourne submissions
- Confidence
- High on the principle; individual projects need their own evidence
My starting point
If Australia wants lasting capability and control, government should be prepared to invest in that outcome. I support a shared public and private approach. I also accept that some supporting electricity and water costs may be shared through household and business bills when the contribution is explicit and justified. Tasmania, 01/10/2026 and Melbourne, 02/10/2026 set out that position.
That is a reason to assess contributions carefully. It is not a case for funding every proposed data centre. People should understand what they pay, what the developer contributes and what benefit the public receives.
What a public benefit should mean
Construction and operating jobs matter. So do services that businesses can actually use, practical skills and any credible Australian control. A forecast of innovation is weaker than a specified commitment, and a commitment is different from an achieved result.
My submissions ask for useful implementation support, rather than a nominal allocation of computing resources. People need to develop workflows, assess outputs and understand their responsibilities. The public case should explain how that capability will reach firms with limited time and technical capacity.
Energy and water are real conditions
I strongly support additional renewable generation to match data-centre demand. Projects, utilities and government should coordinate generation, connections and timing. Genuine constraints may be resolved through staging, shared infrastructure or a different location. Timely decisions require a clear account of what evidence would resolve the concern.
Water requirements should reflect the facility’s demand, cooling design and local supply. Greater Western Water’s June 2026 announcement describes planned recycled cooling-water supply to a future AWS facility. It is an example of a proposed arrangement, not evidence of savings already delivered or proof that the same solution suits every location.
Proportionate assessment should make responsible development achievable. I regard the economic opportunities forgone through unnecessary delay as a serious cost. That is my judgement about the trade-off, not a measured comparison showing that every delay costs more than proceeding.
The strongest challenge to public support
Public contributions can shift costs to people who do not receive commensurate benefits. Promised demand or capability may not materialise. A claim of sovereignty may rest on local storage without meaningful continuity. Those possibilities strengthen the case for transparent scrutiny; they should not be waved away by a large investment announcement.
Equally, an absolute ban on public or shared contributions could prevent investment in a capability the public has deliberately chosen to secure. My position is to leave room for a justified case. The available sources do not calculate the optimal public contribution or establish the merits of a particular project.
Implications and boundaries
I distinguish building infrastructure and skills from subsidising routine AI consumption. I do not support general discounts on users’ AI bills. Users should pay for what they consume, including a possible premium for Australian control and continuity.
Reporting should make material costs, commitments and achieved results understandable while protecting confidential and security-sensitive information. Reusing information already supplied through approval and utility processes can keep that reporting proportionate.
What would change this answer
Clear evidence that a proposed public contribution buys little additional benefit should lead to refusal or redesign. Evidence that shared infrastructure enables valuable capability at a reasonable cost should strengthen the case. Reviews should compare alternatives, who bears risks and whether actual performance matches commitments. Neither a public benefit nor an unjustified subsidy should be assumed from ownership alone.
Primary sources and limits
Recycled cooling-water supply to a planned AWS facility from the start of operations. Demonstrates a proposed arrangement, not achieved drinking-water savings or a solution suitable for every site. Register entry
Edition history
18/10/2026 · v1 · Initial publication
Launch of the living-article series, grounded in the dated submissions and primary sources listed here.
No earlier site edition or retrospective revision is claimed.