GateTrue

What each generator documents about marking its output

Register row: four columns for one entry

A register row is one entry across all four columns. Reading a row sideways gives a product; the pattern of which columns are filled gives something else, which is who the vendor was writing for. As of 2026-09-22.

Two shapes a row takes, and what neither of them isA row read from a pricing grid carries a tier, a price and a control mechanism with the file column empty. A row read from a card or a reference carries a named standard with the commercial columns empty. No row here fills all four, and none of them is a score.A commercial rowA technical rowFree tierA mark, or an omissionA default with no plan attachedPaid tierA tier, often with a priceNothing publishedControlA plan benefitNothing, or a request fieldFile contentsNothing publishedA named standard, sometimes a readerThe shape follows the genre of the source page
Fig. 1 There is no defensible weighting across the columns, because different readers arrive needing different ones.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termRegister row
What it namesOne entry, read across all four columns
What it is notA score, a ranking or a recommendation
Where the register uses itThe support table, and every generator page

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.

1Reading sideways and reading downward

Across a row is one product: what free output carries, what a plan changes, how the mark comes off, what the file holds. Down a column is one question asked of every entry, which is what makes the fixed order of the fields worth its rigidity.

Settling the four columns ahead of any reading is what stops a vendor's own emphasis reshaping the table. Otherwise a company with a detailed plan grid and nothing else would look thorough, and a table of such rows would be a rack of advertisements.

2The pattern of filled cells is a second finding

Rows here come in two shapes. One fills the commercial columns and leaves the file column empty; the other fills the file column and leaves the commercial ones empty. No row on this register fills all four.

That pattern follows the genre of the document a marking statement was published in, almost exactly. A company whose only statement is on a price list has treated marking as packaging; one whose only statement is on a safety card has treated it as a safeguard. Neither has treated it as both.

3What a row is not allowed to become

A verdict. Nothing here weights the columns against each other, because there is no defensible weighting: a reader inheriting footage cares about the free-tier value, a reader budgeting cares about the crossing point, and a reader receiving a file cares about the fourth column.

So a row is a set of values and a shape, and the readings argue about what each value supports. Anything that looked like a total would have to be this register's opinion rather than a vendor's statement.

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: inclusion rule, re-encode, transcode.