Weekly AI infrastructure review: 2026-06-29

[github-actions]

Weekly AI infrastructure review (2026-06-29)

Automated check from scripts/weekly-ai-infrastructure-check.mjs. Triage and either:

• Add or update entries in data/ai-infrastructure-projects.json (and mirror to public/api/ai-infrastructure/projects.json), bump last_reviewed in data/page-freshness.json, then close this issue, OR
• Comment noop and close if nothing actionable surfaced.

Current state of the registry

• Last reviewed: 2026-06-05 (24 days ago) ⚠️ OVERDUE
• Cadence: weekly
• Projects tracked: 17
• By status: construction (11), operational (4), permitted (1), announced (1)
• Announced capacity total: 15.2 GW

AI-infrastructure-flavored news, last 7 days

Matched 5 articles (keyword scan; many will be tangential).

Date	Source	Title
2026-06-26	WIRED AI	Europe Is Fed Up and Wants Its Own AI
2026-06-25	WIRED AI	Why Amazon Dropped Its OpenAI Movie, Data Center Workers Fight Back, and Meta Leaks Employee Data
2026-06-24	Hugging Face Blog	Accelerating Transformers Fine-Tuning with NVIDIA NeMo AutoModel
2026-06-23	Ars Technica	Oracle’s 21,000 layoffs help drive its debt-fueled AI investments
2026-06-23	Hugging Face Blog	Experimenting with the proposed Cross-Origin Storage API in Transformers.js

Sources: WIRED AI (2), Hugging Face Blog (2), Ars Technica (1)

---

What justifies a new entry

1. A gigawatt-class campus is announced, permitted, or breaks ground.
2. A nuclear PPA or restart deal lands between a hyperscaler and an operator.
3. An AI-specialized compute operator (CoreWeave / Lambda / IREN / Hut 8 / Crusoe class) ships a materially larger fleet or PPA.
4. An existing tracked project changes status (announced to permitted to construction to operational).
5. A regulatory event materially reshapes the buildout (FERC ruling on grid bypass, NRC license decision, big court ruling).

What does NOT justify a new entry

• Generic data center announcements not tied to AI workloads.
• Speculative reporting without operator or partner attribution.
• A < 100 MW deployment from a non-flagship operator.
• Routine quarterly capex disclosures without a specific named project.

When you update the registry, bump last_reviewed in data/page-freshness.json so the visible footer stamp moves forward and the OVERDUE flag clears.