1. The lesson of the ants

T.H. White’s The Once and Future King includes a memorable passage where the young Arthur is transformed into an ant and learns that ants live by schedule and collective purpose. A desktop program needs some of that discipline. Not the conformity, but the patience. Large space projects fail when they pretend the schedule is shorter than it is.

Entry 208 covered insurance and liability. This entry proposes a timeline from the second keeper platform to the first operational desktop.

2. Years zero to two: second platform design and build

The second keeper platform, described in entries 177–184, is the pathfinder. Design and build take roughly two years, assuming the first platform has already provided lessons. Customer commitments and government support are secured in parallel.

Milestone: second platform launch.

3. Years two to four: platform operations and learning

The second platform operates for at least two years. This period proves the interfaces, the attachments, the operations model, and the customer pipeline. It generates data that feeds into the desktop design. Some attachments may be upgraded or swapped.

Milestone: platform operations review with ten prioritized design changes for the desktop.

4. Years four to seven: desktop design and build

With platform heritage in hand, the desktop enters detailed design, procurement, assembly, and test. This is the longest and most expensive phase. Modules are built by primes and suppliers, then integrated on the ground before launch.

Milestone: desktop critical design review.

5. Years seven to eight: launch and assembly

The desktop modules launch and assemble on orbit. This phase includes rendezvous, docking, deployment, and commissioning. It is high-risk and requires close operations support.

Milestone: desktop initial operational capability.

6. Years eight to ten: early operations and revenue

The desktop begins serving early customers. Revenue is lower and more variable than the mature estimate. The focus is on proving reliability, building references, and refining operations.

Milestone: positive cash flow from operations.

7. Total span

From the start of second platform design to positive cash flow is roughly ten years. This is long for a startup but normal for a major space infrastructure project. The timeline can be compressed with more money or more risk, but not dramatically.

What this changes

  • A notional desktop program spans roughly ten years from second platform design to positive cash flow.
  • The second platform provides two years of operational learning before desktop build begins.
  • Launch and assembly are high-risk phases requiring dedicated operations support.
  • The next leisure entry can define the first desktop milestone more sharply.