Code packs.
The eight shipped packs, what depth means, and how a new jurisdiction gets built.
Jurisdictions
Rates, taxes, statutory holdbacks, permit fees and code citations live in editable JSON data packs, not in the engine. Changing jurisdiction is a data edit, not a rebuild.
What ships today
| Jurisdiction | Rules | Depth |
|---|---|---|
| Ontario | 105 | baseline |
| Florida | 16 | baseline |
| New York City | 16 | baseline |
| United States — IRC baseline | 12 | baseline |
| Canada — NBC baseline | 9 | baseline |
| British Columbia | 7 | baseline |
| California | 5 | baseline |
| England | 4 | baseline |
What depth means
baseline — the model-code requirements that jurisdiction adopts unchanged are checked; its own local amendments are not applied yet. The audit says which depth you are reading before it shows you a finding.
Every pack is currently baseline, including Ontario. The tier above it — verified, meaning every rule checked against the authority by somebody other than whoever wrote it — requires a second person, and this codebase has had one committer throughout its history. Ontario, British Columbia and California were marked verified until 29 August 2026, when that second check could not be evidenced and they were demoted. A pack returns to verified when there is a name and a date on the check, not before.
Rate, tax and cost data runs wider than the code rules do — 43 cities across Canada, the United States and Europe. See Regions & rate packs for the same check run under five different codes.