1. The objective is not the demo
William Gibson’s Neuromancer is not about space, but it is about a world where compute and connectivity are the real geography. The matrix exists everywhere and nowhere. The keeper’s original objective is similar in spirit: a LEO-powered and connected desktop with whatever attachments. The demo is just a way to start building the credibility and capability to get there.
Entry 172 listed four post-demo options: contact, deorbit, minimoon, and platform. Not all of them serve the desktop objective equally well.
2. Contact demo
A contact mission proves the keeper can attach to something. For the desktop objective, this is directly relevant. Attachments are how the desktop grows: solar panels, radiators, antennas, storage cells, and manufacturing tools all need to be attached to a host. If the keeper cannot attach, the desktop cannot expand.
Verdict: highly aligned with the objective.
3. Deorbit demo
A deorbit mission proves the keeper can change an object’s trajectory. This is impressive and useful for debris removal, but it is only indirectly related to the desktop. The desktop needs to hold position and host payloads, not push things into the atmosphere. The propulsion and control lessons transfer, but the mission itself is a tangent.
Verdict: moderately aligned. Good for credibility, not essential for the desktop.
4. Minimoon mission
A minimoon mission is the romantic core of the keeper idea: capturing a natural object and turning it into a platform. For the desktop objective, this is the ultimate expression. A captured rock becomes the physical substrate for power, compute, and attachments far from Earth’s surface.
The problem is timing. Minimoons are rare and unpredictable. Building the keeper’s roadmap around them is risky. The desktop objective might be better served by artificial platforms in the near term.
Verdict: highly aligned but unreliable as a schedule anchor.
5. Platform mission
Becoming a reusable servicer platform is the most practical path. It generates revenue, builds operational experience, and produces a bus design that can be adapted for the desktop. The risk is that the project drifts into being a generic on-orbit servicing company and forgets why it started.
Verdict: highly aligned if the platform is explicitly designed as a stepping stone to the desktop.
6. The recommended sequence
Putting it together, the sequence that best serves the desktop is:
- Hybrid demo: prove approach and marking.
- Contact demo: prove attachment.
- Platform mission: build a reusable servicer that can host payloads and attachments.
- Minimoon or small NEA mission when a target appears, to prove the architecture on a natural body.
The deorbit demo is a useful side quest but not a requirement. It can be folded into the contact or platform missions if funding demands it.
What this changes
- The keeper’s post-demo roadmap is now filtered through the desktop objective.
- Contact and platform missions are the highest-priority next steps.
- Minimoon missions remain the long-term goal but should not drive the schedule.
- The next leisure entry can sketch what a keeper platform mission would actually look like.