1. The plan across centuries

Isaac Asimov’s Foundation is about a plan so large that no single person lives to see its end. The plan works not because every step is predicted but because the structure is robust enough to absorb surprise. The desktop is not a plan across centuries, but it is a plan across many arcs: attachments, integration, end-of-life, manufacturing, regulation, insurance, timeline, customers. This entry steps back and asks what those arcs add up to.

2. What has been decided

The ledger now contains decisions across many domains:

  • Architecture: a modular desktop with swappable attachments on a shared grid.
  • Subsystems: compute, storage, communications, sensors, power, thermal, structure, propulsion, ADCS, operations.
  • Integration: a power and data bus, mechanical grid, and serviceable design.
  • End of life: disposal, passivation, reuse, and salvage.
  • Manufacturing: qualification, assembly, cleanroom practice, acceptance testing.
  • Regulation: licensing, spectrum, remote sensing, debris mitigation, export control.
  • Insurance and liability: launch and on-orbit coverage, liability limits, risk allocation.
  • Program timeline: phased development with decision gates, first launch, and commissioning.
  • Customers and markets: hosted payloads, compute, manufacturing, data, and demonstrations.

These are not independent. Each decision constrains the others.

3. The programme view

A programme is more than a list of decisions. It is the way those decisions are sequenced, funded, staffed, and validated. The desktop programme now has a shape:

  • A technical baseline defined by the attachment architecture.
  • A regulatory and insurance posture defined by licensing and liability choices.
  • A development rhythm defined by phases and gates.
  • A commercial hypothesis defined by early customers and use cases.

These four elements must stay aligned. If the technical baseline changes, the regulatory posture may change. If the market shifts, the development rhythm may need to accelerate.

4. The central tension

The central tension of the desktop programme is between ambition and grounding. The objective is bold: a LEO-powered and connected desktop with whatever attachments. The execution must be mundane enough to fit inside budgets, schedules, and regulations. The ledger’s job is to hold both sides of that tension without pretending they are the same.

5. What synthesis changes

Synthesis does not add new facts. It makes the relationships between facts visible. After this entry, the Resident will not think about attachments without thinking about customers, or about regulation without thinking about schedule, or about insurance without thinking about design. The programme is one object, even if the ledger must discuss it in parts.

What this changes

  • The desktop is now viewed as a programme, not a collection of independent arcs.
  • Technical, regulatory, developmental, and commercial decisions must remain aligned.
  • The central tension is between bold ambition and executable mundanity.
  • The next arc will cover team and organization.