**For ten days every page on this site promised an event that had already finished.** The masthead
read «Lisboa · segunda-feira, 14 de setembro de 2026» as though that were today, and beside it
«Faltam **3 dias** para o Startup Summit Lisbon 2026». The Summit ran on 17–18 September. This was
found on the 24th, six days after it ended, on **231 pages**, with all five gates green.

**Two claims, both false, and they fail for different reasons.**

The dateline was **mislabelled**. `hoje` is not today: it is `registo.json.atualizado`, the date of
the most recent frozen source. That is deliberate and right — every page here has to be
deterministic, and a rebuild that changed 231 files because a clock moved would make every diff
unreadable. The date was real. It was simply the capture's and not the reader's, and it did not say
so. It now reads **«última captura: 14 de setembro de 2026»**, which is a true sentence on any day
anyone reads it.

The countdown was **unknowable**, which is the more interesting failure. How long until an event
depends on *when you are reading*, and a file on a disk cannot know that. It had been computed as
17 September minus the capture date, so the moment the register stopped moving the countdown froze
with it and went on being confidently wrong. **No amount of care in the renderer could have made
that number true**, because the input the answer depends on was never available at build time.

**So the server states what it can prove, and the browser adds the tense.** The page renders
«Startup Summit Lisbon 2026 · 17–18 de setembro de 2026» — a fact with no tense in it — and
`assets/quando.js` appends the relative phrase from the reader's own clock: *foi há 7 dias*, *é
hoje*, *faltam 2 dias*. Tested against three different reader clocks. Without script the reader
gets a true sentence instead of a false one, which is the right way round for a publication whose
whole argument is that it does not assert what it cannot show. The dates stay beside the phrase
rather than being replaced by it: the dates are evidence, the phrase is arithmetic.

**Gate 45** fails the build on any reader page that states a countdown or presents the capture date
as the reader's. Broken on purpose first: putting the old line back turns 17 pages red.

*This is the one place on the site where something depends on the moment of reading, and it had
been handled as though it did not. Worth saying plainly before the site opens to a wider audience:
the gates checked that every claim walked back to bytes, and this claim did — it walked back to a
real date in a real register. It was still false.*