What Happens Once It Leaves You

●●●●○call

Once something you've written leaves your hands, it stops being entirely yours. This is the whole arc, start to finish, of what happens to a claim once other people start reading it: what changes the moment it's seen, what the audience actually takes away versus what you actually wrote, what circulates without your permission, and what eventually comes back to you, changed.

Frozen the moment it's seen

A private draft is still entirely yours to change; nobody's relying on it yet, so revising it costs nothing. The instant it's seen by anyone else, that stops. From then on, you don't edit it. You write a new document that inherits from the old one, and the old one stays exactly as it was, because someone formed an impression of it that doesn't get to be quietly rewritten out from under them.

What they actually took away

Readers don't absorb a document evenly. The first two or three claims tend to land well; whatever comes after that starts to fade. Front-load your strongest argument and the audience walks away with the strongest version of it. Bury it on the last page and it may never really register at all, even though it's technically still there for anyone careful enough to go looking. Worse, a tentative, carefully hedged claim tends to get remembered as more confident than you actually wrote it: nuance gets sanded off in the retelling, and a "possibly" quietly becomes an "is."

Work you've lost track of

Things you wrote keep moving after you've stopped watching them. A colleague cites your circulated draft in a talk you weren't at. Students compile their own lecture notes into something that gets passed around on its own. An editor anthologises something you wrote years ago, including a claim you've since changed your mind about, and there was no moment where anyone asked you first. You know the parts of your own citation graph you happened to notice. You learn about the rest by accident: an alert, a colleague's aside, a student's thesis, occasionally a full-blown controversy you had no idea you were already inside.

Leaving something out isn't the same as taking it back

If your new paper simply doesn't repeat a claim from your old one, that doesn't retract it. The old paper still asserts whatever it originally asserted; it hasn't been touched. The gap between the two is visible to anyone paying attention, and a sharp reviewer may well point out that your newer work no longer supports a claim your earlier work depended on, which is a more uncomfortable position to be caught in than an honest retraction would have been.

What comes back

Changing your mind doesn't change anyone else's. Your earlier position keeps circulating under your name for as long as the lag takes to close, regardless of what you currently believe. And sometimes what comes back isn't even your actual position: a low-fidelity, compressed version of it enters circulation on its own, and eventually a peer challenges you on a claim you never quite made, based on a garbled account of something you did write once. When one of your claims does get formally retracted, the cost isn't even across everything that inherited it: a paper that had already dropped the claim on its own is clean, one that repeated it but backed it with independent evidence of its own is at least defensible, and one that simply carried it forward unexamined is fully exposed.

Not every publication is a paper

Some of this cycle doesn't run through documents at all. An exhibition is a curated, physical event: the audience encounters it because they walked into the room, not because they sought it out, which changes what "reaching an audience" even means. A lecture gets published, in the sense that matters here, by the act of delivering it to a room. A museum catalogue is tied to the exhibition it accompanies but keeps existing on shelves long after the exhibition itself has closed and the objects have gone back into storage. We haven't fully worked out how this corpus cycle applies to forms that were never a document to begin with.

Told here as what it feels like, not why it's built this way

Two pieces of this, that a document freezes when it's seen rather than when it's saved, and that retraction cascades unevenly through whatever inherited the claim, are also argued as deliberate design decisions elsewhere on this site. This page isn't trying to make that argument again. It's trying to describe what it's actually like to be on the inside of it: the sequence, roughly, in which a piece of your own thinking stops being fully under your control.