OpenAI National Community Compact and Compute Campus Policy Blueprint published November 5, 2026; coverage November 5 to 6, 2026
No More Secret Site Deals: OpenAI Ends Official NDAs and Pledges to Pay Full Power Costs at Future Campuses
OpenAI published two documents on November 5: a National Community Compact covering its own conduct, and a Compute Campus Policy Blueprint proposing rules for the wider industry. The compact applies to every future compute campus OpenAI owns and operates, a boundary the coverage stresses, since it does not clearly extend to the partner-built or leased capacity the company also uses. Its headline commitments are specific. OpenAI says it will no longer use nondisclosure agreements with public officials when negotiating future sites, with exceptions for legitimate security information, trade secrets, and proprietary or competitively sensitive information. It will pay the full cost of the electricity it uses and the infrastructure needed to serve it, provide financial assurances before major spending so other customers are protected if a project is delayed, reduced, or canceled, reduce consumption at peak demand, and prioritise closed-loop water systems. On transparency, each campus gets its own local compact, a named local contact, published construction plans, independent noise studies, and site-level water and electricity reporting, with public progress reports each year. The context is electoral: the documents followed November 3 voting in which data center projects faced repeated local defeats, though the tallies differ by source and should be read separately, one count reporting restrictions in 33 of 45 measures by the morning of November 4 and another framing 41 measures across 10 states, alongside an NBC News poll in which 76 percent of voters opposed a data center in their community. OpenAI chief global affairs officer Chris Lehane told reporters the work had been in development since August. Amazon announced in October that it had stopped using NDAs with government agencies on data center projects. What the reporting does not establish is equally clear: whether the pledges are legally binding, how compliance would be independently verified, what remedy follows a breach, and who decides whether withheld information fits an exception.
Executives
Read the compact as a market signal about the cost of building AI capacity: power, water, noise, and secrecy have become permitting risks, and the largest builder is now pricing community consent into its projects, full power costs, financial assurances, published impact data. Any organization planning compute expansion, its own or through a provider, should expect the same questions from host communities and regulators, and should note the blueprint second purpose: OpenAI is asking lawmakers to make its voluntary terms mandatory for competitors, which would turn this week pledges into next year compliance baseline.
CIO / CISO
For vendor and site governance, the usable output is a question set for any data center or cloud capacity negotiation: will the provider sign officials NDAs, who pays grid upgrade costs, are site-level energy and water figures published, and what assurance protects ratepayers and customers if a project shrinks. Hold the scope line firmly in your records: the compact covers campuses OpenAI owns and operates, and coverage of leased or partner capacity is unresolved, so a supplier claim of compact compliance needs the follow-up question, for this facility, which the compact may not reach. The absence of stated verification or enforcement is not a reason to dismiss the pledges; it is the reason to convert the ones you rely on into contract terms.
Engineers
The technical commitments worth tracking are the measurable ones: closed-loop cooling as the priority design, peak-demand reduction and returning power to the grid when asked, and site-level consumption reporting for electricity and water. If you operate or specify facilities, those three are the emerging expectation set, and they need metering and reporting infrastructure designed in, not estimated afterward. Independent noise studies before operations and annually afterward are also an engineering deliverable, with baselines that only exist if someone commissions them before construction starts.
Everyone (non-IT)
If a large data center is proposed near you, this week changed what you can reasonably ask for. A leading builder has now said, in public, that officials should not have to sign secrecy agreements to discuss a project, that the builder should pay its full power costs, and that residents should see construction plans, noise studies, and water and electricity figures for their site. Those promises belong to one company and its future owned campuses, and nobody has published how they would be enforced, but they set a reference point you can hold any developer to at a public meeting.