One record, a retrieval date on every field, and a diff on refresh

The five steps

1. Read the official record. The ISO page for the draft is fetched and transcribed: status, stage, stage date, committee, classification, page count, price and the full lifecycle. Retrieved 2026-10-20.
2. Export the baseline. The continuity clauses come from the held framework, not from memory. The export is preflighted for placeholders, shared evidence and named bodies; this build asserts zero of each across 57 clauses.
3. Author the cloud judgement in our own words. For each clause, what the requirement means when the service is rented, and a test the customer can run. No sentence of the standard is reproduced; only clause titles and codes stay verbatim.
4. Drive every output from the one file. The pages, the check, the kit, the sitemap and the markdown versions all read the same record, so a fix cannot leave one output disagreeing with another.
5. Refresh and diff. A script re-downloads the ISO record, compares stage, date and lifecycle with the file, writes the result and exits non-zero on a change. The change is what the watch sends.

What is checked before publication

• Every page returns 200 with an HTML content type; every internal link resolves.
• Body text at 16px or larger, labels at 14px, contrast at WCAG 2.2 AA, targets at 24px, one h1, no horizontal overflow at 320 and 390.
• Every unit page is over 400 words and no two share more than a third of their sentences.
• The seven-word overlap test against the held source for every authored line.
• No model is called at runtime. The check is arithmetic on your answers and the record.

What is deliberately not stated

The clause list, the annexes and the requirement text of the draft. They are not public. A page that filled that gap would be inventing the standard, which is the one thing a record like this must never do. Read the note on Annex A.