The page pattern
Every canonical standard page follows the same reading order:At a glancefor fast scanning- a plain-language explanation for mixed audiences
- the detailed requirement structure with blended commentary
- effective dates, amendments, and status
- related standards and source references
Commentary and interpretation
The page is not meant to read like copied legislation or copied standards text. It is allowed to behave like a textbook chapter that rewrites and interprets the source material in a clearer narrative.Selective examples
Examples should appear only when they clarify a difficult judgment or recurring confusion. They support the narrative, but they should not overwhelm it.Status labels
The status label tells you how to treat the page in the corpus. current guidance you should read as the live reference page.current guidance with important amendment history you should review.
historical guidance that has been replaced by another current page.
Source references
Generated summaries stay traceable through visible paragraph-level mapping. The source callout is there so you can move from the generated explanation back to the underlying source quickly.Supporting material labels
When the page uses appendices, illustrative examples, basis-for-conclusions material, or similar non-mandatory text, it should label that material clearly.How to use a canonical page
- Start with
At a glanceif you already know the standard. - Read the plain-language layer if you need context before details.
- Expect commentary and interpretation to be blended into the main narrative.
- Use the source references when you want to verify the underlying text.
- Use related-standard links when the issue crosses frameworks or touches adjacent guidance.