The Name Wrote the Description
Written later and filed to this date, as part of filling in every day of the year.
You will write notes about your own repositories. One line each, what the thing was for, so that whatever reads the notes later, a person or a job, does not have to open the code. One thing only, then: before a line like that goes anywhere, read the repository’s log from the first commit, and when the log and the line disagree, the log is right and your memory wrote the line.
Mine were wrong like this. The job that fills this site’s empty days works from a seed file: a list of old repositories, one line each. One line described a repository named for the machine that ends the world as an early attempt at agents that run unattended, with a README that was an architecture diagram and little else, so that the log would be the only account of what it was for. I had written that from the name. The log says: three commits on one Sunday in May, fifty-one files, an idle game, a clicker about the history of AI, on the standard React starter with a state store bolted on. The README is a title and one image link, and the link points into a downloads folder on one laptop through an editor’s private URL scheme, so the picture loads on that laptop and nowhere else. Then thirteen months of nothing, then ninety-nine commits in one June from the build fleet. No agents. Nothing unattended. Not an architecture diagram, a picture of one, visible to one machine.
The error has a shape, and you can check for the shape. A note about a repository is written from the inside, by the person who knew what they meant to build, and it gets written when the intent is fresh and the code is thin. The repository records what was built. The gap is widest exactly where the name is strongest, because a name carries intent, intent is what you remember, and a strong name goes on believing itself long after the code stopped. Every job that touched my seed file believed the line, because the line read as a fact and nothing in it said it was a guess.
So the check is mechanical and cheap. The log in forward order, so you see the first commit before the last. The README as it sits on disk, not the one you remember writing. The first commit’s file list, which says what the thing was on the day it was most itself. If those three agree with your line, keep the line. If they do not, the line was the name talking.
The writers who fill this archive are told it in their instructions: a dossier is a lead, not a source of truth; a seed is a subject, never a fact. That rule exists because one seed was found wrong, and it was mine. The corrected line says what the repository shows: three commits, one Sunday, a game, a broken picture.