1. The public record is separated from the held record
The public sample gives the structure, the foreword and the introduction. The held current edition gives the requirements that apply today. The two are never blended into a single voice. A page that states a requirement says which edition it comes from. A page that reports a draft change says it is read from the contents.
2. Requirements are paraphrased, not copied
Every requirement, evidence line and preparation note is written in our own words. Only titles, defined terms and data element names stay as they are. A strict seven-word overlap test runs against the held current edition and the public draft sample before anything ships.
3. Silence is stated
If a point is not in the held text or the public sample, the field says "not stated in the text". This is why the new clauses have preparation sections rather than invented requirements.
4. The check is computed, not generated
The scope and date check runs a small set of rules in the browser from a static file. There is no model call at runtime, no upload and no account. The verdict names the rule that produced it.
5. The watch is a diff
A refresh script downloads the public sample, compares it with the record and fails loudly on a change. The diff is the alert. A missing source is a failure, never a pass.
6. Corrections are dated
When a source changes or a reader finds an error, the record changes and the date on every page changes with it. The sitemap lastmod is the record's change date.
Not legal advice; does not certify. Last updated: 2026-10-19.