A novel you have to repair.
Someone left a repository on a drive with a program that fails on launch. His README says that is on purpose. His code says otherwise. To find out what he did, you have to fix it — and the history still has the file he deleted.
tallow ~ % python tallow.py Traceback (most recent call last): File "tallow.py", line 13, in <module> from tallow.watcher import Watcher ModuleNotFoundError: No module named 'tallow.watcher' # the file is in the history. it has been the whole time.
The object
Three ways in. All of them end the same night.
Plug it in
The repository exactly as he left it, broken on purpose. A card with the first move on it. Nothing else. Works offline, forever.
Read it on a train
The same story as a printed novel — the transcript of the repo, with the commit history in the margin. No laptop required.
Both, boxed
The drive and the book in one case. Read the room, then open the machine, or the other way round. The order changes what you notice.
The method
Nothing on the drive is decoration. Every clue is a decision somebody made and could not undo.
Fingerprints are decisions
Loss and guilt are readings. What survives is a mislabelled box, a re-taped corner, a call that never connects. The reader works backwards from the wear.
Two plots, one room
Grief and guilt leave the same residue. If only one story explains what you found, the room is a description, not a mystery.
Clocks hide in objects
Fading, dust, a lapsed habit, a disconnected number. They date things without anyone writing a date down — which is exactly why he never wrote one.
Editions
First run: 2,000 pairs. Ships with the drive, a printed book, and no account of any kind.