The quiet machinery of American space nuclear capability, held open for sixty-one years by people you will mostly never hear about, now being cashed in.
On September 12, 1962, President John F. Kennedy stood in front of forty thousand people at Rice University and delivered the speech that you already know. We choose to go to the Moon in this decade and do the other things, not because they are easy, but because they are hard. The sentence has its own zip code in the American imagination. It has been quoted in eulogies, on plaques, in the openings of a dozen Netflix documentaries, and on the side of at least one craft beer. You know it.
Here is what is less well known.
Second, earlier in the same speech, Kennedy placed the coming age of space inside a historical sequence.
Those who came before us made certain that this country rode the first waves of the industrial revolutions, the first waves of modern invention, and the first wave of nuclear power, and this generation does not intend to founder in the backwash of the coming age of space.
Nuclear and space, paired in one breath. The speech is not just about getting to the Moon. It is about joining nuclear power to space as the next great national capability wave.
Third, and this is the one that matters: Kennedy did not write those lines, and in private he did not believe them.
The speech was drafted by Theodore Sorensen and revised by the President. But the broader framing the speech performed, the idea that the space effort was about capability rather than a stunt, that "the others" belonged in the same sentence as the Moon, that nuclear and space should be yoked together as paired national investments, was the argument a man sitting in the audience that afternoon had been making inside the administration for nineteen months.
His name was James Webb. He had been Kennedy's NASA Administrator for nineteen months. He was fifty-five years old, a former Director of the Budget under Truman, a former Undersecretary of State, and the kind of Washington administrator who wrote books on public administration in his spare time. The word for him is institutional. He was not an engineer. He was not a scientist. He was the kind of person who understands that the hard part of any great national effort is not the technical challenge. It is holding the coalition that funds the technical challenge long enough for the technical challenge to become a capability.
Through bureaucratic persistence, legislative alliance, and a mastery of the kind of slow institutional work that does not make it into commemorative plaques.
That is one scene. To understand it, we need a second one.
The second scene takes place sixty-three years and seven months after Rice, on the morning of April 14, 2026, in a ballroom at the Broadmoor Hotel in Colorado Springs. The forty-first Space Symposium is in its second day. The ballroom holds roughly six hundred people, most of them defense and aerospace industry attendees. The speaker is Michael Kratsios, Director of the Office of Science and Technology Policy, forty years old, in the job for thirteen months.
Kratsios is not giving a speech. He is delivering a document.
The document is called NSTM-3, short for National Security Technology Memorandum 3, and its title is National Initiative for American Space Nuclear Power. It is six pages long. It runs on clocks.
Thirty days for NASA to initiate a new reactor program. Sixty days for the Department of Energy to assess whether the industrial base can deliver four reactors in five years. Ninety days for the Department of War to brief on a 2031 in-space reactor mission. Ninety days for OSTP itself to produce what the document, without any apparent awareness of the phrase, calls an obstacles roadmap.
It sets a 2030 deadline for a lunar surface reactor. It specifies twenty kilowatts as the mid-power floor and one hundred kilowatts as an "extensibility" target, a distinction whose rhetorical function is ambition and whose operational function is retreat. It directs fixed-price contracting, milestone-based payments, and parallel NASA and Department of War competitions.
It is, depending on how you read it, either the most substantive American space-nuclear policy instrument since 1989 or another piece of paper in a stack of papers six decades tall.
Steven Sinacore, NASA's Fission Surface Power Program Executive (a position that did not exist until September of 2025), has been saying the same thing about NSTM-3 for three weeks, since before the memorandum was even released. He will keep saying it.
He is right. It has been an execution problem since SNAP-10A's reactor safety system tripped in May 1965 and the Atomic Energy Commission chose not to build another. It has been an execution problem through NERVA, through SP-100, through JIMO, through DRACO, through Kilopower, through sixty-one years of cumulative spending that now totals roughly twenty billion dollars and produced one reactor that worked for forty-three days. It has been an execution problem in the specific sense that someone has to actually execute.
Someone has to actually execute. The question this essay asks is who that someone has been, across sixty-one years, and what it has cost them to hold the position. NSTM-3 is an attempt to finally exercise the capability they built and held. Whether the attempt succeeds is a question for the next decade, not this essay. What you are inheriting, as an American in 2026, is the quiet labor of several generations of forgotten administrators, about to be cashed in by an administration that is not required to know any of this.
We should probably start with SNAP-10A.
The United States has launched one fission reactor into space. It was called SNAP-10A, short for Systems for Nuclear Auxiliary Power, tenth design iteration, model A. It was the size of a wastepaper basket. It lifted off from Vandenberg Air Force Base on an Atlas-Agena rocket at 21:24 Greenwich Mean Time on April 3, 1965. It went critical in orbit roughly twelve hours later. It produced 590 watts of electrical power (enough to run a small window air conditioner, not enough to boil a kettle) for forty-three days, at which point a voltage regulator on the Agena upper stage, which had nothing to do with the reactor, failed. The reactor's safety system did what it was designed to do: it ejected the beryllium reflector, the chain reaction stopped, and the dead reactor continued on its orbit.
What follows will be about holding things for a long time, and SNAP-10A is the only American space reactor that has actually done any holding. Every other American space-nuclear program, for the last sixty-one years, has been either a ground test, a paper study, a cancelled contract, or a design exercise. SNAP-10A is the one artifact.
The program that produced it, however, is not usually remembered as a success. This is because SNAP-10A stopped working after forty-three days and the United States did not launch another one. A program that produces a single object and then ceases looks, from a distance, like a failure. The question worth asking is: failure at what?
Geoffrey Bowker and Susan Leigh Star, in their 1999 book Sorting Things Out, have a useful phrase for what is going on here: classification as infrastructure. The idea is that categories like success, failure, program, capability, hardware, and paper study do not passively describe the world. They organize it. They determine what gets funded, what gets remembered, what gets written into the next budget, and what falls off the ledger. SNAP-10A is remembered as a minor entry in a list of cancelled programs because the category of "program success" was defined, by the Atomic Energy Commission and NASA and the Bureau of the Budget, as producing a fleet. In a different classification scheme, one that treated demonstrating capability as the success metric, SNAP-10A would be remembered as the only time the United States ever pulled it off.
The capability did not go to the graveyard with the program. It went to the Atomic Energy Commission, which had built the reactor, and to the national laboratories where the engineering expertise lived: Atomics International, Los Alamos, Oak Ridge. When SNAP-10A's funding ended, the people who had designed it did not evaporate. They kept working, on other reactors, for other programs, many of which would also get cancelled. The capability to build space fission reactors remained in the United States after 1965. The institutional permission to actually use it did not.
Capability and permission are not the same thing.
Capability is a physical and human fact: it is expertise, infrastructure, fuel supply, manufacturing tooling, testing facilities, and the workforce that knows how to operate them. Permission is a political fact: it is appropriations, authorization, a launch approval regime, insurance, indemnification, and a mission whose owners want the capability exercised. The United States after 1965 had capability. It did not have permission. It would spend the next six decades maintaining the first while waiting on the second.
The people who maintained capability across those six decades, across twelve presidencies, across multiple total reorganizations of the federal research landscape, are the subject of this essay. They are mostly not famous. Several of them will not be named here because this essay does not know their names. One of them is already on this page. His name is James Webb.
If SNAP-10A was about power (a reactor that sits on a spacecraft and makes electricity), NERVA was about propulsion. Different idea, same underlying technology. You take a nuclear reactor, you run liquid hydrogen through it, the hydrogen heats to several thousand degrees, and you expel it through a rocket nozzle. The exhaust velocity is roughly twice what you get from the best chemical rockets. This means, in practical terms, that a nuclear thermal rocket is the difference between a Mars mission that takes nine months and a Mars mission that takes three and a half.
NERVA (Nuclear Engine for Rocket Vehicle Application) was the project that was supposed to build one. It ran from 1955 to 1973, which is eighteen years. It spent, in inflation-adjusted dollars, something in the neighborhood of ten to twelve billion. It conducted twenty-three reactor firings at a dedicated test complex at Jackass Flats, Nevada. Its most powerful test, Phoebus-2A in 1968, produced over four thousand megawatts of thermal output for twelve minutes. That is more thermal power than any reactor has ever produced before or since. The program demonstrated that nuclear thermal rockets work, that they are reliable, that they are survivable, and that the engineering of them is broadly understood.
The cancellation is sometimes described as a failure of NERVA, which is misleading, because NERVA was not failing. NERVA was a working demonstration of a technology that no longer had a mission to attach to. Apollo was ending. The Mars program that NERVA had been sized for was not going to happen. The upper-stage nuclear booster that NERVA was supposed to enable was, in a post-Apollo fiscal environment, not fundable. When a technology no longer has a patron mission, the technology is cancelled regardless of whether it works.
What NERVA had instead of Lal and Myers's three features was a quieter thing. It had institutional sponsors. In the United States Congress, the Joint Committee on Atomic Energy (a permanent oversight body that handled all nuclear matters from 1946 to 1977) functioned as NERVA's legislative patron. Senators Clinton Anderson of New Mexico and Howard Cannon of Nevada, both of whom represented states that housed NERVA facilities, protected its appropriations against repeated efforts to cut them. The program kept running. Not because it passed the Manhattan Project test. Because it had friends in Congress who were willing to fight for it, and because the facilities it had built were in their districts.
This is the pattern that will repeat. A President resistant to broader capability. An administrator who engineers the conditions under which the President encounters the capability's strongest case. Appropriations approved, one fiscal year at a time, through a combination of executive persuasion and legislative patronage. When NERVA was cancelled in 1973, the capability went into storage. The fuel, the designs, the test infrastructure, the workforce: all of it. Some of it is still in storage now. Some of it is about to come out.
Between NERVA's cancellation and the next serious American space-reactor program, ten years passed. The capability sat. The workforce aged. Some of it retired. Some of it drifted into terrestrial nuclear work, into weapons design at the national labs, into the commercial nuclear industry as it was collapsing under the weight of Three Mile Island and changing economics. The institutional memory thinned. When the next program started, in 1983, many of the people who had built NERVA were no longer available to advise it.
SP-100 was a Reagan-era program to build a 100-kilowatt space fission reactor. It was jointly managed by NASA, the Department of Defense, and the Department of Energy. It was, in its original framing, a civilian science program: reactors for deep-space probes, for lunar bases, for Mars missions. In its operational reality, it was an artifact of the Strategic Defense Initiative.
SDI, announced by Reagan in March 1983, was the grand plan to build a space-based missile defense system. Its technical requirements (space-based interceptors, directed-energy weapons, orbital sensors) produced a power-demand profile that could not be met by solar arrays. A 100-kilowatt reactor would have been useful. A megawatt-class reactor would have been better. SP-100 was sized for the low end of this requirement, and its budget tracked the SDI appropriations cycle with considerable fidelity. When SDI funding rose, SP-100 rose. When SDI funding was renegotiated, SP-100 was renegotiated. When SDI was formally descoped in the early 1990s, SP-100 lost its primary strategic rationale.
The program was cancelled in 1994. It had spent roughly one billion dollars. It had produced no flight hardware. It had, however, produced a substantial body of reactor design work (particularly on high-temperature lithium cooling and thermoelectric power conversion), which migrated, on cancellation, into the national laboratories and the Department of Energy's reactor programs. The design work did not disappear. It shifted file cabinets.
The boundary object frame explains how SP-100 could be sustained for a decade with no clear prime mission. Each community of practice held its own piece. Tap through to see what SP-100 was, depending on who you asked.
Every community had a stake. When the Department of Defense stake was pulled in the early 1990s, the other communities could not hold the program alone. And yet the technical work did not die when the program died. It was absorbed by the communities that had been interpreting it. DOE kept the reactor physics. DoD kept the radiation-hardened electronics. NASA kept the thermal management research. The boundary object fragmented back into its interpretive communities, and each community held onto its piece.
This is how capability survives a program's death. Not through a single institution's protection, but through multiple institutions each treating the capability as theirs for different reasons. The capability becomes polysemic. You can't kill all the meanings at once.
The idea, proposed by NASA in 2003, was to build a Jupiter mission using nuclear electric propulsion. Not nuclear thermal, which uses a reactor to heat propellant. Nuclear electric: a reactor generating electricity, which runs an ion engine, which produces very low thrust but at extremely high efficiency. The spacecraft would have weighed roughly thirty tons, carried a 200-kilowatt reactor, and used the slow but efficient ion propulsion to reach Jupiter, orbit Callisto, depart for Ganymede, orbit it, depart for Europa, and orbit it too. All on a single mission, which is something no Jupiter mission has ever done or is likely to do with chemical propulsion.
JIMO was going to be the first flagship-class demonstration of space-nuclear propulsion in actual use. It was the mission that NERVA had been designed for, thirty years late and with a different propulsion architecture. It was also a trillion-dollar idea dressed as a four-hundred-million-dollar program.
The program was cancelled in 2005, after roughly four hundred and sixty-three million dollars had been spent. The reasons were multiple: the Bush administration's Vision for Space Exploration redirected NASA toward lunar return; the technical scope of JIMO was assessed as outrunning the budget; and the reactor requirements (a space-qualified 200-kilowatt system) were recognized as requiring a development program that dwarfed the spacecraft program itself. JIMO was, to borrow Lal and Myers's phrase, flagship-first in a domain where flagship-first does not work.
What happens instead is that every new program assumes it will resolve these questions on the way to launch. Every program fails to do so, because resolving them requires legislative action or cross-agency regulatory rulemaking that takes longer than the program itself. The questions defer. And then the program is cancelled, and the questions defer again, and the next program inherits an even longer backlog of unresolved regulatory ambiguity.
JIMO, when it was cancelled, had not even begun to address its launch approval regime. It had not commissioned the environmental impact statements it would eventually need. It had not secured indemnification. It had assumed, as every program before it had assumed, that these things would get worked out during the program's long development arc.
The reactor work, on cancellation, went to the Department of Energy's Office of Naval Reactors (the same organization that runs the propulsion reactors on American submarines and aircraft carriers). Naval Reactors has the unusual institutional property of being simultaneously under the Department of Energy (as a civilian matter, sort of) and under the Department of the Navy (as a military matter, sort of), which means it is difficult to cancel from any single direction. It also has nearly seventy years of continuous operational reactor experience. When JIMO's reactor design work moved there in 2005, it was entering the most institutionally stable reactor organization in the United States government. Twenty-one years later, that work is still there. Some of it has surfaced, in modified form, inside the design studies for the current lunar fission surface power program. The fragments keep coming back.
The last cancellation in this sequence is recent enough that some of the people involved are still in the jobs they held when it happened.
DRACO (Demonstration Rocket for Agile Cislunar Operations) was a joint DARPA and NASA program, started in 2020, to build a flight-test nuclear thermal propulsion demonstrator. Unlike NERVA, which had been sized for Mars missions, DRACO was sized for cislunar operations: maneuvering between Earth orbit and lunar orbit. Unlike SP-100 and JIMO, which were nuclear electric, DRACO was a return to nuclear thermal: the NERVA lineage, revived with high-assay low-enriched uranium fuel instead of the highly enriched uranium NERVA had used.
The program had a prime contract with Lockheed Martin, a reactor subcontract with BWX Technologies, a targeted 2027 flight date, and approximately four hundred and ninety-nine million dollars in combined DARPA and NASA funding. It produced substantial engineering work (reactor designs, HALEU fuel qualification, ground-test infrastructure, a flight-test spacecraft concept) before the FY2026 President's Budget Request, released on May 30, 2025, cancelled it.
The reason given was economic. The DARPA deputy director, Rob McHenry, explained that launch costs had fallen to the point where the efficiency gains from nuclear thermal propulsion no longer justified the development expense. This is a specific, narrow, and technically defensible claim. Chemical rockets had become cheap enough, thanks to SpaceX, that the business case for expensive nuclear alternatives had softened. What McHenry said was accurate, within the frame of what he said.
What he did not say is also worth noticing.
Forrest Morgan and James Acton have written, in different forms, about something they call warhead ambiguity: the difficulty for one nation's radar operators to distinguish between a scientific satellite and a weapons platform on the same kind of bus, in the same orbit, made by the same contractors. DRACO, although a civilian science-adjacent program, was managed by DARPA, which is a defense research agency. Its technology overlaps with Project Pele, which is a defense reactor program. Its fuel supply chain overlaps with every other American advanced reactor initiative, civilian or military. The civil-and-defense distinction that American space-nuclear policy has insisted on since SPD-6 in 2020 is, in the DRACO case, a paperwork distinction. The actual work is fungible.
The civil-and-defense distinction that has been load-bearing fiction for sixty years is about to become just fiction.
NSTM-3 directs parallel NASA and Department of War reactor programs, with shared fuel supplied by DOE, with common components, with OSTP coordinating the whole thing. The fiction is thinning. Space-nuclear work was never really civilian or military. It was always a capability that both communities drew on. That is about to be declared out loud.
Five programs. Sixty-one years. Twenty billion dollars, give or take. One flight. Forty-three days of operation.
The conventional way to tell this story is as a catalog of failures. The bolder version is that these programs were not failures at all. They were vessels. Each one carried the capability forward for the length of its funded life, and when it was cancelled, the capability migrated. Expertise to the labs. Designs to successor programs. Infrastructure to storage. Fuel supply to the next application. Regulatory experience to the accumulating backlog of unresolved questions.
Nobody architected this migration. It was the accumulated effect of thousands of individual decisions by program managers, lab directors, civil servants, legislative staffers, and contractors, each making locally rational choices to preserve what they had when their program was cancelled. The capability portfolio that the United States will attempt to cash in with NSTM-3 was not built by any single person. It was held by many people, across many cancellations, for reasons that did not coordinate.
James Webb was one of those people. He was an important one. He was not the only one. And he is the one worth paying attention to here, because the pattern he represents, the institutional figure who holds capability across presidencies that would not preserve it on their own, is the pattern that made all of this possible, and the pattern that may not be available much longer.
We should probably talk about the tape.
The meeting was recorded. The tape was declassified and released by the JFK Presidential Library in 2001. The recording is unusually clear for its era. Anyone with an internet connection can listen to it. The substance of the meeting is an argument between the President and his NASA Administrator about what NASA is for.
Sixty-three days after the Rice speech, on the morning of November 21, 1962, a meeting convened in the Cabinet Room of the White House. It was Tuesday. The President was there. James Webb was there. So were Robert Seamans (Webb’s deputy), Brainerd Holmes (NASA’s chief of manned space flight), Hugh Dryden (NASA’s deputy administrator), Jerome Wiesner (the President’s science advisor), David Bell (the director of the Bureau of the Budget), and several others. The meeting had been called because of a story in Time magazine about a rift between Webb and Holmes over NASA’s priorities. Kennedy wanted the rift resolved. The recording is unusually clear for its era. Anyone with an internet connection can listen to it.
Kennedy is assassinated thirteen months after the Cabinet Room meeting. Webb serves Lyndon Johnson for five more years and resigns in October 1968, nine months before Apollo 11 lands. He never sees the thing he made.
It is tempting to tell the story we have just told as the story of a great administrator. The institutional hero who saw what his President could not see, fought the necessary fight, and built the apparatus that would carry the capability forward for generations. This is an emotionally satisfying narrative, and parts of it are true. Webb was an unusually capable administrator. He did win many of the arguments he needed to win. The capability apparatus that existed when he left NASA was substantially of his construction.
But telling the story this way commits the error this essay has been trying to avoid, which is replacing Kennedy hagiography with Webb hagiography. The "great man" frame is part of what makes institutional work invisible in the first place, because it assigns credit for collective effort to a single named figure, which means everyone else in the story becomes an anonymous helper or a passive environmental condition.
Here is a list, deliberately incomplete, of the people who held American space nuclear capability across the six decades between SNAP-10A and NSTM-3:
That is not all of them. It is not close to all of them. Most of the people who held the capability are genuinely anonymous, in the sense that they do not appear in the histories because they were doing the kind of work that does not get written into histories. They were running test facilities, writing appropriations justifications, maintaining reactor design codes, training graduate students, preserving institutional memory in the form of notebooks and conversations and quiet mentorship. The apparatus held because a great many people, mostly without coordinating, each did their small piece of the holding.
Webb is the face of this pattern because he operated at a visible level and because his specific battle with Kennedy is documented on tape. He is not the pattern's unique author. The pattern predates him (NERVA started in 1955, under Eisenhower, before Webb was at NASA) and postdates him (he resigned in 1968, fifty-eight years before NSTM-3 was issued). What he did brilliantly was occupy a particular institutional role with particular political skill at a moment when the role's influence was unusually large.
The apparatus is not Webb. The apparatus is what held.
If you take the view these case studies have been working toward, what happened between 1965 and 2026 is not a story of failure. It is a story of holding. The United States, across twelve presidencies, nine changes of party, and four major reorganizations of its research enterprise, held a space nuclear capability portfolio without exercising it. The capability was available the entire time. It was not used.
Several things follow from this observation.
The first is that the usual framing of the American space nuclear record is inverted. The conventional story is that the United States tried and failed, repeatedly, to build space reactors. The story these case studies have been telling is that the United States tried, repeatedly, not to build space reactors while preserving the ability to do so. The programs were not attempts at deployment. The programs were the vehicles through which capability was held. When each vehicle was cancelled, the capability migrated to the next.
The second is that the people who held the capability did not always know they were holding it. Webb, in 1962, would not have used the phrase "sixty-year option." He was arguing for "preeminence in space" on a horizon he could actually see, maybe ten or fifteen years out. Anderson and Cannon were not architecting a 2026 lunar reactor. They were protecting facilities in their states. Finger was not preserving a capability portfolio for a grandchild generation. He was keeping a program alive that he believed was technically valuable. The sixty-year hold is an aggregate effect. It is what emerges when many people, over many years, each do the smaller thing in front of them.
The third is that this kind of hold depends on specific institutional conditions. It requires legislative committees that exist long enough to build patronage relationships with programs. It requires a civil service protected enough to retain technical memory across administrations. It requires national laboratories with enough budget autonomy to keep workforce intact between programs. It requires agencies that can absorb cancelled work rather than dispersing it. It requires a federal research enterprise that is, to a meaningful degree, insulated from the shortest cycles of political time. The 1950s and 1960s had these conditions robustly. The 2020s have them in uneven and, in several cases, degraded form.
This is the point in the essay where the writer is supposed to tell you what this means for NSTM-3. The writer declines. What this means for NSTM-3 is a question that depends on conditions the essay cannot assess from here. Whether Steven Sinacore gets to keep his fifteen-person program intact through 2030. Whether the HALEU supply ramps on schedule. Whether a Tier III presidential launch authorization gets tested without the INSRB blowing up around it. Whether Congress holds its end of the appropriations through an election cycle. Whether the civil servants assigned to execute NSTM-3 are the kind of administrators who can engineer a 2026 analogue of Jackass Flats, at a moment when Jackass Flats-style engineering is harder than it used to be.
What the essay can say, standing in April 2026 and looking back along the sixty years, is this: the option is being exercised. The thing Webb argued for in the Cabinet Room in 1962, and that several hundred less-famous people held in trust for the six decades after that, is now being cashed in. Whether the cashing-in produces an operational reactor on the Moon by 2030, or merely adds NSTM-3 to the stack of documents in the same file cabinet as SP-100 and JIMO and DRACO, is not the most interesting question about the moment.
The most interesting question is how long it has taken the United States to get here, and what it has cost, and who paid.
We should probably end where we started.
On September 12, 1962, President John F. Kennedy stood at Rice Stadium and delivered a sentence about the Moon that has outlived him and almost everyone who was there to hear it. The sentence is carved, now, into the stadium's commemorative plaza. Tourists take pictures of it. Schoolchildren visit it on field trips. The sentence has done well for itself.
In the audience that afternoon was a fifty-five-year-old career administrator named James Webb, who had pushed, through Theodore Sorensen, for the broader framing the speech performed: the nuclear-power pairing, the "and the others, too" tag that the President would not be quoted on. Webb lived to see Apollo 11 land. He died in 1992. His name was not on anything famous until 2002, when the administrator of NASA at the time decided to rename the Next Generation Space Telescope after him.
On April 14, 2026, in a ballroom at the Broadmoor Hotel, Michael Kratsios delivered NSTM-3 to an audience of roughly six hundred people. Steven Sinacore stood near the podium. Afterward, Sinacore went back to his office at NASA Headquarters, where he runs a fifteen-person program on a firm-fixed-price posture with a 2030 delivery date, reporting to an administrator who has been in the job for ten months and may or may not be in the job by the time LR-1 launches, if LR-1 launches. Sinacore will not talk, in interviews, about whether he thinks 2030 is realistic. He will only say, in the phrase he has now repeated to several dozen audiences, that the lack of an operational space nuclear reactor is not a technology problem, it is an execution problem.
The execution has been going on for sixty-one years. It may go on for another sixty-one. It may not. Webb did not know whether his bet would pay off either. He arranged the conditions for the bet and then left the room.
That is what this essay has been about. Not the reactor. Not the memorandum. Not the capability, in the technical sense. It has been about the kind of work that sets up the conditions under which a later moment becomes possible, and the kind of person who does that work, and what it costs to hold such conditions open for long enough that the later moment arrives.
That is how it works. That is how it has always worked. The question worth asking, now, is whether it still does.
Now that you have read what was held and how, you can try to cash the option. The April 14 memorandum authorizes a mid-power reactor for the lunar surface by 2030. It defers the 100 kWe target to "the 2030s" with no binding milestone. It does not address the megawatt class at all.
This is a calculator for what those distinctions actually mean. Pick a destination. Load a preset or tap what you want to do. Watch the tiers.
Each destination is its own problem. Tap the one you want to build against.
Configurations drawn from the 2026 program landscape. Tap to load, then adjust below.
Reference: a household microwave draws about 1 kWe.
Select components above and the power breakdown appears here.
The April 14 memo authorizes the second. It gestures at the third. The first is a ground test. The fourth is not in the document.
In August 2025, Acting NASA Administrator Sean Duffy demanded 100 kWe by the first quarter of fiscal year 2030.
In March 2026, Jared Isaacman announced SR-1 Freedom as a 20 kWe pathfinder, and the 100 kWe figure quietly dropped out of the active plan.
On April 14, NSTM-3 ratified the 20 kWe floor as the programmatic baseline and moved the 100 kWe target into "extensibility" language for the 2030s.
The rhetoric is Manhattan-scale. The mechanism is not.
The execution has been going on for sixty-one years.
Build a mission first. When you have components selected, you can share the whole thing natively, copy the summary, grab a deep-linked URL, or download a PNG social card.