Data Rules

Five working rules, separated by purpose and adoption state. Use this section to understand a decision; use Contracts for the normative requirement.

Permit classification at a glance

Three surfaces, three states. The version numbers are not interchangeable.

Identity and classification

Rules that decide which property or category a source record belongs to.

First American property match ARS-standardized address first, APN fallback, one scalar fa_propertyid or quarantine. Adopted contract rule Permit classification One ledger for the proven-local Silver taxonomy, lake labels, the local overlay and the proposed v2.2.2 contract amendment. Mixed state · review first Owner type heuristic Separates entity type from mailing eligibility. Whole-token rules and structured fields take priority over name fragments. Reference design

BuildZoom ingestion operations

Policies for keeping source history and making the large permit delivery practical to process.

Full refresh and retention Monthly upserts, quarterly reconciliation and 12-month retention for inactive records. Adopted sandbox policy Faster format Raw gzip stays auditable; validated Snappy Parquet becomes the only optimized Bronze input. Full sandbox run validated · 2026-06-25

Reading rule: “proposed” and “candidate” are not production states. The permit classifier remains blocked on producer agreement and the signed 365-row CLS-04 golden set. See Contracts for adopted obligations and Resources for source dictionaries.