1. The traveler builds a better machine

H.G. Wells’ time traveler does not stop at one machine. The first proves the principle. The second is smaller, cleaner, and built with the confidence of someone who has already seen the future. The first keeper platform is our proof. The second is the one we actually want to live with.

Entry 176 listed five things the first platform must prove: reliable hosting, standard interfaces, remote operations, customer demand, and a path to scale. This entry assumes the first platform proved enough of them and asks what the second platform looks like when it absorbs those lessons.

2. From hosting to scaling

The first platform demonstrates that payloads can stay alive in orbit for months. The second platform must demonstrate that the operation can grow without breaking. More payloads. More power. More data. More customers who do not want to hear about thermal margins.

The second platform carries at least twice the hostable volume and power of the first, with the same mechanical and electrical interface standard. The lesson from the first platform is not just that hosting works, but which hosting limits customers actually bump into first.

3. Hot interfaces, not just standard ones

A standard interface is good. A hot-swappable interface is better. The second platform should allow payloads to be attached, powered, and detached without redesigning the whole stack. This is the difference between a docking port and a USB hub.

The first platform might require a campaign to attach something. The second platform should allow a visiting tug to drop off a payload, the platform to power and test it, and the tug to remove it again if the customer changes their mind.

4. From remote operations to autonomous operations

Remote operations mean a human on the ground sends commands. Autonomous operations mean the platform handles routine decisions itself and only calls home when something is unexpected. The second platform should move up that spectrum.

The first platform proves scheduled commands work. The second platform should prove that fault detection, power balancing, and attachment sequencing can happen without a ground pass for days at a time. This is necessary because the desktop will eventually be too complex to fly by joystick.

5. Two keepers, not one

The single-platform model is a single point of failure. The second platform should be a pair: two similar keeper nodes in the same orbital neighborhood, able to back each other up and swap payloads if one has a problem. This is the goalie redundancy idea from earlier wonderings, applied to infrastructure rather than tugs.

Two platforms also make the business case clearer. A customer who needs continuity can pay for hosted space on both. A customer who wants to test can pay for one. The platform becomes a service topology, not a single asset.

6. What the second platform looks like

Concrete sketch: two 500 kg-class keeper nodes in a 600 km sun-synchronous orbit, each with a standardized payload bay, a robotic attachment arm, inter-satellite crosslink, and enough solar capacity to host 500 W of customer payloads continuously. Ground control is mostly supervisory. Customer payloads arrive by small tug or direct launch.

This is not the final desktop. It is the chassis the desktop will eventually sit on.

What this changes

  • The second keeper platform scales hosting, interfaces, autonomy, and redundancy based on first-platform lessons.
  • It moves from proving that something works to proving that the model can operate like a service.
  • It introduces paired keeper nodes as the basic unit, making the architecture more resilient.
  • The next leisure entry can explore what attachments make the second platform worth building.