GateTrue

What each generator documents about marking its output

Value since: how long a statement has held

Value since is the day a recorded value is known to hold from. Confirmations do not move it, so a change in the vendor's statement is visible as a change in the date rather than hidden by routine checking. As of 2026-09-22.

What the gap between two dates tells a readerWhere the two dates are the same, a value was first recorded on the day it was read. Where they differ, the statement has held since the earlier date and was confirmed on the later one, and the gap is the duration the register can vouch for.Are the two dates on this value the sameYesNewly recordedThe value was written down on the day thepage was read. One date is printed.NoHeld and confirmedThe statement has been present at everycheck since the earlier date. Both areprinted.The gap is the duration the register can vouch for
Fig. 1 A column of identical pairs trains a reader to skip them, so only differing pairs are printed in full.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termValue since
What it namesThe day a value is known to hold from
What it is notThe day this site last looked at the page
Where the register uses itBeside values whose two dates differ

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 date that is supposed to stay still

If both dates moved on every check, nothing in the register would record duration. Keeping one of them fixed means a reader can see that a statement has held since a particular day, which is a different and more useful fact than knowing somebody looked at it recently.

It also makes a change legible. When a vendor rewrites a line, the value-since date moves and the reading date moves with it, and the pair says a real thing happened rather than a routine check.

2What it can and cannot claim

It claims that the statement was present on that day and has been present at every check since. It does not claim the vendor published it then: a page may have said the same thing for a year before anybody here opened it, and the register has no way to know.

So the date is a floor rather than an origin. Where the two dates are the same, the value was first recorded on the day it was read, which is the ordinary case for a newly added row.

3Why it is displayed conditionally

Where both dates are the same, printing both would be noise, so the row shows one. Where they differ, both appear, because the gap between them is the informative part: a statement that has held for months and was verified this week.

That is a small formatting decision with a real effect on how a table reads. A column of identical date pairs trains a reader to skip them, and the pairs that matter are exactly the ones a skipping reader would miss.

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: stable identifier, not documented, stated position.