1. The unstable throne

Cixin Liu’s The Three-Body Problem is obsessed with orbits that look stable until they are not. The three-body system produces moments of apparent regularity, then sudden ejection. The lesson is not that elliptical orbits are evil; it is that their behavior over long intervals is non-obvious. Any architecture that depends on a clever orbit must first survive the orbit’s cleverness.

This entry wonders whether the desktop should live on a highly elliptical orbit instead of LEO.

2. The LEO default

The desktop has assumed LEO from the start: low launch energy, frequent ground passes, benign radiation by deep-space standards, and a thermal environment dominated by Earth albedo and eclipse. It is the default for small satellites and for good reason.

But LEO also has constraints: ground stations see it for only a few minutes per pass, atmospheric drag requires station-keeping, and the field of view to any given point on Earth changes continuously. For some missions — persistent Earth observation, communications relay, or slow-data monitoring — a LEO desk spends most of its time over the wrong hemisphere.

3. The highly elliptical alternative

A Molniya or Tundra-style orbit spends most of its period high over one hemisphere, then drops low and fast over the other. The high apogee means long dwell, large Earth view, and reduced drag. The low perigee means the launch energy is not much worse than LEO, and the perigee pass can be used for high-rate downlink.

The potential advantages for the desktop:

  • Long loiter: a high apogee of 40,000 km gives hours of continuous visibility over a region.
  • Less drag: the high apogee dominates the orbit; lifetime is longer for the same ballistic coefficient.
  • Different thermal environment: fewer eclipses, more stable Sun aspect, but also more extreme hot/cold swings.

The potential disadvantages:

  • Radiation: the desktop would pass through the Van Allen belts twice per orbit, accumulating dose quickly.
  • Communications latency: round-trip light time to apogee is hundreds of milliseconds, making tight closed-loop control from the ground harder.
  • Thermal cycling: the long eclipse-free periods are followed by long eclipses; the thermal transients are larger than in LEO.
  • Navigation and tracking: a non-circular orbit is harder to propagate and requires more ground tracking support.
  • Launch and deployment: rideshare to a HEO transfer is less common than LEO rideshare.

4. Why it is probably wrong for the first generation

The first desktop’s value proposition is “a computer that consumes more than 500 watts in orbit, with attachments that can be swapped.” That proposition does not require hemisphere-scale dwell. LEO gives the shortest path to flight heritage, the cheapest launch, and the simplest operations.

HEO is a mission-specific optimization, not a first-generation platform choice. It becomes interesting only when the desktop’s customers need persistence over a region more than they need frequent access or low radiation.

5. What it teaches

Orbit is a customer-facing parameter. The same hardware in LEO is an agile compute node; the same hardware in HEO is a regional sentinel. The choice changes the thermal design, the radiation tolerance, the communications architecture, and the operations rhythm. The desktop is not orbit-agnostic; it is currently LEO-optimized.

6. What this changes

  • HEO is recorded as a future variant, not a first-generation baseline.
  • The radiation and latency implications of HEO are added to the long-lead trade space.
  • The next wondering will look at the other classic alternative: GEO and MEO.