Rewrite.exe

Opening scene

You are Teodor Marchetti and you found it in a folder you don't remember making, an .exe with no readme, which every instinct you have says do not run. You ran it. Of course you ran it. There is a search box and it autocompleted your best friend's name before you finished typing it.

You changed one field. DRINKS: heavily → DRINKS: no. Small. Kind, even. Milo has been trying to quit for a year and hating himself for failing. You told yourself it was a test and you clicked SYNC before you could argue, and the button went grey, and your phone lit up with a text from Milo about the six-a-side on Sunday that you are apparently both still playing, that you have apparently always played.

The record is open in front of you. Milo's other fields scroll on — job, sister, the year you met — every one of them a text box with a cursor that will happily sit wherever you click. The undo counter in the corner says: 1.

Turn 1 of 12

I take in the scene, and act on what matters most.

The flat is quiet in the way that only happens after 2 a.m., when the radiator stops clicking and the neighbours stop pretending they have jobs. Your desk lamp is off. The monitor is the only light in the room, and it is the flat, clinical white of a database frontend that has never heard of dark mode. The window to your left shows the back of the betting shop across the alley, shutters down, a security light buzzing orange over a fire escape nobody uses. Saanvi's door is closed. No sound from behind it. She sleeps the way QA testers sleep — deeply, defensively, like someone who knows that anything left unresolved at midnight will still be broken in the morning.

The program is called rewrite.exe. It sits in a folder called C:\Users\Teo\Desktop\_old\_old\, a path that suggests you made it years ago and forgot, except the folder's created timestamp is yesterday. The icon is the default Windows application placeholder — that blank rectangle with the blue bar — which means whoever built it did not care whether you opened it, only that you would. The autocomplete on the search box is the part that should have stopped you. It knew Milo's name after three characters. It knew the nickname, not the legal name. Fen. Not Milo Fenwick. The name on his birth certificate, the one his mother uses when she's angry, the one you have typed exactly twice in eight years of friendship.

His record is still open. The fields scroll past in the grey-on-grey of a ten-year-old CRM, each one a label and a text input and nothing else — no dropdowns, no validation, no help text. JOB: Site manager, Kestrel Construction. SISTER: Priya Fenwick, 31, Manchester. YEAR MET: 2016, university halls, the night he put a fire extinguisher through a vending machine. DRINKS: no. The last one is yours. You changed it from heavily twenty minutes ago, and the cursor is still blinking at the end of the two letters you typed, patient as a heartbeat.

Your phone is face-down on the desk. You picked it up once since the sync and the messages were normal — Sunday six-a-side, can you bring the bibs, Tilly's got a calf strain — normal in a way that made your stomach drop, because Milo has been trying to quit drinking since January and failing since January and talking about failing since January, and apparently he does not remember any of that now. Apparently nobody does. The undo counter in the bottom-right corner of the window reads 1, in a small font, the kind of thing you would miss if you weren't looking for it.

You are looking for it. One undo. The field is two letters wide and the consequences are the size of your friend's entire year, and you are sitting here with the power to give it back to him or to make another edit first — to fix something, to test something, to see how deep this goes — knowing that every new sync burns the one rope you have left. The cursor blinks in DRINKS: no. Outside, the security light on the betting shop flickers and steadies. Somewhere behind Saanvi's door, her alarm clock ticks over to 2:14. The program waits.