The Surface
and the Strata

Stratum I · just beneathIt happened in a single day

The first surprise is that there is barely any history to dig through. Most features hide months. This one was born and finished inside one calendar day — the third of March — across two commits and a single sitting. There was no slow gestation, no scrapped predecessor sketched over weeks. The labor here is not spread thin across the calendar. It is compressed, folded into an afternoon, which is exactly why it hides so well.

Stratum II · deeperThe rename inside the day

Below the first commit, in the same day, the page was already being reclassified. The bibliography was renamed almost as soon as it existed — a small reach for the right shape before the day was out. To rename a thing is to decide again what it is. That second decision is invisible on the surface; the finished page carries no trace that it was something else, briefly, hours earlier.

Stratum III · the bedrockWritten over, not deleted

Here is the strangest layer, and the most telling. The history records one thousand three hundred seventy-seven insertions and not one deletion. By that account, nothing was ever thrown away. And yet only seven hundred twenty of those lines are in the file today.

The reason is that this page is generated. It is built from source into the public tree by a script, and the rename and the rebuild on that same day quietly replaced six hundred fifty-seven of the original lines — without a single deletion ever reaching the log. A generated artifact hides its rework better than any hand-written file. The machine rewrites the lines and leaves no scar.

This is the ordinary condition of finished things, not a failure of this one. Bowker and Star noticed that infrastructure becomes invisible exactly when it succeeds. You stop seeing the citations and start seeing only the argument they support, and the same recession happens to the labor that produced them. Success closes over its own history.

So it would be easy to read those six hundred fifty-seven vanished lines as waste. They are not. They are the first, longer, rougher form of the page — the version that had to exist before the build could fold it down into the clean seven hundred twenty that ship. The discarded lines are the reasoning, externalized, then cleared away once the generator had done its work. The repository keeps the reasoning long after the page forgets it.

on the way back upIt never moved alone

The bibliography did not arrive by itself, either. A generated page cannot ship without touching the machine that generates it. In the same breath it reached sideways into six other files: the build script that assembles it, the two synced copies written into the public tree, the essay's own index and introduction, and the project's package.json. None of those are the bibliography. All of them had to move for the bibliography to appear.