By Christina Alfonso, Executive Director and President Council on Global Competition and Innovation – CGCI; Senior Fellow, The Intelligence Project at Harvard’s Belfer Center
America is building something big.
In late 2025, the United States launched the Genesis Mission—an AI and high‑performance computing effort designed to accelerate breakthroughs across national priorities, including energy capacity and national security. The program is ambitious by design: federal compute, national labs, AI models, robotics, and curated datasets are organized to speed discovery and engineering where it matters most. It has already been cast as America’s “AI Manhattan Project” in a bid to roughly double U.S. scientific productivity over the coming decade.
To maximize Genesis’s impact, it must operate not only as a breakthrough science platform but as the operating system for U.S. energy. In a country with world‑class research, deep capital markets, and a Department of War planning for contested logistics and resilience, utilities and developers are still working on an energy system held together by legacy processes. The missing layer is a shared, scalable backbone that connects these actors into a coherent energy‑security system—that is the role Genesis is positioned to play.
The Energy Capacity Crisis
For more than a decade, U.S. electricity demand looked flat, but that is changing dramatically. Load is now rising as AI data centers and compute infrastructure scale faster than grid build‑out timelines. Electrification is shifting vehicles, buildings, and industrial processes from fuels to electrons, while reindustrialization and onshoring pull new manufacturing demand back onto U.S. networks. What began as an “energy transition” story is now an energy capacity and throughput story with direct national security implications. In a competition defined by industrial strength, technological edge, and military readiness, electricity is the foundational strategic input.
Yet while demand accelerates, the system that moves power is constrained. A massive volume of proposed generation and storage sits in interconnection queues—far beyond what today’s transmission system and planning processes can absorb quickly. Projects stall, timelines stretch, attrition rises, and even where capital is ready, permitting fights and cost‑allocation debates slow the build.
For the Pentagon, it is also a defense industrial base (DIB) problem in disguise. The same substations, interconnection queues, and contested transmission corridors that decide where fabs and data centers can run at scale also decide whether depots, ports, and bases can add the capacity and resilience their missions demand. This energy layer sits in a blind spot between infrastructure policy and defense acquisition, so it rarely appears as a requirement, program of record, or budget line tied to specific defense outcomes. It is central to warfighting and surge capacity, but still largely unrecognized in how it is governed and resourced.
Platform vs Operating System
Genesis was set up to be a federal AI‑enabled science platform, integrating compute, data, models, and tools across the national laboratory system and beyond. In early 2026, the Department of Energy translated that mandate into Genesis AI challenges with aggressive targetsacross grid planning and operations, nuclear deployment, facility autonomy, and high‑consequence engineering workflows. Some of these challenges already call for interoperable digital twins, streaming data standards, audit trails, and agentic workflows.
But there is a difference between a platform for science and an operating system for energy security. A platform is successful when it produces results. An operating system is successful when others can reliably build and run on top of it, at scale, under constraints, and within real decision processes.
The Genesis mandate and its early challenge set already lean in this direction. The task now is to make “operating system” the organizing principle for how the platform is built, governed, and adopted.
Three Design Questions Genesis Can Use to Maximize Its Impact
Thinking of Genesis as an operating system surfaces a set of design questions that Genesis leaders and their partners now have a timely opportunity to answer.
The first is who counts as a user. Today’s narrative understandably centers on national labs and academic researchers, but they are not the actors who approve interconnection requests, issue permits, dispatch power plants, or allocate capital. The highest‑leverage users are grid operators and utilities, state and regional regulators and permitting authorities, Department of War installation and resilience teams, and the developers and investors who decide what actually gets built. If these users cannot use Genesis in their normal workflows, it will produce knowledge but not throughput.
The second question is what interfaces it exposes. In software, an operating system matters because it standardizes interfaces. For energy security, those interfaces translate into common ways to ingest grid, load, and reliability data; to run interconnection and transmission studies with reproducible assumptions and outputs; to evaluate nuclear, fusion, and data‑center projects against shared security, resilience, and performance benchmarks; and to generate decision‑grade evidence packages that regulators, the Department of War, and investors can trust.
The third question is who governs the platform and how. If Genesis becomes the operating system for critical energy decisions, governance needs to be as intentional as the technical architecture. Governance decisions must answer who sets priorities when agencies disagree, who vets external partners and under what criteria, how conflicts are resolved across federal, state, and regional boundaries, what becomes “standard” when trade‑offs are unavoidable, and who is accountable when those standards fail.
Early U.S. electric power systems illustrate the stakes. Regional grids emerged with mismatched rules and processes, and their patchwork structure stalled national scaling. Only when governance frameworks—starting with the state commissions of 1907 and culminating in the 1935 Public Utility Act—established shared standards did the grid evolve from scattered experiments into coherent national infrastructure. That experience proved in practice that without governance there is no grid.
The Role of the National Labs
The national laboratories are central to making Genesis work. They should be the core developers and maintainers of models and standards, the stewards of digital twins, neutral validators of tools proposed by industry, and hosts of testbeds where high‑risk ideas can be proven safely. In that role, they can enable and inform applied decision‑making across utilities, regulators, the Department of War, and industry, even though they are not the ones formally issuing permits or allocating capital.
The goal is not to centralize intelligence inside labs, but to push reliable, vetted intelligence to where decisions actually happen: public utility commissions, grid control rooms, military base planning offices, and capital committees. If Genesis becomes a lab success story with limited adoption outside the lab ecosystem, the United States will still face slow interconnection, fragmented transmission build‑out, and misaligned incentives. The opportunity is to turn the labs’ technical excellence into shared infrastructure that lowers friction and de‑risks investment for everyone else.
Designing Genesis as an Operating System for Energy Security
Ultimately, Genesis will succeed as an operating system for energy security only if it makes it easier for operators, regulators, and investors to say “yes” to the right projects. If Genesis is built as the OS layer—secure kernel, standardized interfaces, reference workflows—external partners can build the financing structures, bankability frameworks, and resilience packages that move from policy intent to steel in the ground. Success will show up as less friction across institutions: faster interconnection and planning, higher conversion of queued projects into built capacity, and measurable gains in resilience for critical loads and defense facilities.
As President of the Council on Global Competition and Innovation (CGCI), this is where I see market‑facing national security organizations like ours adding particular value. Institutions operating at the intersection of capital markets, critical technologies, and national security can translate Genesis workflows into investable theses and scalable public–private partnerships, mobilizing private capital and operating expertise alongside federal leadership while reducing the amount of direct public funding required. That role depends on having a federal platform built from the outset to interface effectively with markets. What remains is to decide what Genesis is for and to design it accordingly.



