> ## Documentation Index
> Fetch the complete documentation index at: https://library.thepocketca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to read standard pages

> Understand the standard page template, status model, and source-reference pattern used across the library.

export default function StandardStatus({status = 'Current'}) {
  const palette = {
    Current: {
      background: '#E8F7F4',
      color: '#175D51',
      border: '#B9E3DB'
    },
    Amended: {
      background: '#FFF4E5',
      color: '#8A5400',
      border: '#F1D5A6'
    },
    Superseded: {
      background: '#F6F1F1',
      color: '#6A4D4D',
      border: '#DDCACA'
    }
  };
  const tone = palette[status] || palette.Current;
  return <span style={{
    display: 'inline-flex',
    alignItems: 'center',
    padding: '0.28rem 0.72rem',
    borderRadius: '999px',
    fontSize: '0.85rem',
    fontWeight: 700,
    letterSpacing: '0.01em',
    background: tone.background,
    color: tone.color,
    border: `1px solid ${tone.border}`
  }}>
      {status}
    </span>;
}

## The page pattern

Every canonical standard page follows the same reading order:

1. `At a glance` for fast scanning
2. a plain-language explanation for mixed audiences
3. the detailed requirement structure with blended commentary
4. effective dates, amendments, and status
5. 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.

<InterpretiveNote title="Interpretive commentary">
  Use interpretive commentary to explain where the real judgment sits, what readers often misunderstand, and how the source requirements fit together.
</InterpretiveNote>

## 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.

<SelectiveExample title="Selective example">
  If two promises in a contract look separate on paper but are not separately identifiable in context, the revenue pattern may need to be assessed as one combined performance obligation rather than two separate ones.
</SelectiveExample>

## Status labels

The status label tells you how to treat the page in the corpus.

<StandardStatus status="Current" /> current guidance you should read as the live reference page.

<br />

<br />

<StandardStatus status="Amended" /> current guidance with important amendment history you should review.

<br />

<br />

<StandardStatus status="Superseded" /> 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.

<SourceReference document="Example source document" paragraphs="¶9, ¶22-30, ¶31-38" note="Reference styling is standardized across the library so you can spot source anchors 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.

<SupportingMaterialNote materialType="Illustrative examples" purpose="Used to enrich commentary and explain application">
  Supporting material can deepen understanding, but it should not be presented as if it were the same thing as the core mandatory requirement.
</SupportingMaterialNote>

## How to use a canonical page

* Start with `At a glance` if 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.