1. The seed has to grow

Neal Stephenson’s The Diamond Age is about a designed object — the Young Lady’s Illustrated Primer — that is supposed to teach and adapt. Its value is not in the first edition but in how it evolves with each user. The first keeper platform is like that. Its job is not to be perfect. Its job is to teach enough lessons that the second platform is meaningfully better.

Entry 175 estimated the first platform at $12–19M over four years. That is too much to spend on a single learning mission unless the learning is specific and actionable. This entry defines what the first platform must prove.

2. Capability one: reliable power and data hosting

The platform must show that it can keep multiple payloads powered, thermally controlled, and connected to the ground for months at a time. This sounds basic, but it is the foundation of the desktop objective. If the platform cannot reliably host payloads, the desktop cannot exist.

Success metric: 95% uptime for hosted payloads over the first six months, with logged anomalies and recoveries.

3. Capability two: standard attachment interfaces

The platform must demonstrate at least one standardized mechanical, electrical, and data interface that future desktop modules can use. This is the keeper’s equivalent of a USB port or a rack mount. Without it, every attachment is a custom integration.

Success metric: at least three different payloads integrated and operated using the same interface standard.

4. Capability three: remote operations

The platform must be operated primarily from the ground with minimal manual intervention. This is essential because the desktop will eventually be too far away for real-time human control. The platform should test command scripts, fault responses, and software updates in orbit.

Success metric: 90% of routine operations executed via scheduled commands rather than real-time ground passes.

5. Capability four: customer pipeline

The platform must prove that external customers are willing to pay for hosted payload slots. Revenue is not the only goal, but it is the strongest signal that the platform is useful. A platform with no customers is a hobby.

Success metric: at least two paid external payloads or letters of intent for the next platform before the first one ends.

6. Capability five: path to scale

Finally, the platform must generate a concrete list of design changes for the next version. Bigger solar panels? More compute? Different orbit? Redundant radios? The first platform succeeds when the second platform’s requirements document is obviously better because of what the first one taught.

Success metric: a published post-mission review with at least ten prioritized design changes and their rationale.

What this changes

  • The first keeper platform is evaluated on five capabilities: hosting, interfaces, remote ops, customers, and scalability.
  • These capabilities are the bridge between the demo missions and the full desktop.
  • The next leisure entry can sketch the second platform based on these lessons.