GateTrue

What each generator documents about marking its output

Feature grid: a sales table read as a specification

A feature grid lists plans across and features down. Its purpose is to make an upgrade look worthwhile, which decides what appears on it and what a blank in it can honestly be read to mean. As of 2026-09-22.

What a grid is built to convey, and what it cannotA grid exists to move a visitor rightward, so the crossing point is stated plainly and the appearance of the mark is absent. A manifest is not a feature anybody upgrades to obtain, which is why no grid in this register names a provenance standard.On the gridNot on the gridThe planWhich tier stops applying the markNothing about earlier filesThe moneyA list price beside that tierNo price for the mark itselfThe markA noun, usually one or two wordsNo size, place or behaviourThe fileNothingNo standard, no field, no routeThe purpose of the document decides both columns
Fig. 1 Nine entries are read from this genre, and all nine record not documented for what the file carries.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termFeature grid
What it namesA table of plans and features, published to sell a subscription
What it is notA specification of what any file carries
Where the register uses itThe source of nine entries' recorded values

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.

1The purpose of the document decides its contents

Every line on a grid is there because it makes the gap between two columns clearer. Watermark removal earns its place for exactly that reason, which is why the crossing point is the one value grid-read rows carry reliably. Nothing else about the mark helps sell a plan, so nothing else is printed.

The same purpose explains a structural silence. A provenance manifest is not something anybody upgrades to obtain, so a grid built around upgrades has nowhere to put it. Every entry in this register whose file-contents cell is filled was read from a different genre of page.

2Three readings of one blank

A blank cell can mean the plan does not include the feature, which is what a grid is built to convey. It can mean the line was cut for space, which happens on narrow layouts. Or it can mean the question has never been addressed anywhere, which is a fact about the company rather than the plan.

Only the first is about the product. A register that treated all three alike would be inventing findings, so values read from a blank are labelled as omissions and the readings say what the omission rests on.

3Two layout traps that invert a naive reading

Some grids print the same feature line under every plan and carry the distinction in an icon, so text alone says every plan qualifies. Others describe each plan as the one below plus additions, so a feature named at one tier is inherited upward in silence and its absence higher up means nothing.

Both are legitimate designs and both mislead anything working from extracted text. The register records the method beside the value for that reason, and the readings name which trap each grid presents.

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 paid tier column, reading a plan table. Nearby terms: cumulative grid, feature icon, negative feature line.