The method behind the notes.

Make the source traceable. Keep the interpretation bounded. Leave uncertainty visible.

Evidence workflow: read the source, establish scope, preserve evidence123Read the sourceEstablish scopePreserve evidence
An editorial workflow. Each transition needs a documented decision.

Two evidence statuses

Requirement means that the linked official source explicitly supports the narrow summary in our record. It does not mean that the statement applies to every reader or that a product has been assessed. Each requirement needs a locator, scope and review date. The entire applicability section remains relevant even when a short summary cannot reproduce it.

Context only means that a source helps orient a question but is not being used as a confirmed requirement. Application pages, register landing pages and documents with unresolved version status can all be useful in this category. We do not promote a contextual source into a requirement because its publisher is authoritative.

Editorial implementation suggestions use language such as “we suggest” or “an example design”. Synthetic scenarios are labelled. They are original explanatory devices, not observed incidents, interviews or regulator-approved patterns.

Three dates, three meanings

Publication / revision
When the source was issued or changed, if that fact is established.
Effective date
When the particular provision takes effect. Amendments can have different commencement dates.
Last checked
When we read the cited source for this edition. It is not a guarantee that the source is unchanged today.

Unknown effective dates are recorded as “Not established”. We do not substitute a web page’s update date, the document’s original commencement or the date we accessed it. A future requirement would need a distinct pending status and a clear commencement note; this edition contains no pending requirements.

From source to publication

  1. Identify the document

    Use an official publisher, a stable URL where available and a specific locator. Confirm that the page resolves and contains the passage being discussed.

  2. Read the boundaries

    Record jurisdiction, document type, licence or activity scope, exclusions and version uncertainty. Avoid a conclusion broader than the evidence.

  3. Write the analysis

    Paraphrase narrowly, then distinguish our practical questions and examples from the source. Link the relevant dossier and related brief.

  4. Check the record

    Validate IDs, dates, source links and status. Review the visible text alongside the exported fields so that an export keeps the same caveats.

Corrections and unresolved questions

A correction should identify the affected page or record ID, the exact disputed statement and the official source that supports a change. Preserve that information when raising an issue with the publication owner. This edition has no public submission form or verified editorial email address; we do not publish a fabricated contact.

When an error is established, the intended editorial process is to update the affected statement, record the reason and date, and reconsider any dependent brief or matrix entry. If a source becomes unavailable or its status cannot be established, the record should be withdrawn from the requirement set until reviewed. These are editorial commitments, not claims that an external review has occurred.

Edition record

Published content changes
DateChangeScope
16 November 2026Initial research editionFour briefs, two jurisdiction dossiers, eight source records

Read the publication statement for identity and limits, or inspect individual source notes in the matrix.