GateTrue

What each generator documents about marking its output

Applies-to note: the qualifier beside a value

An applies-to note is the short phrase beside a recorded value. It names the field the value fills and, where it matters, how the reading was taken: from a sentence, an omission, or a particular surface. As of 2026-09-22.

What the phrase beside a value is doingThe note names the column the value fills, which is what makes a quotation into a comparable field. It carries the evidence class, which is what a later reader needs to repeat the reading. And it carries any scope the vendor's own wording attached to the statement.Three things the note carriesThe fieldWhich of the four columns this statement is being read into.The evidence classA sentence, a layout reading, a default, or no such plan.The scopeA route, a surface or a plan group, exactly as the vendor'swording gave it.Not in itComparisons, judgements, or anything worked out from severalpages at once.One thing it never carries
Fig. 1 Nothing evaluative goes in it. Comparative observations belong in prose, where they can be attributed to an argument.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termApplies-to note
What it namesThe field a value fills, plus how it was read
What it is notPart of the vendor's statement
Where the register uses itBeside every value in the evidence lists

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1Why a value needs a qualifier at all

The same sentence can answer different questions depending on which column it is being read into. A line about a mark on a free plan fills the free-tier field; the same page's benefit list fills the paid-tier field. Without a note, a list of statements would be a list of quotations with no structure.

It also carries the reading method, which is where an omission gets labelled as an omission and a console statement gets labelled as applying to a surface. That is the part a later reader needs in order to repeat the reading.

2What belongs in it and what does not

The field, the evidence class, and any scope the vendor's own wording attached: a route, a surface, a plan group. Nothing evaluative, nothing comparative, and nothing this register worked out by reasoning about several pages at once.

Comparative observations belong in the prose of a reading, where they can be attributed to an argument rather than sitting beside a quotation as though the vendor had said them.

3How it interacts with scope

Where a vendor scoped a statement, the note carries the scope as written. A mark described on downloads from the vendor's own surfaces is recorded with that phrase attached, not generalised to every file the model produces.

That restraint is what allows one entry in this register to document two surfaces with opposite defaults without the two statements contradicting each other. Each is true within its scope, and the scope is in the note.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the protocol page, what earns a row. Nearby terms: scope as written, re-reading, register row.