Patchwake

A vessel with a memory

A clean reset is convenient, but it can remove the connection between an object and what it survived. Patchwake treats the vessel as something worth continuing with. A dent is not a decoration added to make a new object look old. It comes from a choice made during the run and becomes a practical reason for the next repair.

This gives the repair ritual a narrative role. Plates and wire restore enough integrity to travel again, while the action history keeps the order of events. The vessel can become useful without becoming blank. A player does not need a written biography to remember the time they took too much salvage and spent the next few turns putting things right.

Saving that history is part of the idea. An exported run carries its actions, and restoration checks whether the recorded state follows from them. The memory is constrained by the game rather than written as a flattering summary afterward. That makes it possible to revisit the sequence that produced a particular departure.

The local loop begins with recovering parts. Repairs spend plates or wire and raise module integrity by 30, capped at 100. All three modules need at least 60 before departure. A route consumes fuel; the encounter choice changes the salvage and damage on return. Recovering supplies at the dock remains possible when the inventory runs low, with turns as the cost.

Export a repaired run and bring its action history back into the workshop. Notice the consequence before adding another step. This presentation does not connect a hosted service or issue a token; its claim is the small interaction you can actually inspect.