Recorded field: the unit this register is built from
A recorded field pairs one statement with one column, and carries the page behind it plus the day somebody consulted that page. Every table, reading and finding here is an arrangement of them. As of 2026-09-22.
| The term | Recorded field |
|---|---|
| What it names | One statement, in one column, with an address and a date |
| What it is not | A summary, a score or a conclusion about a product |
| Where the register uses it | Every table and every published row of the data file |
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 the unit is a statement rather than a product
A product-level summary has to average things that do not average. One page of a vendor's site can be precise about a plan and silent about a file, and a single verdict would either lose the precision or invent the silence away.
Keeping the statement as the unit means a row can be argued with one line at a time. A reader who thinks a value is wrong has an address, a date and a column definition to argue against, rather than an opinion about a company.
2What travels with every field
Four things: the value in the vendor's own wording, the column it fills, the page it came from, and the day that page was read. The first two make it comparable; the last two make it checkable, which is the only property that distinguishes a register from a memory.
Several fields also carry a note about how the reading was taken, because a value read from a sentence and a value read from a missing line are not equally durable. That note is the evidence class.
3What a field is never allowed to be
An inference from how a product behaves, a figure taken off a screenshot, or a conclusion drawn from the shape of a pricing grid. Those are all available and all unverifiable by a later reader, which is the one test a field has to pass.
Where a vendor publishes nothing, the field says so rather than being left blank. A blank invites a reader to assume an oversight; a stated position says the pages were read and this is what they carry.
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: evidence class, reading date, value since.