GateTrue

What each generator documents about marking its output

Plan inheritance: when silence on a grid carries nothing

Plan inheritance is the convention that a dearer plan includes everything the cheaper ones do. Where a page relies on it, a feature is named once and its absence higher up means nothing at all. As of 2026-09-22.

Which silence on a grid carries informationBeneath the plan where a feature line first appears, silence means the feature is not included. Above it, silence is inheritance and carries no information. Treating the two alike places a boundary wherever a vendor stopped repeating itself.The marking line is absent from this plan's listThe plan is below the first mentionInformativeThe feature is not included, which is whata grid is built to convey.The plan is above the first mentionNot informativeInheritance. The line was named once andis not repeated.One direction of silence is evidence; the other is layout
Fig. 1 The register records where the line first appears, not where it last appears.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termPlan inheritance
What it namesThe convention that a dearer plan includes everything below it
What it is notA guarantee that any particular feature is inherited
Where the register uses itThe method behind one entry's paid-tier reading

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.

1A convention, not a rule the page states

Most grids never say that upper tiers inherit; the layout assumes it. Sometimes the assumption is made explicit, with each plan described as the one below plus additions, and sometimes it is left entirely to a reader's expectations about how pricing pages work.

Either way the reading has to account for it, because the alternative is to treat an unrepeated line as withdrawn. That would place a marking boundary wherever a vendor happened to stop repeating itself, which is a property of copywriting rather than of a product.

2Where inheritance can fail, and why the register does not assume it

Features do occasionally stop at a tier: seat limits, support levels and some usage rights are not monotonic. So the register does not assert that a mark stays absent above its crossing point; it records where the line first appears and what the page says, and leaves the rest to the page.

In practice the marking line has never been observed to reverse on these entries, which is worth stating and is not a reason to record an inference. A cell that asserted continuity would be making a claim the page does not.

3What it means for reading upward

The procedure is: find the lowest plan carrying the marking line, take that plan and its list price, and stop. The only informative silence is beneath that plan. Everything above is inheritance, and confirming it by looking for a repeat is the commonest way to place a boundary wrongly.

That is the reading method printed beside such values here. It tells a later reader not just what was found but how the page was traversed, which is what makes the reading reproducible by somebody who disagrees with it.

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: trial tier, credit allowance, output cap.