Prediction
pre-registration, pre-registered, countsDefinition
A count committed before the thing it counts exists — what an adapter will cost in files, lifecycle entry points and authored-row columns — so that the order is checkable in git log rather than asserted
The three buckets and their counting rules are frozen in brand-gate's 2026-09-09 agnosticism document and are not renegotiated per adapter. A prediction declares its prior exposure first — what the author had already seen, and which bucket that compromises — and is scored afterwards in a counts document, where a miss is recorded as a miss. The commit that adds the prediction adds no adapter.
Pre-register, commit the prediction alone, then write. The sequence is the whole method: a number written after the adapter exists is a description, and only a number written before it is a test of whether the contract said enough. The typography prediction said 37 names; the adapter bound 35, and the two are recorded as a miss rather than rounded.
Avoid: a prediction in the same commit as the adapter, or one that does not say what its author had already seen.