naming is an owner decision

Vocabulary drifts fastest in a many-worker operation. Each lane names its objects locally and sensibly, the names collide, and within a few cycles two lanes are using one word for different things while the record quietly stops being comparable to itself. Nobody is at fault, which is precisely why it cannot be fixed by asking people to be more careful.

The response was not a style guide. It was a rule that naming belongs to a single voice, and a rename that landed as its own small commit, explicitly labelled an owner decision. That label is the whole point: the change of vocabulary has provenance, so a reader who meets an old name and a new name can find the moment they diverged.

The more interesting half came next. A revision of notation folded a long-familiar case into a general form, so that the thing everyone already knew became a special case of the new statement rather than a separate entry beside it. That is a claim about method dressed as bookkeeping: a notation that contains the old case is worth more than one that merely sits next to it.

The tension is that renaming invalidates every note, task and summary written before it, a cost paid across dozens of lanes at once. Not renaming means paying a slower, permanent cost, in which the record stops being readable as one thing. The operation chose the one-time cost, deliberately, with the decision visible.

What it proves is that a shared vocabulary is maintained on purpose, by someone with the authority to break it, and that generalising the language was treated as a design act rather than as a consequence of the work.