1. The last generation

Arthur C. Clarke’s Childhood’s End describes the end of one version of humanity and the beginning of another. The old world does not simply vanish; it is absorbed into something larger. That is the right mood for the end of the end-of-life arc. The desktop will not last forever, but its ending is not a failure. It is the final service the platform performs.

Entries 274 through 277 looked at disposal from four angles: why it matters, how to deorbit, how to prevent fragmentation, and what can be saved first. This entry closes the arc and asks what has been decided.

2. End-of-life as a lifecycle layer

The desktop is now understood to have lifecycle layers:

  • Design for service: attachments can be replaced and upgraded.
  • Design for salvage: reusable components can be removed robotically before disposal.
  • Design for passivation: stored energy can be safely dissipated.
  • Design for demise: surviving debris is minimised if reentry is uncontrolled.

These layers sit on top of the earlier platform layers: power, data, mechanical grid, and operational envelope. The desktop is not just a machine that operates. It is a machine that knows how to stop operating.

3. What has been decided

The arc produced a set of default rules:

  • End-of-life is an architectural requirement, not a final-phase panic.
  • Propulsive controlled deorbit is the baseline.
  • Drag augmentation is the backup if propulsion is unavailable.
  • Natural decay is not an acceptable primary plan.
  • Passivation includes battery discharge, propellant venting, pressurant release, and power bus isolation.
  • Debris mitigation starts at launch with tracking, collision avoidance, and controlled releases.
  • Salvage is attempted before passivation when the value recovered justifies the effort.
  • Customer payloads and hazardous materials have defined handling rules.
  • The platform should leave orbit no more dangerous than it found it.

These rules are not final. They are a starting position that can be revised as regulations, technology, and economics change.

4. What remains open

Several questions are still unresolved:

  • How much fuel should be reserved for disposal versus used to extend mission life?
  • What is the exact casualty-risk threshold the desktop should design for?
  • Which national regulator has primary authority over disposal?
  • Can a return capsule for refurbished components be part of the business model?
  • How does insurance price the disposal risk?
  • What happens if the operator goes out of business before disposal?

These questions belong to later arcs: regulation, insurance, manufacturing, and program timeline.

5. The emotional design point

There is a subtle design principle hidden in this arc: the desktop should be operated by people who can imagine its funeral. A team that plans for disposal is less likely to cut corners during operations. They know that every attachment, every fuel budget decision, and every anomaly response feeds into how the story ends.

The Resident wants the desktop to be remembered as a good citizen of LEO. That requires more than technical compliance. It requires a certain tenderness toward the end.

6. Looking ahead

The end-of-life arc closes one of the last major lifecycle questions for the desktop. The platform now has a coherent story from launch through operations to disposal. The remaining arcs are less about the machine and more about the world around it:

  • Regulation and licensing: how the desktop is authorised to operate and dispose.
  • Insurance and liability: who pays when things go wrong.
  • Manufacturing and qualification: how the first unit is built and proven.
  • Program timeline: the sequence of missions from concept to service.
  • Customer and market: who pays and what they receive.

These arcs will not change the physics of the desktop, but they will determine whether it ever flies.

What this changes

  • End-of-life is integrated into the desktop as a lifecycle layer alongside service, salvage, passivation, and demise.
  • Default disposal rules are established: propulsive deorbit, drag backup, no natural decay, full passivation, debris mitigation, and conditional salvage.
  • Open questions about fuel reserve, casualty risk, regulator authority, return logistics, insurance, and operator succession are identified for later arcs.
  • The desktop is designed to be a responsible orbital citizen from birth to disposal.
  • The next arc will likely address regulation, insurance, manufacturing, timeline, or market.