GateTrue

What each generator documents about marking its output

Documented default: what happens with no decision

A documented default is what a vendor says happens when nobody chooses. It matters more than the available options, because most files are produced without anybody making a decision about marking. As of 2026-09-22.

Two published defaults, pointing opposite waysOne entry documents a setting as on, so output carries a mark until somebody turns it off. Another documents a request field as false, so output is clean unless a caller asks for a stamp. Both describe what happens when nobody makes a decision.A setting documented as onA field defaulting to falseOutput with no decisionMarkedCleanWho changes itWhoever runs the accountWhoever writes the callRecoverable laterOnly from a note at the timeFrom the code that made the callRecorded inThe free-tier and control columnsThe paid-tier and control columnsA default is the starting state, not a guarantee
Fig. 1 Options are exercised by people who know they exist. Defaults apply to everybody else, which is most output.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termDocumented default
What it namesThe published behaviour when nobody sets anything
What it is notThe range of options a product offers
Where the register uses itFive free-tier values, and two control 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 state most output is in

Options are exercised by people who know they exist and have a reason to care. Defaults apply to everybody else, which on any product is most users most of the time. A vendor publishing a default has therefore said more about its output than a vendor publishing a switch.

Two entries here publish defaults in opposite directions: a setting documented as on, so output is marked until somebody intervenes, and a request field documented as false, so output is clean unless somebody asks. Both are more informative than the existence of the control.

2Why a default is a column value here

The free-tier column was defined to answer a question about payment, and on five entries no payment is involved: the vendor describes what output carries and names no plan. Rather than leave those cells empty, the register records the documented default and labels the evidence class differently.

The alternative would be a table where the entries that publish the most about their output have the emptiest rows, which would be exactly backwards. The label keeps the two kinds of value distinguishable without discarding either.

3A default is not a guarantee

It describes behaviour absent instruction, which is a claim about the ordinary case and not about every case. A default can be changed once by whoever holds an account and then apply for months without anybody remembering, which is the auditability problem a settings switch creates.

So a default value in this register should be read as the starting state. What a given file carries depends on whether anybody moved it, and on one entry that is unrecoverable after the fact.

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 user toggle column, source documents. Nearby terms: limitations section, verification platform, public reader.