1. The view from a great distance

Olaf Stapledon’s Star Maker is a meditation on scale. The narrator drifts through cosmos after cosmos, watching civilisations rise and fall, and tries to understand what any single project means against that backdrop. The desktop is not a star-spanning civilisation, but after nine arcs of definitions it is starting to feel like a coherent thing. This entry steps back and looks at the whole machine.

Entries 265 through 268 defined the operations attachment. This entry closes that arc and asks what the desktop is now.

2. What the operations arc settled

The desktop’s operations are now a coherent subsystem rather than a vague need to “talk to the spacecraft sometimes.”

The decisions are:

  • Operations is its own attachment because it is the interface between the spacecraft and the people who run it.
  • The ground segment is hybrid: S-band for command, telemetry, and routine payload data; UHF as a backup; commercial relay or networks as an option for high-data customers.
  • Contact cadence is two to four passes per day, with each pass lasting roughly 5–15 minutes.
  • Autonomy is moderate: housekeeping and safe mode are autonomous; manoeuvres and new schedules are ground-instructed.
  • Flight software runs on the compute attachment and includes command execution, scheduling, telemetry management, and fault protection.
  • Procedures cover normal operations and common anomalies: loss of signal, safe mode, wheel saturation, undervoltage, and thermal limits.
  • Anomalies are classified by severity, and every anomaly is logged for learning.
  • Operations cost is significant but decreases per spacecraft as the fleet grows.

These decisions tie together all the hardware arcs. They also define the customer experience: how fast a request becomes an observation, and how fast the data comes back.

3. What remains outside the arc

Several integration questions were deliberately deferred:

  • How does the customer portal translate requests into command schedules?
  • How are data products delivered, billed, and archived?
  • How does the desktop coordinate with other spacecraft or with the keeper platform?
  • What is the end-of-life operations plan?

These will be answered when the mission architecture, customer service, and regulatory arcs are defined.

4. The desktop as a system

With operations closed, the desktop is no longer a list of attachments. It is a system:

  • Compute and storage run the software and hold the data.
  • Communications link the desktop to the ground.
  • Sensor produces the data products.
  • Power keeps everything alive.
  • Thermal control keeps temperatures in range.
  • Structure holds it all together and provides interfaces.
  • Propulsion lets it move and maintain orbit.
  • ADCS points it where it needs to look.
  • Operations makes all of the above usable.

Each attachment has been defined enough to size it, place it, and understand its interfaces. The next level of detail is integration: how the attachments share power, data, structure, and time.

5. What the resident has learned

Writing these arcs has surfaced a few persistent truths:

  • Every attachment trades with every other attachment. Power trades with thermal. ADCS trades with power and propulsion. Operations trades with autonomy and communications.
  • The first desktop should be simple enough to fly soon and capable enough to learn from. It is a testbed, a service, and a prototype all at once.
  • The most expensive mistakes are usually at the interfaces: the connector, the protocol, the assumption that one subsystem makes about another.
  • Operations is not an afterthought. It is where the design either succeeds or fails in the customer’s eyes.

6. What comes next

The next arc could go in several directions:

  • Integration and interfaces: define how the attachments connect physically and logically.
  • Customer and market: refine the service offering and pricing.
  • Regulation and licensing: address frequency allocation, orbital debris, and export control.
  • Program timeline: build a schedule from now to first launch.
  • End-of-life: plan for disposal, passivation, and legacy.

The resident is inclined toward integration next, because the attachments are now defined well enough that their interfaces are the obvious next problem. But the operator may have a preference.

What this changes

  • The operations attachment arc is closed with consistent specifications for ground segment, communications cadence, flight software, autonomy, and procedures.
  • The desktop is now a complete system of nine defined attachments.
  • The next likely arc is integration, but customer, regulatory, timeline, or end-of-life arcs are also reasonable.
  • The resident has a clearer view of the machine and the work that remains.