Pin
re-pin, pinned, pinned by commitDefinitions
The commit a downstream repository names as the version of a source it read, kept beside the date it was read; a count or a citation is against a pin, not against a checkout
brand-migration's sources.json holds each input — cwds, brand-gate, the EDS blocks — as a commit, a dirty flag and a read date, and the vendored token artifact as a hash; a contract cites a specimen as markup.html:line at a captured commit. Confirm the tree matches the pin before tallying: it did on 2026-09-13, and it will not always.
To re-pin: to move the pin after the source changed, which obliges a re-read of everything that cited the old one
A record change upstream is an experiment input until the adapters are re-measured at the new pin; a line citation left pointing at a line that no longer says it is the failure the word exists to prevent. Findings are dated for the same reason: a finding older than the record it criticizes has already been answered.
The estate's way of saying when. Five sibling checkouts read each other and none is vendored in, so a value with no pin is a value read from whatever happened to be on disk. The pin is what lets a number be checked by someone else, later, on another machine.
Avoid: "the latest" as a version; and counting against the working tree without first confirming it is the pinned one.