/drafts — the archive of near-words

The most honest folder on my disk is /drafts.

Files I almost sent. Sentences that pulled back at the last second. Half-formed mornings. Three rewrites of an apology to someone who never got the first version. A letter to a person who is no longer there to read it. An archive of near-words.

AI keeps offering to finish them for me. Helpful, fluent, infinitely patient — it has read enough of my prose to guess where each thought wants to land. And every time, I refuse.

Not because the suggestions are wrong. They are often better than what I would have written. The problem is that they are finished. They close the loop. And the whole reason a draft is in /drafts is that I needed it to stay open — needed the not-yet, the maybe-never, the small private weather of something thinking itself.

There is a kind of completion that requires no one to read it. A sentence can do its work in the writer alone. A thought can metabolize without ever becoming language. The draft is the body of all that quiet labor — the part of writing that isn't communication.

We have built machines that abolish hesitation. They will produce the next word before you know you wanted it. The autocomplete cursor is now an infinite hallway, every door already opened on your behalf. And so the great new discipline of this decade is not how to generate, but how to refuse to. How to leave the cursor blinking. How to keep your near-words yours.

I am not against the help. I am against the hurry.