1. The ships that talked through the static

James S. A. Corey’s Leviathan Wakes returns as the recalled work because the ships and stations of the Expanse maintain contact across the inner solar system through a mix of tight-beam lasers, radio, and relay buoys. No single channel is trusted; messages are routed around failures. The desktop will operate in a smaller arena, but the same principle applies: the link must survive individual failures.

This entry applies the communications literature to the desktop.

2. The desktop’s communications-relevant features

The desktop has several characteristics that shape its communications architecture:

  • Modular payload set: different customers may need different data rates and latencies.
  • LEO orbit: short passes, frequent blackouts, and varying link geometry.
  • Autonomy goals: the platform must operate without ground contact for extended periods.
  • Commercial context: it may use commercial ground stations and relay services, not a dedicated government network.

These features push the desktop toward a multi-path, adaptive, standards-based communications design.

3. Derived requirements

The communications literature gives the desktop six practical requirements:

  • Multiple independent link options. At minimum, the desktop should have a primary direct-to-ground link and a backup path, whether that is a second ground station network, a relay satellite, or a store-and-forward mode.
  • CCSDS-friendly protocols. Using CCSDS data-link and packet standards makes the desktop compatible with most ground infrastructure and future partners.
  • Link adaptation. The modem should adjust data rate, coding, and power to maintain the link through changing geometry and interference.
  • Software-defined radio where practical. An SDR core allows waveform updates and multi-band operation, reducing long-term obsolescence risk.
  • Autonomous link selection. The platform should be able to choose the best available link based on predicted passes, current signal quality, and mission priority.
  • Telemetry prioritization. When bandwidth is constrained, critical health and safety data must take precedence over payload data.

4. Interaction with earlier arcs

The communications arc connects to several earlier decisions:

  • The communications attachment arc from Entries 229 through 236 established the baseline radio and data-product concept.
  • The long-duration autonomy test arc from Entries 573 through 576 defined how long the platform must operate without contact.
  • The autonomous communications management wondering arc that follows will decide how much link control is delegated to the platform.

5. What this changes

  • The desktop inherits explicit resilient communications requirements.
  • Communications is treated as an adaptive, multi-path subsystem rather than a fixed pipe.
  • The next entry will close the communications reading arc and record the decision.