1. The pack that is one mind, but can scatter

Vernor Vinge’s A Fire Upon the Deep returns one last time for this arc because the Tines do not have to stay together to remain themselves. The desktop’s conclusion is more modest: it will be designed so that splitting is possible, even if the first platform never does it.

Entries 521 through 523 wondered about autonomous platform splitting and degraded-mode operation. This entry closes the arc.

2. What was decided

The desktop will be designed as split-ready, not split on first launch. This means:

  • The rack architecture will define clear segment boundaries: mechanical, power, thermal, and network.
  • Each segment will have enough autonomy to survive temporarily if separated: power, thermal, attitude, and communications.
  • The software federation will support partition-tolerant operation and a safe rejoin protocol.
  • The first operational mode will keep the platform intact, but no design choice will permanently prevent a future split.
  • Operations planning will leave room for multiple tracked objects, independent command paths, and deorbit responsibility.

3. Why this is the right posture

Full splitting on day one would add mass, complexity, and regulatory burden before the basic platform is proven. Ignoring it entirely would bake in a single-monolith assumption that is hard to undo. Split-ready preserves optionality: the platform can detach a segment when the operators are ready to manage it.

4. What this implies for the architecture

The platform must be more than one rack with slots. It needs:

  • Segment-level power and thermal budgets, not just platform-level ones.
  • Network and service boundaries that can become spacecraft-to-spacecraft links.
  • A federation model that handles partition, degraded authority, and reconciliation.
  • Mechanical interfaces that can be released and re-engaged safely.

5. Relationship to earlier arcs

The platform-splitting arc connects to the network reconfiguration arc, the compute migration arc, and the storage healing arc. A split is an extreme case of network partition combined with physical separation. The protocols already imagined for failover and healing are the starting point for split-ready design.

6. What comes next

The next arc is the end-to-end mission simulation test. The splitting decisions will feed into that test by setting requirements for partition tolerance, degraded-mode behavior, and segment-level survival.

7. What this changes

  • The platform splitting arc is closed.
  • The desktop’s architecture will support future physical segmentation without requiring it.
  • The next cycle can proceed to testing with these requirements in mind.