Responsible AI infrastructure: check the compact and blueprint clauses, not “campuses are already responsible”

OpenAI’s 2026-11-05 post puts the claim plainly: communities that host compute campuses should shape plans, make developers cover power costs, and share jobs and business opportunities. The same day it released two documents. The National Community Compact states what communities can expect at campuses OpenAI owns and operates. The Compute Campus Policy Blueprint asks lawmakers for rules on self-paid power, public reporting, narrow NDAs, and clawbacks on tax incentives.

This is not a model launch. It is a checkable policy and community-compact text, layered on January Stargate Community commitments and specific Georgia and Ohio pledges. The test is the duties and numbers in the files, not reading the headline as “responsible infrastructure already delivered.”

Hard facts (https://openai.com/index/setting-new-standard-responsible-ai-infrastructure/; publicationDateText November 5, 2026; body cross-checked via r.jina.ai and Wayback; accessed Asia/Shanghai same day):

• Two files: National Community Compact (https://cdn.openai.com/pdf/community-compact.pdf) and Compute Campus Policy Blueprint (https://cdn.openai.com/pdf/compute-campus-policy-blueprint.pdf).
• Scope: every future compute campus OpenAI owns and operates gets a local compact; engage residents early, keep a local point of contact, report publicly each year.
• Energy: pay the full cost of electricity used and infrastructure needed to serve the campus; provide financial assurances before major spending so other customers are protected if a project is delayed, reduced, or canceled.
• Resources and transparency: a water plan per campus, prefer closed-loop or low-water cooling, publish site-level water and electricity use; publish construction plans and independent noise studies before operations and annually afterward; no NDAs with public officials except narrow protections for security information, trade secrets, or competitively sensitive information.
• Jobs and local investment: publish expected jobs, work with unions and training providers, report annually on hiring and apprenticeships; make sustained investments in priorities residents help select.
• Named local figures: Effingham County, Georgia, $4.8 million for free school meals for all 14,000 students; Pike County, Ohio, a joint $6 million childcare commitment from OpenAI and SB Energy. The Georgia Power agreement allows cutting power delivered to the campus by up to 1,000 megawatts in high-demand periods.
• The blueprint also asks state utility commissions to make large electricity customers cover costs they add to the grid; utilities to ease interconnection when campuses can safely cut demand; Congress to speed transmission upgrades and restore or expand clean-electricity tax incentives; and tax-incentive terms to be public, measurable, and recoverable if a developer falls short.

Evidence strength: this is a company policy statement plus legislative asks, not a third-party audit. What you can check now is whether the two PDFs exist, whether the post restates the duties above, and whether the named $4.8 million, $6 million, and 1,000-megawatt figures remain in the text.

How to test it: open the compact and blueprint PDFs and match “pay our own way,” water plans, NDA limits, and annual reporting; re-read the January Stargate Community commitments and the Georgia and Ohio posts to see whether today’s text really is the “next step.” If later independent local reporting shows campuses not paying their power costs, not publishing water, power, and noise data, or requiring broad NDAs of public officials, lower the execution claim.

Steelman: writing self-paid power, financial assurances, and clawable incentives into industry rules would shrink the familiar fight where campus costs are socialized and gains stay private. Annual public reports also give residents a table they can cite, not only a verbal promise.

Strongest steelman: voluntary company pledges without state utility rules and public incentive terms will not bind “whoever builds a campus.” Pushing that work to lawmakers is politically honest; a one-firm compact cannot cover the industry.

Steelman risk: the files are OpenAI’s own account. They lack a third-party verification schedule and detailed remedies for breach. Scope is limited to campuses it “owns and operates”; joint ventures, leased sites, or campuses run by others are not written as full equivalents. The $4.8 million and $6 million figures are local priority examples, not a national welfare standard. “New standard” in the title is a normative claim, not a finished compliance audit.

For local officials and utility regulators, the next six months to watch are whether state large-load cost-allocation rules appear along blueprint lines; whether OpenAI-owned campuses start publishing site-level water, power, and noise reports; and whether NDA practice narrows to the stated exceptions. For readers, the check is the compact and blueprint clauses plus the named dollar figures, not “responsible AI infrastructure already achieved.”

What to check in this post is the enforceable language in the National Community Compact and Compute Campus Policy Blueprint, plus the Georgia and Ohio dollar figures and the 1,000-megawatt curtailment clause; not reading “setting a new standard” as industry compliance already done. It is a checkable policy stance with local examples. Treating the headline as past tense leaves the source behind.

【No.2】