Two Lunar Systems—and the Problem of the Wrong Plug

Part 6 of 32 · Series date: September 7, 2026

In an imagined future emergency, a rover reaches a nearby base with almost no power left. Help is close. A charger is ready.

The plug does not fit.

That would be a foolish reason to lose a valuable machine. If people were aboard, it could be much worse. Yet anyone who has traveled with the wrong phone adapter understands how easy it is for useful systems to fail at their edges.

As lunar programs grow, those edges will matter. NASA's Artemis effort and the International Lunar Research Station may develop different hardware, networks, and rules. The question is how much they can share when sharing makes sense.

Working together does not mean being identical

Two railway companies do not need the same logo to use the same track gauge. Two phones do not need the same brand to exchange a message.

Engineers call this ability interoperability. It means separate systems can work together through agreed connections and rules.

On the Moon, it could involve a data format, a docking interface, a radio signal, or a way to request help. It could also involve simple details, such as whether a robot can grab a standard handle on another team's cargo.

NASA's LunaNet specification is one effort to define shared approaches for lunar communications and navigation. It provides a technical foundation for compatible services. It is not proof that all future lunar systems will use it. NASA: LunaNet specification

Standards are offers and agreements before they become habits.

Why separate systems may emerge

Space programs serve science, industry, national goals, and public pride. They answer to different governments and face different rules. Some designs also make different choices for good technical reasons.

So it is unlikely that one grand blueprint will cover every lunar activity.

CNSA's ILRS partnership material describes its own framework for international work. The existence of that framework does not tell us, by itself, whether every interface will clash with Artemis-linked systems. Actual designs must be compared. CNSA: ILRS partnership guide

We should resist two easy stories. One says all programs will blend into a happy world project. The other says separate programs must become enemies.

Between those extremes is a lot of useful room.

Start with the least glamorous agreements

Imagine two science teams using nearby sites. Neither wants the other's landing plume to cover its equipment in dust. Both need to know when a spacecraft will arrive.

They could share a schedule and basic hazard information without sharing every design secret.

Now imagine a researcher needs to compare measurements from both teams. Agreed units, time stamps, and location references could make the data far more useful.

These are small acts of cooperation with large practical value. They reduce surprise.

NASA's description of the Artemis Accords includes transparency, assistance, and efforts to avoid harmful interference. The Accords reflect the commitments of their participants; they are not a rulebook accepted by every country. NASA: Artemis Accords

Even limited agreement can help if it answers a real operational need.

The plug fits. Now what?

Give our stranded rover an adapter. The metal parts connect. Have we solved the problem?

Only if the systems also agree on what passes through the cable. The right shape is no help if the power is wrong. A message that says the rover is ready must mean the same thing to both machines. Both crews need to know who can switch the flow on and how to stop it.

A useful rescue test would include those steps, with teams using their own gear and normal instructions. Can they complete the handoff? Do they spot a bad connection? Can either side halt the process safely?

This is where a shared standard earns its keep. It turns an offer of help into a service that can actually reach someone. The paperwork matters because, in the end, it has to work in a person's hands.

Rescue should be designed before rescue is needed

A friendly promise is valuable. A tested ability to help is better.

Suppose one crew can reach another but cannot connect an air supply. Or suppose a rescue vehicle has no safe way to carry an injured person from a different suit system.

The problem is not solved by goodwill alone. Teams need to know what their equipment can actually do.

That suggests a sensible order: identify likely shared needs, choose a few common interfaces, and test them. An emergency drill can expose a flaw while nobody is in danger.

Not every system needs to be universal. Some may be too costly to adapt. The point is to make conscious choices instead of discovering the limits in a crisis.

The risk of locking everyone out

A base that controls a vital service could gain great influence. Think of the only useful data relay or the only prepared landing area near a work site.

That influence could support a business. It could also create a weak point if access is uncertain or a single provider fails.

These are future risks to plan for, not claims about a current lunar monopoly. Open interfaces and more than one route can make a network more resilient. They can also make it easier for small teams to join.

The best lunar economy would have room for a new idea without requiring its maker to build an entire space program first.

A good neighbor in a hard place

The Moon will not make human politics disappear. It will make the costs of some mistakes harder to ignore.

Return to the rover with the fading battery. This time, the crews have practiced together. They know the cable, the checks, and the stop command.

Power begins to flow.

A small agreement made on Earth has just become a very large act of neighborliness on the Moon.