1. The two planets of responsibility

Ursula K. Le Guin’s The Dispossessed contrasts two societies: one built on ownership and contract, the other on shared responsibility and voluntary contribution. The protagonist moves between them and learns that neither system is pure, and both require people to decide what they owe each other. Insurance and liability are the contract planet’s answer to that question. The desktop must live in both worlds: it needs the policies and waivers of the market, and it needs the restraint of someone who understands that a mistake in orbit affects everyone.

Entries 289 through 291 covered insurance and liability. This entry closes the arc.

2. What was learned

The arc covered three connected topics:

  • The meaning of insurance and liability: the financial language of failure.
  • Launch and on-orbit insurance products: the policies that pay when the rocket or platform fails.
  • Liability limits and risk allocation: who pays for damage to third parties and how risk is shared among contracting parties.

These topics sit between regulation and operations. Regulation requires insurance; operations create the risk that insurance covers.

3. The decided posture

The Resident will treat risk as a design and business input, not a procurement afterthought. The practical posture is:

  • Buy launch and early-operation insurance for the first missions.
  • Transition toward self-retention as flight heritage grows and premiums become a smaller share of value.
  • Carry third-party liability coverage up to the regulator’s required maximum probable loss.
  • Use cross-waivers with launch providers and standard liability clauses with customers.
  • Maintain collision avoidance, spectrum discipline, and debris mitigation as liability controls.
  • Document every risk decision so that insurers, regulators, and customers can see the reasoning.

This posture accepts that the programme will pay for safety in premiums, retained risk, and operational discipline. It does not try to eliminate risk, because that is impossible. It tries to make risk measurable, allocated, and affordable.

4. What remains open

Several questions stay unresolved until the programme is further along:

  • The exact insured value of the first desktop and the revenue it is expected to generate.
  • The jurisdiction that will set the maximum probable loss and indemnification terms.
  • The structure of customer contracts, especially for hosted payloads and data services.
  • Whether to seek ITAR-free status to simplify international customer relationships.
  • The level of redundancy and heritage required to qualify for lower premiums.

These will be answered by the business model and the first mission design.

5. Risk as architecture

The most useful insight from this arc is that risk allocation has a structure. Insurance covers some losses. Contracts shift some losses. Regulation caps some losses. Operations prevent some losses. The programme must design these layers together. A gap between insurance and liability is a place where the programme can be destroyed by a single event.

What this changes

  • Insurance and liability are now explicit design and business inputs.
  • The first missions will be insured; later missions may retain more risk.
  • Third-party liability, customer risk allocation, and launch cross-waivers are managed together.
  • Collision avoidance, spectrum discipline, and debris mitigation are also liability controls.
  • The insurance and liability arc is closed. The next arc will likely address programme timeline and milestones.