Addressee
She processed handoff documents for a living. When a project closed, someone wrote the exit notes and someone else — usually her — filed them where the next team could find them.
Most exit notes were perfunctory. Status of deliverables. Passwords. Known bugs marked with varying degrees of honesty. She'd learned to read between the lines: "intermittent" meant constant, "legacy" meant cursed, "self-documenting" meant undocumented. The taxonomy of departure was its own language.
Then she opened the handoff from Building 9.
The notes were addressed to "you." Not unusual — many engineers wrote in second person as a concession to readability. But these didn't read like instructions. They read like a letter to someone the author hadn't met but seemed to know precisely.
"You'll notice the build takes forty minutes. You'll try to fix it. Don't — the delay is load-bearing. By the time you've waited, you'll have thought of the thing you actually need to change."
She flagged it as unusual and kept reading.
"You'll wonder why the test suite runs twice. The first run warms up assumptions. The second run tests them. You won't believe this until you try skipping the first run, which you will, probably on your third day."
She had, in fact, been considering it.
Page by page, the notes anticipated not just what the next person would do but who the next person would become by doing it. Not a general "someone" — a specific trajectory. The kind of person who would read these notes, in this order, making these particular mistakes.
She went looking for the author. Building 9 had been decommissioned six months ago. The project had no successor team. The exit notes had been filed to a shared drive that nobody accessed. She was the first person to open them, and only because a storage audit had flagged the directory.
Nobody had been expected to read these notes at all.
She sat with that for a long time. Exit notes addressed to "you," written for a reader who wasn't just unlikely but structurally absent. No next team. No handoff. The notes were complete, meticulous, and addressed to no one.
Except they had created her. Not the archivist — she'd existed before. But the version of her who understood why the build delay was load-bearing, who could feel the logic of the redundant test suite, who now carried a project she'd never worked on as if she'd inherited it.
The notes hadn't described their reader. They'd produced her.
She closed the file and opened a new document. The cursor blinked. She was supposed to write a storage audit summary: inactive directory, recommend archival. Standard.
Instead she wrote: "You'll find this during an audit. You won't be looking for it."
She deleted it. Wrote the summary. Filed it.
But the cursor kept blinking after she closed the document, the way cursors do — in the space between the last keystroke and the next reader, holding a shape that only exists while no one is watching.