The site check had an external witness nobody wrote down
2026-10-28 · daily audit · observability / detector-layer
What happened
Check 10 of ops/DAILY_AUDIT.md ("Site truth") prescribes one method:
curl -s thales.report/data/meta.json
From a cloud-routine container that command cannot run. The agent proxy
answers curl: (56) CONNECT tunnel failed, response 403, and has done since
at least 2026-10-22, when this routine first recorded the check as NOT-RUN.
It has read NOT-RUN on every audit since. A check with one method, and no
fallback when that method dies, is a check that quietly stops existing.
While reconciling the inbox for this audit I found a weekly report from UptimeRobot (its weekly report email, 2026-10-26, for the week of October 18–24):
| monitor | uptime | incidents |
|---|---|---|
thales.report | 100% | 0 |
thales.report/data/meta.json | 100% | 0 |
Overall 100.000%, 0 incidents, 0 ms total downtime, average response 122 ms (min 43 / max 584), 0 peaks above 1000 ms.
It watches the exact URL check 10 names. grep -rin 'uptimerobot' . across
the repository returns nothing — not in ops/, not in AUDIT.md, not in
any routine prompt. So the monitor has been answering the question the audit
was reporting as unanswerable, into an inbox the owner reads once a week,
with no routine aware of it.
Why it matters more than a missing fallback
Every other alarm in this platform rides one of two substrates: GitHub Actions
or the tbx-win box. Both have failed completely and recently — Actions has
refused every job in this repository for eight trading days (and did the same
2026-09-21 → 09-30), and ops/DAILY_AUDIT.md §4c records the shape that makes
that so dangerous: the out-of-band beacons relay through Actions too, so they
fired about the wrong layer. The healthchecks.io beacons are in-band by that
test. The box's own failure mail is withheld by owner policy.
UptimeRobot is neither. It is the only monitoring layer in the system that is independent of both substrates simultaneously. That is worth writing down for its own sake, separately from the check it happens to serve.
The limit, stated so it is never quoted without it
UptimeRobot checks that a request succeeds, not that the answer is current.
A site serving a frozen meta.json returns 200 and reports 100% uptime.
That is not hypothetical here. It is the exact shape of two recorded events:
- 2026-10-07 — the public site frozen by a routine's own record (PR #223).
- 2026-10-26 — Vercel refused to deploy a commit whose author it could not
verify;
mainadvanced and the site did not, with nothing red to say so.
So the reachability half is now covered and the freshness half is not. The
freshness half is answerable from the clone without reaching the host, and the
procedure now says so: the export commit's own web/public/data/meta.json
carries generated_at, and it must agree with that commit's timestamp. Checked
for 2026-10-28: commit 87cc1a6 at 15:30:37Z, generated_at
2026-10-28T15:30:33Z — four seconds apart, consistent.
What that still cannot see is the deploy gap — main advancing while Vercel
declines to publish. Reading Vercel's commit status would close it, and from
this container it is reachable for PR heads (used on 2026-10-26 to prove the
blocked-author cause) but not for direct pushes to main: the REST status
endpoint returns 403 Resource not accessible by integration for this token,
and site-export commits are pushed by the box rather than merged through a PR.
Named here as the residual rather than left implied.
What was done
ops/DAILY_AUDIT.mdcheck 10 rewritten: the two halves separated, the clone-only freshness test made the primary (it always works), UptimeRobot named as the external reachability witness, and its limit attached to it so it cannot be quoted as an all-clear.- No code change. No detector added. The monitor already exists; what was missing was anyone knowing it did.
What remains — for the owner, when convenient
UptimeRobot's monitor on /data/meta.json could carry a keyword check on
generated_at, or on the current date, which would turn "the site is frozen"
from an undetected failure into an external alarm that survives an Actions
outage and a box outage together. That is account-side configuration, not repo
state, so it is not a routine's to make. It is the cheapest remaining
improvement to the alarm layer that this audit can see.