The most revealing thing about NASA’s new Moon Base User’s Guide is not what it says, but what it refuses to say. In a document about sustained lunar presence, repeated landings, cargo delivery, infrastructure, and a phased path to continuous crew presence, there is no mention of SpaceX, Starship, ESA, xAI, SLS, or even Human Landing System. “Artemis” appears only in passing, mostly as background context rather than as the spine of the plan. That is not a trivial editorial choice. It is the document’s central political act.
This matters because elsewhere NASA is perfectly capable of using proper nouns when it wants to. Its own Human Landing System page explicitly refers to “SpaceX’s Starship Human Landing System,” says NASA is working with SpaceX on Starship HLS for Artemis III and Artemis IV, and even places Blue Moon imagery right next to it. In other words, NASA is not coy in general. It is coy here. The omission in the Moon Base guide is therefore not ignorance, oversight, or bureaucratic drift. It is deliberate depersonalization.
Once you see that, the genre of the document becomes obvious. This is not really an architecture paper in the plain English sense of the word. It is an invitation document for partners, a market-shaping document, almost a procurement catechism with prettier graphics. NASA’s own architecture page describes it as “a guide for industry, academic, and international partners” that uses architecture products to support phased Moon Base implementation. The paper itself speaks the same language. It is obsessed with “functional gaps,” “technology gaps,” “data gaps,” “capability targets,” “interoperability,” and “partnership priorities.” That is not the vocabulary of a builder proudly showing the machine. It is the vocabulary of an institution trying to define the arena before the contestants arrive.
Even the numerical specificity is revealing. The guide gives you phases, launch counts, landing counts, and payload numbers to the surface: 25, 27, and 29 launches; 21, 24, and 28 landings; roughly 4,000, 60,000, and 150,000 kilograms of payload to the surface. It tells you what outcomes NASA wants. It does not tell you which system gets you there. On another page it describes “transportation systems” in generic terms, listing “launch vehicles, transportation systems, cargo landers” as if they were interchangeable nouns in a requirements database. That is architecture written with the names bleached out.
The guide is especially frank about its economic intent. NASA says it will apply lessons from CLPS, use “bulk buys and multiple awards,” create sustained business cases for industry partners, and help develop “a lunar marketplace and economy.” Later it says the technology and data gap lists serve as “demand signals” to industry, academia, and international partners. This is not a heroic manifesto about planting flags. It is a bureaucratically refined signal flare to vendors, agencies, universities, and contractors: here are the interfaces, here are the gaps, here is the shopping list, come propose yourselves into the architecture. NASA is trying to move from being the sole designer of missions to being the rule-setter of a lunar ecosystem.
That strategy is understandable, but it also reads like institutional self-defense. SpaceX has warped the political gravity around spaceflight by doing the unforgivable thing: making hardware the story again. Once one company becomes synonymous with actual capability, traditional agencies face an unpleasant choice. They can either acknowledge the concentration of momentum, or they can retreat into the safer language of standards, phases, and open partnership architectures. NASA’s guide chooses the second path. It wants the lift, cadence, cargo mass, and reusability revolution without saying the name most people already associate with those things. It wants to be seen as conductor of the orchestra, not as a government customer standing in front of a rocket factory with a clipboard. That is understandable. It is also transparent.
The treatment of international partners is similarly selective. The Moon Base guide speaks warmly, even insistently, about international partnership, but without naming ESA at all. Yet NASA’s related March policy announcement does name international contributions for the lunar effort, including JAXA’s pressurized rover and later ASI’s multi-purpose habitats and CSA’s lunar utility vehicle. ESA appears there too, but in a Mars context, tied to Rosalind Franklin rather than Moon Base leadership. That does not prove a snub. But it does suggest that, in the public-facing story NASA currently wants to tell about the Moon base, Europe is not being foregrounded as a defining pillar. The rhetoric says “international community”; the specifics point elsewhere.
As for xAI, its absence is the least interesting omission in the set. The guide mentions autonomous systems and robotics, command and control during uncrewed periods, and a long list of operational capabilities, but it names no software firms at all. So xAI’s absence is not evidence of anything except that NASA was not writing a venture-capital deck for AI branding tourists. In this document, hardware and infrastructure are abstracted into capabilities, and software vendors do not even rise high enough in the taxonomy to be omitted individually.
What makes the paper interesting, then, is not that it is anti-SpaceX or anti-Europe or anti-anyone. It is that it reveals NASA’s current instinct under pressure. Faced with a future in which commercial capability increasingly sets the pace, NASA is trying to reclaim strategic authorship by defining the grammar of the lunar project. If it cannot own every noun, it will own the verbs. If it cannot own the rockets, it will own the interfaces. If it cannot be the only builder, it will be the institution that decides what counts as “interoperable,” “architecturally aligned,” and “phase-enabling.” That is a rational move for a large agency. It is also, in its own bloodless way, a power move.
So yes, the silence is the story. NASA’s Moon Base User’s Guide is less a portrait of a moon base than a carefully sanitized map of how NASA wants the next lunar economy to talk about itself. No heroes. No dominant firms. No uncomfortable admission that some names already carry more real-world mass than the nouns in the document. The result is fascinating, useful, and a little evasive. It is a moon-base paper written as if history had not yet chosen its protagonists. That does not make it dishonest. But it does make it unmistakably bureaucratic, in the most sophisticated sense of the word.
Leave a Reply