Gateway: learn from an architecture that changed

Gateway was developed as a small lunar-orbit station supporting exploration, science and transfers between visiting spacecraft. Its planned Power and Propulsion Element supplied electrical power and maneuvering capability, while the Habitation and Logistics Outpost, or HALO, provided pressurized working space and supporting systems. International contributions were part of the broader architecture. These functions explain why the concept was more than a single capsule parked near the Moon.

The historical design placed Gateway in a near-rectilinear halo orbit. That orbit has changing distance from the Moon and differs from a low circular orbit. Choosing an orbit changes transportation, communications and operating requirements, so the station’s location was part of its system design. The accompanying Gateway HALO image is a rendering of the planned configuration. It documents design intent, not an operational station photographed in lunar orbit.

NASA’s June 2026 inspector-general memorandum describes the move away from Gateway as a staging location toward a Moon base. A September NASA discussion describes work to repurpose HALO power and avionics for a lunar surface technology demonstration. Those statements do not establish that HALO has landed, or that an entire orbital station can be placed on the surface without redesign. Preserve the original project history while clearly identifying the changed direction.

An original comparison makes the engineering issue visible. An orbital electronics box designed for one mounting arrangement may face different loads, dust exposure and heat-transfer conditions on a surface platform. Reusing the box could save development effort, but engineers still need to compare the new requirements with its qualified capabilities. A component that worked under one set of assumptions is not automatically suitable under every other set. Reuse is a proposal to evaluate, not a waiver of qualification.

Compare future options fairly

Imagine that a project has already spent sixty budget units on hardware. Adapting it for a new task would cost twenty more units, while a new alternative would cost fifteen for equivalent verified capability. The sixty units already spent do not disappear, but they also cannot be recovered by choosing the more expensive future option. The comparison must consider remaining costs, risks, schedule and actual usefulness. These fictional figures are not NASA contract estimates.

The lower apparent price is not automatically decisive either: perhaps the new alternative has an untested interface or a longer delivery time. Document the assumptions and compare the options on the same requirements. Gateway’s history is valuable precisely because exploration plans evolve. It teaches learners to read engineering diagrams as dated proposals, follow the status of individual components and assess what changed without erasing the people and technical work behind the earlier design.