How these pages are built

Source capture

1. Primary sources only: Texas statutes / enrolled bills, eCFR, and named regulator FAQs when labelled as readings.
2. Where possible, text is sliced from a fetch file and re-checked with quote-verification scripts — not hand-typed from memory.
3. Each stored section keeps url, last_verified, and optional effective_from.

Presentation rules

• Every calculator output block carries citations with links and verification dates.
• Regulator FAQ language is labelled “Regulator reading — not statutory text.”
• Pages state what the text does not cover when a common question has no answer in the statute.
• No page asserts a lawful / unlawful verdict about the reader’s facts.

Automated gates

Before a build ships, the project runs a compliance gate over the real dist/ HTML, DOM smoke tests against each calculator, unit tests on the engines, and needle checks that shipped strings still match the data layer. A self-test injects violations to prove the gate still fails when it should.

Re-verification

Statutes change. Treat every last verified date as a snapshot, not a promise of perpetual currency. Re-check the official URL before relying on a page after material time has passed.