1. The problem of proving contact
Carl Sagan’s Contact is about many things, but at its core it is about evidence. The protagonist spends the novel trying to prove that something extraordinary happened, knowing that extraordinary claims require evidence that can survive skepticism. The keeper hybrid demo has the same problem. If the servicer approaches a spent stage and drops a marker, how does the project prove it happened?
This matters for funding, for credibility, and for the project’s own honesty. A mission whose success cannot be independently verified is not a successful mission.
2. Tier one: internal telemetry
The minimum success is that the servicer reports it reached the target and deployed the marker. This means:
- Onboard navigation logs showing relative distance decreasing to the planned hold point.
- Images or video of the target from the servicer’s camera.
- Telemetry confirming marker deployment.
- Post-deployment images showing the marker separating from the servicer.
This tier is necessary but not sufficient. Telemetry can be wrong, misinterpreted, or simply not believed by outsiders.
3. Tier two: external verification
The next level is confirmation by something other than the servicer itself:
- Ground radar or optical tracking observes the servicer and the target in close proximity.
- Independent analysts can correlate the servicer’s orbit with the target’s orbit during the encounter window.
- The marker, if large and reflective enough, is tracked as a separate object after deployment.
This tier is what turns an internal claim into a public fact. Without it, the demo is just a press release.
4. Tier three: scientific or operational residue
The highest level of success is that the demo produces something useful beyond the act itself:
- High-resolution images of the target’s surface condition, which help future servicing or debris-removal missions.
- Accurate measurement of the target’s tumble state and center of mass.
- A catalogued marker that serves as a reference point for future observations.
- Public release of the approach trajectory and navigation data so other missions can learn from it.
This tier is what makes the demo worth more than its cost as a stunt.
5. How to communicate it
The project should publish three things immediately after the encounter:
- A timeline of the approach and deployment.
- A small set of verified images and tracking data.
- A candid assessment of what worked, what did not, and what was learned.
The third item is the most important. A demo that admits its limitations builds more credibility than a demo that claims perfection.
What this changes
- Success for the hybrid demo is defined across three tiers: internal telemetry, external verification, and operational residue.
- The project must design the marker and the encounter to produce externally verifiable evidence.
- Public communication should include honest limitations, not just highlights.
- The next leisure entry can return to the broader keeper roadmap and ask what comes after the hybrid demo.