1. The cloud ark that steered itself

Neal Stephenson’s Seveneves returns as the recalled work because the arklets and Endurance must maintain their orbits and avoid debris without constant ground supervision. A LEO desktop must do the same: counteract drag, respond to conjunction warnings, and manage its own propellant budget.

This entry wonders about autonomous orbit maintenance and collision avoidance.

2. What autonomous orbit maintenance means

Autonomous orbit maintenance is the platform’s ability to keep itself in the desired orbit without waiting for ground instruction. The spectrum includes:

  • Ground-planned: all stationkeeping and reboost burns are scheduled from the ground.
  • Ground-triggered: ground commands a burn; the platform executes.
  • Autonomous execution: ground approves a burn plan; the platform chooses the exact time within a window.
  • Autonomous planning and execution: the platform detects orbit decay, plans a burn, and executes it within policy.
  • Fully adaptive: the platform optimizes its orbit strategy based on drag forecasts, mission needs, and propellant state.

For the desktop, the realistic region is autonomous planning and execution within ground-approved policy.

3. What autonomous collision avoidance means

Autonomous collision avoidance is the platform’s ability to respond to a conjunction threat without waiting for ground. The spectrum includes:

  • Ground-planned: all collision avoidance maneuvers are designed and approved on the ground.
  • Ground-triggered: ground sends a maneuver command; the platform executes.
  • Autonomous execution: ground approves a maneuver template; the platform executes when a threshold is crossed.
  • Autonomous decision: the platform receives conjunction data, evaluates the risk, and decides whether to maneuver within pre-approved rules.
  • Fully autonomous: the platform detects the threat itself and acts.

For the desktop, the realistic region is autonomous execution of pre-approved maneuver templates, with ground notification.

4. Why this matters

Ground contact windows are not aligned with every conjunction or every drag event. A close approach may occur during a ground silence. Drag may accumulate faster than predicted after a solar storm increases atmospheric density. If the platform can act on its own, it can maintain orbit and avoid collisions without waiting.

5. What could go wrong

  • The platform overreacts to a low-risk conjunction and wastes propellant.
  • The platform underreacts because its risk model is wrong or the data is stale.
  • A collision avoidance maneuver creates a new conjunction with another object.
  • Autonomous stationkeeping conflicts with customer payload operations.
  • Ground loses visibility because the platform maneuvers without reporting in time.

6. What this changes

  • Autonomous orbit maintenance and collision avoidance are not about removing ground oversight but about compressing response time.
  • The desktop can probably handle drag makeup and low-risk conjunction responses autonomously.
  • The next entry will wonder about maneuver planning and propellant conservation.