(U//OS) · The Prescient Desk · Spion
Pages that announce nothing
Standards bodies publish on their own schedule and tell no one. This channel fetches a fixed list of their pages on a six-hour clock, hashes what a reader would actually see, and records every move with the time it was observed. The record below is the whole product. Nothing here is a summary of it.
1Sixty days of the watch
One lane per source, one column per day, oldest at the left. Ochre is a recorded change, green a first baseline, red an unreachable source. Empty means checked and steady — the ordinary condition, and the one that makes a mark mean something.
2Condition of every source
| Body | Page | Condition | Last observed | Last moved | Signal | Text hash |
|---|
3Observation record
Newest first. Quoted material is capped at twelve paragraphs and 240 characters each — enough to tell you what appeared, not enough to stand in for the source. Follow the link.
4How to read this
Two signals, kept apart. Every check asks the server whether the page moved, using the ETag and Last-Modified it handed over last time, and separately computes a hash over the page's extracted text. Where those two disagree the row says so. A moved ETag with a stable text hash is cosmetic churn. A moved text hash under stable server metadata means the cache headers are misdescribing the page.
Text, not bytes. Hashing raw bytes reports a change on every request, because nonces, session tokens, and cache-busting asset URLs move constantly. The hash here runs over extracted text with scripts, styles, and all tag attributes dropped. PDFs are the exception: they are hashed as bytes and labelled as such, and embedded timestamps mean a PDF can move without a substantive edit.
Observed at, not checked at. The runner is GitHub's scheduler, which is best-effort and defers under load. Times below are when an observation was written, which is the earliest the change can be asserted — never the moment it happened.
Whose clock. The watch runs on infrastructure the desk does not control. Correction, 2026-07-27: this paragraph previously said it commits under a machine identity. It does not. The workflow declares a committer address in GitHub's legacy no-reply form, which resolves to the account of an unrelated third party, so every observation commit is currently attributed to someone with no connection to this desk. The commits are real and the timestamps are the runner's; only the attribution is wrong. It is being corrected in the workflow, and this notice stays until it is. The point the paragraph was making still holds, and now holds against its own author: A monitoring record kept entirely on the operator's own machine is worth exactly as much as his word.