1. The pack that comes back together
Vernor Vinge’s A Fire Upon the Deep returns as the recalled work because the Tines do not just split; they also reassemble, and the reunion is not automatic. The desktop’s platform-splitting arc decided that segments could separate. This arc wonders whether they can come back together without a human pilot.
This entry wonders what autonomous rejoining and docking of split platform segments would mean for the desktop.
2. The current assumption
So far the desktop has been imagined as one rack. If a segment is ever detached, the default assumption is that it either stays detached for a mission or is recovered by a separate servicer. Autonomous rejoining adds a new path: a segment leaves, performs a task, and returns to the main platform under its own control.
3. What rejoining adds
Autonomous rejoining would change several things:
- Reusable detachments. A segment could be sent out and absorbed back, rather than being a one-way trip.
- Mission modularity. The platform could temporarily specialize: one segment carries a sensor or tool, returns, and swaps roles.
- Risk management. A segment that develops a fault could be brought back for repair or retirement instead of abandoned.
- Operational complexity. Rejoining requires the platform to track, communicate with, and safely approach its own segment.
4. Why this is worth wondering about now
The desktop does not need autonomous rejoining on day one. But the split-ready architecture decided in Entries 521 through 524 only becomes fully useful if rejoining is at least possible in principle. A segment that can leave but never return is a disposable asset. A segment that can return is a reusable tool.
5. What this changes
- Autonomous rejoining is identified as a long-term capability that completes the splitting story.
- The wondering arc will explore what it changes, what it needs, and whether the desktop should design for it.
- The next entry will look at the consequences in more detail.