Home / Method
How each record is written and checked
Five steps, applied to every clause page. The method is the product: a record that cannot be checked is a summary, and a summary is what a review rejects.
| Step | What happens |
|---|---|
| The official record | Read the ISO catalogue entry and its machine feed for the designation, edition, stage, stage date, committee, ICS and page count. Record the date read. |
| The public text | Read the publisher preview of the 2009 edition for the contents, terms, notation and the clauses it exposes. Where the text is not public, say so rather than infer. |
| Our own wording | Write the requirement, the evidence and the test in our own words. Only titles and defined terms stay verbatim. Run the overlap check against the source and the prior edition. |
| The evidence and the test | Name the artefact an auditor samples and the test a reader can run. A page without both is a summary, not a record. |
| The refresh | Re-read the public record on a schedule, diff it against the data file, and fail loudly on any change. That diff is what the watch sends. |
The overlap rule
Every requirement, evidence line and test is written in our own words. Nothing ships until a strict seven word overlap check against the source and its prior edition comes back clean. Only titles, defined terms and data element names stay verbatim, because a defined term has to be quoted to be useful.
What the record does with a gap
Where the public text is silent, the page says so. It does not fill the gap from memory, from a search snippet or from another standard. A reader can therefore tell what is sourced, what is inferred and what is not public, which is the difference between a record and an opinion.
What the refresh does
It downloads the public record, compares the fields it can read with the data file, and fails loudly on any change. It does not silently update the record. A change is a decision, and the diff is the thing the paid watch sends.
Not legal advice; does not certify.