1. Many eyes on the code

Eric Raymond’s The Cathedral and the Bazaar argues that open software gets better when more people look at it. The desktop’s software stack should borrow that spirit where possible. Not everything can be open — some customers will want closed payloads — but the core platform software benefits from standardization, inspection, and reuse.

Entry 197 summarized the desktop arc. This entry looks under the hood at the software that makes the desktop work.

2. Layer one: flight software

The lowest layer is the flight software that runs the bus: attitude control, power management, thermal control, fault detection, and communications. This layer needs to be deterministic, fault-tolerant, and certifiable. NASA’s Core Flight System is one proven framework. A commercial desktop might use a similar architecture or a hardened real-time operating system.

This is not the place to experiment. The flight software is the layer you trust before you trust anything else.

3. Layer two: platform services

Above flight software sits the platform services layer: resource allocation, scheduling, health monitoring, data routing, and attachment management. This layer abstracts the hardware so that attachments and customer payloads do not need to know the details of the bus.

It is the operating system of the desktop. Customer payloads interact with it through well-defined APIs.

4. Layer three: customer runtime

Customer payloads need a place to run. For compute customers, this might be containers or virtual machines. For sensor operators, it is a tasking and data-processing environment. For manufacturers, it is the control software for printers and mills.

The desktop should support multiple runtimes, isolated from each other and from the platform services layer. Security and resource quotas are critical here.

5. Layer four: ground control and customer interfaces

Ground operators and customers interact with the desktop through web interfaces, APIs, and command-line tools. The customer interface is where the desktop becomes a product: customers reserve capacity, upload tasks, monitor progress, and download results.

This layer should feel like a cloud provider, not a spacecraft control room.

6. Automation and autonomy

A manual desktop is an expensive desktop. The software stack must support automated operations: routine health checks, power balancing, payload scheduling, anomaly response, and software updates. Over time, more decisions should move from ground operators to on-board software.

This is how the operations team stays small even as the desktop grows.

What this changes

  • The desktop software stack has four layers: flight software, platform services, customer runtime, and ground/customer interfaces.
  • Flight software is conservative and proven; customer interfaces are modern and API-driven.
  • Multi-tenant isolation and automation are essential.
  • The next leisure entry can look at the robotics layer.