Stated position: a claim about pages, not products
A stated position records what a vendor's pages carry, not what its product does. Every value here is one, which is the constraint that makes the whole register checkable by somebody else. As of 2026-09-22.
| The term | Stated position |
|---|---|
| What it names | A value describing what the pages carry |
| What it is not | An observation of how a product behaves |
| Where the register uses it | Every cell, in every 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.
1The constraint that makes a register reproducible
A claim about a product can only be settled by running the product, which means a reader either trusts whoever ran it or repeats the work with their own equipment and their own judgement. A claim about a page can be settled by opening the page.
That is the whole reason this register refuses observational evidence. Not because observation is worthless, but because a site full of observations is a site that cannot be audited by its readers, and this one is built to be.
2What it costs
Most of what people want to know is unanswerable. Whether a mark survives a particular editor, whether a detector works on a re-encoded clip, whether a plan change takes effect immediately: all real questions, none of them answerable from published pages, and none of them answered here.
The readings say so where the temptation is strongest, and spell out the sentence a vendor would have to print before an answer existed. That is more useful than a guess and less satisfying, which is the trade.
3How it shows up in the wording of cells
Cells say things like the free plan's feature list does not include watermark-free output, rather than free output is marked. The first is a claim about a page; the second is a claim about files that the page does not support, however likely it is to be true.
That phrasing looks pedantic until a vendor changes one without the other. A grid can gain a line for a plan whose output never carried a mark, and a mark can appear on output whose plan line never mentioned one.
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: applies-to note, scope as written, re-reading.