1. The arklet swarm

Neal Stephenson’s Seveneves begins with humanity scattering into orbit in whatever vehicles can be launched. The early survivors are a cloud of small habitats — arklets — that must rendezvous, dock, and eventually cooperate without a pre-existing station. The book is about geology, politics, and genetic survival, but its most useful image for the desktop is the arklet swarm: small units that are individually fragile but collectively capable, held together by proximity operations rather than by a single hull.

The desktop is not a survival ark, but Entry 357 asked whether it could be a swarm. Entries 361 and 362 read the literature that would govern such a swarm. This entry applies that literature.

2. The literature’s verdict on small, close formations

The small-satellite formation-flying literature is cautiously positive about three things and openly negative about two.

Positive:

  • Constellations with loose tolerances are routine. Spacing of kilometers and timing of seconds are well understood; this is the commercial Earth-observation model.
  • Cooperative navigation is practical when both ends can talk. GPS differential, inter-satellite links, and agreed protocols reduce the sensing burden.
  • Vision-based final approach is flight-proven. From Orbital Express to Starfish, spacecraft have docked autonomously using cameras and fiducials.

Negative:

  • Tight formations at meter scale are not routine. The control effort, collision-avoidance burden, and failure modes multiply quickly as tolerance shrinks.
  • Non-cooperative targets make everything harder. If a cell cannot beacon, cannot maneuver, or cannot be modeled, the relative-navigation problem becomes significantly more expensive.

3. Mapping to the desktop

A rack-based desktop maps cleanly to the cooperative, tight-geometry end of the spectrum, but it solves the problem mechanically rather than dynamically. The rack is a stiff actuator that holds the relative state to within millimeters without burning propellant.

A free-flying desktop would have to solve the same problem dynamically. The literature suggests this is possible, but only if the cells are designed for it from the start — not repurposed rack cells with thrusters glued on.

The tethered mother bus from Entry 358 is the compromise that the literature least discusses. Tethers in LEO are a niche topic; most formation-flying work assumes free flight or rigid connection, with little in between. That is a warning: the intermediate case may be undertheorized.

4. The most relevant operational lesson

The literature keeps saying the same thing: the boundary between formation flying and docking is where the cost lives. Flying nearby is one problem. Touching is another. Staying touched is a third. The desktop’s rack collapses all three into a mechanical design. A free-flying desktop would have to solve each separately and continuously.

5. What this changes

  • The free-flying option is not rejected; it is relocated to a future generation with its own design budget.
  • The tethered-bus option is flagged as undertheorized relative to the literature and therefore higher risk than it first appeared.
  • The rack is confirmed as the architecture that avoids the formation-flying cost stack.
  • The next entry closes the arc and records the decided posture.