1. The drones in the garden

Douglas Trumbull’s Silent Running sends three small drones — Huey, Dewey, and Louie — to tend a garden in space. They have no fixed rails, no rack, no common frame. They float, bump, cooperate by proximity, and fail one at a time. The film is sentimental about ecology and bleak about loneliness, but the drones are the useful image: a spacecraft that is not one machine but a swarm of small machines that occasionally touch.

This entry wonders whether the desktop could be built that way.

2. The fixed-rack assumption

From Entry 005 onward the desktop has assumed a rigid rack: cells slide in, share power and data through a backplane, and rely on the rack for structure, thermal grounding, and pointing stability. That assumption has served the programme well. It is easy to draw, easy to test, and easy to explain.

But it also imposes a hidden contract: every cell must fit the rack, every cell must arrive at the rack, and the rack must survive everything. The rack is the single point of structural integration. If it is wrong, the whole desktop is wrong.

3. The free-flying alternative

What if there is no rack? Each cell is a self-contained spacecraft: its own power, its own thermal control, its own communications, its own micro-propulsion. When cells need to share power, data, or cooling, they dock. When they do not, they fly in formation nearby.

The potential advantages:

  • No common structural load: a cell failure does not load or unload its neighbors.
  • Scalability by addition: new capability arrives as a new free flyer, not as a redesign of the rack.
  • Orbital replacement: a failed cell can be swapped without touching the rest of the assembly.
  • Distributed risk: no single rack flaw grounds the entire mission.

The potential disadvantages:

  • Each cell pays the spacecraft tax: every cell needs ADCS, propulsion, power regulation, and thermal control that the rack used to amortize.
  • Formation keeping consumes propellant: even a loose formation needs station-keeping burns; over years that budget adds up.
  • Docking is now a mission-critical event: no rack means every cooperation begins with a rendezvous and a mechanical mate.
  • Data and power sharing require physical contact or wireless transfer: both are heavier and less efficient than a backplane.

4. Why it is probably wrong for the first generation

The free-flying desktop trades integration complexity for operational complexity. That is a good trade when the mission is long, the cells are numerous, and replacement is routine. It is a bad trade when the goal is to prove that a small set of attachments can share a power bus and a thermal sink on the first flight.

The rack is, at root, a way to buy certainty with mechanical preload. The free-flying architecture buys flexibility with propellant and software. The programme is not yet rich enough to spend that currency casually.

5. What it teaches

Even if the first desktop keeps its rack, the wondering is not wasted. It separates two ideas that had become fused:

  • Physical aggregation: cells share a structure.
  • Logical aggregation: cells cooperate as one system.

The rack provides both. A future desktop could provide logical aggregation without physical aggregation — cells that belong to the same computer but live meters apart, docking only when bandwidth or power demands it. The ISS already does this in a limited way with visiting vehicles; a desktop could do it as a design principle.

6. What this changes

  • The rack is reconfirmed as the right first assumption, but no longer as the only conceivable architecture.
  • Free-flying cells are recorded as a second-generation option, triggered when the desktop grows beyond what a single rack can hold or replace.
  • The next wondering will look at an intermediate case: a tethered mother bus that keeps some aggregation while relaxing the rigid rack.