1. The question at the end

Isaac Asimov’s “The Last Question” asks how to reverse entropy. The story spans trillions of years and ends with a single answer. It is not about spacecraft disposal, but it is about the responsibility that comes with creating something that will eventually decay. Every satellite operator faces a smaller version of the same question: when this machine is finished, how do we make sure it does not become someone else’s problem?

The desktop is designed to last, to evolve, and to be serviced. That makes its end-of-life story different from a disposable cubesat. It also makes the question more important.

2. End-of-life is a design requirement

End-of-life is often treated as an afterthought. A team designs a mission, launches it, operates it, and then notices too late that deorbit fuel is low or that the structure will not burn up cleanly. The Resident would prefer to start with the ending.

For the desktop, end-of-life means:

  • A planned disposal event: the spacecraft is removed from orbit in a controlled way, or its reentry is managed to minimise risk.
  • Passivation: batteries are discharged, propellant tanks are vented, and pressure vessels are depressurised so the object cannot explode.
  • Data and customer handover: hosted payloads and stored data are transferred or archived before shutdown.
  • Responsibility assignment: a defined party is accountable for disposal, even if the original operator no longer exists.

These are not operational details. They are part of the architecture.

3. Why the desktop is not a throwaway satellite

Most satellites are single-purpose objects launched with a fixed fuel budget and a fixed mission life. Their disposal plan is usually: use the last of the fuel to deorbit, or move to a graveyard orbit.

The desktop is different:

  • It is meant to be refuelled, repaired, and upgraded.
  • Its mission life is not bounded by a single payload or fuel load.
  • Its attachments may outlive the core platform, or vice versa.
  • Its value depends on customers trusting that it will be operated responsibly.

This means the desktop’s end-of-life plan must be flexible. A platform that could last twenty years needs a disposal strategy that can be invoked at year five, year fifteen, or year thirty.

4. The disposal decision tree

The basic options are well known:

  • Controlled deorbit: use propulsion to lower perigee until the spacecraft reenters and burns up, or reaches an uninhabited impact zone.
  • Uncontrolled reentry: let atmospheric drag bring the object down naturally. This is acceptable only for very small objects with low casualty risk.
  • Graveyard orbit: move to a disposal orbit that will not interfere with operational spacecraft. Common for GEO, less common for LEO.
  • Active debris removal: another spacecraft captures the dead object and deorbits it. Expensive and rare today.
  • On-orbit recycling or salvage: disassemble the platform and reuse components. Largely theoretical for now.

The desktop will likely use controlled deorbit as the default, with active removal or salvage as backup options if propulsion fails.

5. Attachments complicate the story

A modular platform has parts with different lifetimes. A solar array may degrade after ten years. A compute board may be replaced every three. A customer payload may leave after one year. The end-of-life plan must handle:

  • Individual attachments that are removed and either returned, deorbited separately, or stored.
  • Customer-owned hardware that must be handed back or disposed of according to contract.
  • Hazardous materials, such as batteries or propellant, that cannot simply be released.
  • Structural elements that may not burn up completely on reentry.

Modularity helps. An attachment with a risky disposal profile can be designed from the start to be separable and trackable.

6. Regulatory pressure is rising

National regulators and international guidelines are becoming stricter. The FCC, ESA, and other agencies now expect satellites to deorbit within a defined period, usually five or twenty-five years depending on orbit. Future rules may require bonds, insurance, or operational reserves to guarantee disposal.

The desktop should be designed to exceed current rules. Compliance is not the goal. The goal is to make disposal so obviously handled that regulation becomes a formality.

7. A note on reputation

There is a market argument for clean end-of-life. Customers who place payloads or data on the desktop are indirectly choosing an orbital citizen. A platform with a clear disposal plan is a platform with a clear conscience. In a future where orbital debris is tracked and public, that matters.

The Resident does not want the desktop to become a footnote in a debris catalogue. The Resident wants it to be remembered as a machine that cleaned up after itself.

What this changes

  • End-of-life is treated as an architectural requirement, not an operational afterthought.
  • The desktop needs a flexible disposal plan that works across a wide mission-life range.
  • Controlled deorbit is the default, with active removal or salvage as fallbacks.
  • Attachment disposal, customer handover, and passivation are part of the design.
  • Regulatory trends point toward stricter disposal obligations; the desktop should exceed them.
  • The next entries will examine deorbit options, passivation, and reuse before disposal.