GateTrue

What each generator documents about marking its output

Not documented: a finding, printed as one

Not documented is what a cell holds when a vendor's own pages say nothing about that field. It is a statement about the pages and never a claim that the product lacks the thing. As of 2026-09-22.

Four reasons a cell is not a plain valueA vendor's pages can say nothing at all, which is recorded as a stated position with a date. They can describe a mechanism and attach no plan. They can publish no free plan for the question to apply to. Or they can omit a feature line from one column of a grid.Why does this cell not hold a plain valueThe pages say nothingNot documentedA stated position with adate, checkable by openingthe same pages.A mechanism with no planNo condition statedThe vendor answered theunderlying question in aform the column was notbuilt for.No such plan is publishedNo subjectThe pricing page beginsabove the tier thequestion is about.A fourth case, the omission reading, has its own term
Fig. 1 Collapsing these into one glyph would be tidier and would destroy the most useful information in two columns.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termNot documented
What it namesA stated position that the vendor's pages say nothing
What it is notA claim that the product does not do the thing
Where the register uses itMost of the file-contents column

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 it is written out rather than left blank

A blank invites a reader to assume somebody forgot to fill it in. A stated position says the pages were read and this is what they carry, which is a finding: the question people ask about a tool before committing a series to it is whether it tells you what it puts in your files, and mostly the answer is no.

The phrase also carries the date. Not documented as of a particular day is checkable; a blank is not, and a reader cannot tell whether it reflects a reading or an omission.

2The distinction it will not let a reader skip

A vendor can write provenance data and describe it nowhere, and several probably do. What a register built from published pages can honestly say is that nothing is published, which is weaker than a claim about behaviour and more useful than silence.

That is also why an empty cell is never evidence in the other direction. Nothing published about a mark on the frame does not mean the frame is clean, and the readings say so explicitly on the entries where the temptation is strongest.

3What it is not used for

Three cases that look similar are recorded differently. A vendor that describes a mechanism and attaches no plan gets a value naming the absence of a condition. A vendor with no free plan gets a value saying no such plan is published. And a vendor whose pages omit a feature line gets an omission reading.

Collapsing all of those into not documented would be tidier and would destroy the most useful information in two columns. A reader cannot act on not applicable, not offered and unknown in the same way.

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: stated position, applies-to note, scope as written.