How the record is built

The steps

1. Read the official record and the public preview. Record the retrieved date and the source URL.
2. Build one JSON record with a unit per clause area, defined term and annex section. Each field points to its source.
3. State every definition and requirement in our own words. Only titles and defined terms stay verbatim.
4. Run the seven word overlap test against the source. Fix any field that overlaps.
5. Generate every page from the record, then run the refresh script against the live record.
6. Deploy, run the smokes, the UX audit and the link check. Record the results.

Claim levels

This document is mostly vocabulary, concepts and principles. Most rows are not shall requirements, so every row states what it is: definition, concept, principle, annex note or scope statement. A reader can then tell an obligation from an explanation, which is the difference that matters in an audit.

What the overlap test covers

Every authored field, including definitions, practice guidance, evidence lines, gaps and preparation. The test strips punctuation and compares seven word sequences against the source. A single overlap fails the run.

Limits

The bodies of clauses 4 and 5 and of Annexes A and B are not public. The record covers what is public, and says so on every affected page. A later release can add clause level detail when the published edition is available.