How the record is made and checked.
One record drives the pages, the free check, the kit and the refresh diff. That is the rule that keeps a page and a download from disagreeing.
1. Read the authorised text
We downloaded the authorised PDF of C2026A00064, registered 7 July 2026, and read every operative provision. The record's source is the Federal Register of Legislation, not a summary.
2. State the requirement in our words
Every requirement, evidence line and action is written in our own words. The strict seven-word overlap test runs against the Act and against the Australian Consumer Law text the Act amends. Only titles and defined terms stay verbatim.
3. Keep the source on every field
Each unit carries the pinpoint citation, the party bound, the dates, the cross-references and a source pointer. Where the Act is silent or leaves a detail to regulations, the field says so.
4. Hold the duty provisions as controls
The five provisions that place a duty on a supplier are held in the standards record with evidence artefacts. The other eighteen units are scope, application, enforcement or machinery, and are marked as such.
5. Refresh and diff
The refresh script re-downloads the authorised text, hashes it and compares it with the snapshot behind the record. A change fails loudly and produces the diff the watch sends. A clean run prints a hash and a pass.
6. No runtime model
The site makes no model call at runtime. The pages are static, the check is arithmetic on the record, and the kit is rendered from the record at build time.
What the record cannot do
It cannot decide a design question, a surcharge classification or a standard form question. Those need the facts and a lawyer. The record gives the provision and the evidence, and says where the judgement starts.