Editorial, Sourcing, and Corrections Policy

Primary-source standard

Regulatory claims must be supported by a government statute, administrative rule, agency program page, official form, or government enforcement dataset. Secondary sources can help locate a rule but cannot be the sole support for a material compliance claim.

Page review

1. Identify the agency and controlling legal sources.
2. Verify each structured field independently against its cited source.
3. Record the verification date and a plain-language changelog.
4. Run build, link, schema, and required-field checks before publication.
5. Recheck source availability automatically and review material source changes before updating a claim.

Use of automation and language models

Automation checks source availability and detects changed source content. A language model may summarize a changed source or prepare a draft for review. It may not invent a source, create an unsupported legal claim, or publish a regulatory change automatically. A source-linked review is required before a draft becomes editorial content.

Corrections

Material errors are corrected in the structured source record and documented in the page changelog. A correction should identify the page URL, disputed statement, controlling primary source, and effective date. A direct public correction channel is being configured; until it is live, readers should rely on the linked agency sources for current obligations.

Update frequency

Source URLs are checked weekly. A successful automated check does not prove that a legal interpretation is current. Pages retain their visible last-verified date until their substantive claims have been reviewed.