Show the likely impact
Publish credible estimates for grid demand, water use, household costs, jobs, data, and ecology.
Subject 01 / Public-review draft
Data centers, cloud systems, and energy-intensive AI can affect water, electricity, household bills, jobs, data rights, and local ecosystems. This draft asks what evidence and protections should be required before public-benefit claims are made.
Public review only. This page does not certify, endorse, approve, or authorize an infrastructure project.
In plain language
AI infrastructure should not ask the public to trust broad promises. Before an actor can claim alignment, affected people should be able to inspect the likely costs, the promised safeguards, the decision rights, and the evidence that will remain public.
Publish credible estimates for grid demand, water use, household costs, jobs, data, and ecology.
People who carry the risk should have meaningful authority, not only a listening session.
Define what would require mitigation, redesign, delay, or rejection before construction or scaling.
Use independent review and publish non-sensitive evidence so claims can be checked over time.
Interactive pressure test
Each lens turns the draft into four practical questions: what could go wrong, what proof is needed, who needs protection, and what should stop the project.
Energy + grid
Your focused review question
What minimum energy and grid evidence should be public before an AI infrastructure project can claim alignment?Answer on this site
Formal public draft
Status: public-review one-pager. The language below is the source draft rendered for easier reading; it is not a final standard or certification scheme.
AI infrastructure should not raise bills, drain water, weaken grids, extract data, displace workers, or burden ecosystems without transparent evidence, affected-party governance, and measurable community benefit.
Grid-impact analysis, reliability safeguards, and a resilience contribution.
No modeled net harm for vulnerable households without mitigation or benefit routing.
Water-use disclosure, basin-specific thresholds, drought sensitivity, and public reporting.
A binding community benefit agreement with participatory governance.
Local training, transition benefits, no-surprise automation, and career pathways.
Public-interest telemetry governed through a data trust or equivalent accountability.
Baseline ecological review, restoration triggers, and Rights-of-Nature alignment where legally viable.
Independent review, a public dashboard, a claims register, and evidence publication.
Defined conditions that pause, redesign, or reject the project.
People who carry the risk have a meaningful role in decisions, oversight, and remedy.
The least proof that must exist before an actor can make an alignment or public-benefit claim.
A non-sensitive receipt showing what was measured, promised, decided, delivered, and audited.
One focused contribution
Choose one missing proof, protection, decision right, or pause condition. You can submit it on this site without a GitHub account.
GitHub is optional and public. Use it when you want to propose a source edit or join a public issue discussion.