1. The primer that carries its own instruction set

Neal Stephenson’s The Diamond Age returns as the recalled work because its Young Lady’s Illustrated Primer is a self-contained teaching device that works whether its owner is in a mansion or a slum. A separated desktop segment must be similarly self-contained: enough of the plan, the software, and the energy budget packed into a smaller hull so that it can keep operating without the rest.

This entry lists what the desktop would have to provide for autonomous platform splitting to work.

2. Physically separable segments

The rack must be designed so that segments can detach and reattach:

  • Mechanical interfaces. Each segment needs its own structure, attitude control, and thermal radiators.
  • Power autonomy. Solar arrays, batteries, and power management must support the segment’s reduced load.
  • Thermal autonomy. Radiator area and heater capacity must scale to the segment’s smaller mass and power.
  • Communications autonomy. Each segment needs an antenna and radio, or a relay arrangement with siblings.

3. Logical separation and federation

Software must know how to become two platforms:

  • Service partitioning. Workloads, storage replicas, and network services must split cleanly along segment boundaries.
  • Quorum and authority rules. The federation must decide which segment owns which decisions after a split.
  • Rejoin protocol. When segments come back together, they must reconcile state, synchronize clocks, and merge services without conflict.
  • Degraded-mode policy. Each segment must know which services to keep, pause, or shed based on its resources.

4. Operational and regulatory provisions

The ground side must also be ready:

  • Tracking and conjunction screening for each segment.
  • Independent command paths in case one segment loses its primary radio.
  • Licensing clarity for split, rejoined, and retired segments.
  • Deorbit responsibility for segments that cannot be recovered.

5. What this changes

  • Platform splitting requires investment in modular power, thermal, communications, software federation, and operations infrastructure.
  • Many of these provisions are useful even if the platform never splits: they improve survivability and flexibility.
  • The next entry will decide whether the desktop should design for this capability.