Article reader Listen + reading controls
Article reader
Preparing the reader…
Reading settings
Lunar infrastructure starts with interoperability¶
The Defense Advanced Research Projects Agency (DARPA) has announced the 10-Year Lunar Architecture (LunA-10) capability study. The effort will examine how a future lunar economy might move from isolated, self-sufficient projects toward shareable and scalable infrastructure for power, communications, logistics, and other services.
The timing of that architectural work matters. Interoperability is easiest to praise before systems exist and hardest to achieve after every provider has optimized a private solution.
Early architecture shapes later options¶
When an environment is immature, building a complete end-to-end system can be rational. A provider controls interfaces, schedules, and performance. The result works without waiting for an ecosystem.
As activity grows, those independent systems can become expensive islands. Each brings its own power assumptions, communications protocols, connection mechanisms, data formats, and support model. Shared infrastructure then requires adapters, redesign, or abandonment of prior investments.
LunA-10 creates an opportunity to identify the interfaces that should become common before the architecture hardens.
Interoperability is more than a technical standard¶
A specification can define voltage, connector geometry, data format, or service interface. It cannot by itself settle who maintains the standard, who certifies conformance, how scarce capacity is allocated, or how a provider changes an interface without stranding users.
Those are governance questions. They determine whether interoperability survives commercial competition and mission urgency.
Systems engineering often distinguishes functional, physical, and operational views. Lunar infrastructure needs all three. Two components may connect physically yet remain operationally incompatible because their timing, reliability, authority, or failure assumptions differ.
Treat interfaces as shared knowledge¶
An interface document is a boundary object among spacecraft designers, power providers, communications engineers, operators, investors, and government users. It must be precise enough to build against while carrying enough rationale to adapt responsibly.
Star and Griesemer's research on boundary objects helps explain the challenge. Shared artifacts coordinate groups that hold different expertise and interests. Their usefulness depends on being recognizable across communities without erasing local requirements.
Every critical interface should therefore preserve:
- the need it serves and alternatives considered;
- technical requirements and tolerances;
- assumptions about environment and operations;
- failure and recovery behavior;
- security and trust boundaries;
- ownership and change process; and
- evidence required for conformance.
The rationale matters because lunar systems will encounter conditions and users the first designers cannot fully anticipate.
Design graceful failure across providers¶
Shared infrastructure creates efficiency and new dependencies. A communications, positioning, or power service may support many missions. Resilience requires understanding how failures propagate and which functions must continue locally.
Architecture studies should ask not only how services connect, but how they degrade. Can a user recognize reduced confidence? Can one provider fail without cascading across the network? Can essential functions operate temporarily without the shared service? Who coordinates recovery when several organizations are affected?
The International Organization for Standardization systems-lifecycle standard emphasizes interfaces, stakeholder needs, verification, validation, and lifecycle processes. Those disciplines become especially important when no single program owns the whole environment.
Preserve competition above stable interfaces¶
Common infrastructure need not eliminate innovation. Good interfaces can concentrate competition where it creates value while keeping basic connection and safety predictable. The aim is not to standardize every design choice. It is to decide which boundaries should remain stable enough for an ecosystem to form.
LunA-10 is a study, not yet an infrastructure program. That makes it the right moment to surface incompatible assumptions, identify shared services, and define how architectural knowledge will be governed.
The Moon may be distant, but the organizational lesson is familiar. Complex ecosystems are not integrated at the end. They become integrable because leaders treat interfaces, decision rights, and shared evidence as first-order design choices from the beginning.
Sources and research trail¶
- Defense Advanced Research Projects Agency, “A Framework for Optimized, Integrated Lunar Infrastructure” (August 15, 2023).
- Defense Advanced Research Projects Agency, LunA-10 capability study.
- International Organization for Standardization, ISO/IEC/IEEE 15288:2015, Systems and Software Engineering—System Life Cycle Processes (2015).
- Star and Griesemer, “Institutional Ecology, ‘Translations’ and Boundary Objects” (1989).
- Carlile, “A Pragmatic View of Knowledge and Boundaries” (2002).