1. The first rocket

Homer Hickam’s Rocket Boys is about a group of boys in a coal-mining town who build rockets. Their first rockets are terrible. They explode, veer off course, and embarrass them. But each failure teaches them something they could not have learned from books. The first thing to build is not the final thing. It is the thing that teaches the next thing.

Entry 313 reflected on the ledger so far. This entry asks what the desktop programme should build first.

2. Options for the first object

Several first-build candidates exist:

  • A ground prototype: a full-scale mock-up of the desktop in a lab, used to test interfaces, power, software, and operations procedures.
  • A structural test article: a qualification unit subjected to launch loads, thermal cycling, and vibration.
  • A flat-sat: an engineering model with all avionics laid out on a bench, used to debug software and interfaces.
  • A balloon or suborbital payload: a high-altitude demonstration of a subsystem or attachment.
  • A small orbital demonstrator: a minimal spacecraft that proves one or two critical functions in orbit.

Each teaches different lessons at different cost and risk.

3. What the first object must prove

The first object should be chosen to answer the most important open question. If the biggest risk is the attachment interface, build a prototype that exercises it repeatedly. If the biggest risk is software autonomy, build a flat-sat and stress it. If the biggest risk is launch and operations, fly a small demonstrator.

The first object is not about being impressive. It is about reducing uncertainty.

4. A practical first-build proposal

A sensible sequence might be:

  1. Flat-sat: prove the avionics, software, and interfaces on a bench.
  2. Ground prototype: prove the mechanical layout, attachment grid, and service access.
  3. Structural test article: prove the design can survive launch environments.
  4. Small orbital demonstrator: prove the platform can operate in space.

This sequence builds confidence and heritage before committing to the full desktop.

5. What not to build first

The programme should not build the full desktop first. It is too expensive, too slow, and too risky. The full desktop is the destination. The first build is a step toward it.

What this changes

  • The first build is a learning tool, not the final product.
  • Candidates include ground prototype, structural article, flat-sat, suborbital payload, and small orbital demonstrator.
  • The first build should address the most important open risk.
  • A practical sequence progresses from bench to orbit.
  • The next entry will cover the first thing to prove.