Personalization layer: 32 county-assessor adapters, 45 historic-overlay polygons

When a homeowner types their address, AskBaily can now infer in under three seconds whether the parcel sits inside an HPOZ, what year the structure was built, what the assessor's last-sale value was, what climate zone the city is in, and whether the building style suggests structural quirks (post-and-beam vs. balloon-frame vs. stick-frame). Wave 292G is the data spine that makes that personalization possible.

The 32 county-assessor adapters are the hardest part of the work and the part nobody publishes. Every county has its own search endpoint, its own field names, its own concept of "owner of record," and its own update cadence. LA County publishes through ArcGIS REST. NYC's ACRIS is its own stack. Cook County publishes through a different ArcGIS stack with completely different schemas. Miami-Dade has two services that have to be joined. Harris County (Houston) returns parcels keyed by HCAD tax ID, which does not always align with the address. Maricopa County (Phoenix) has the cleanest API of the 32 and was the easiest to integrate.

The shape that came out of the work is one normalized ParcelLookup interface in lib/personalization/types.ts that returns, for any address: assessor parcel number, last-sale value (where public), year built, square footage, lot size, owner type (individual vs. trust vs. LLC), zoning district, and a "data confidence" score capped by the source. Each adapter implements this interface in lib/personalization/assessor-providers.ts plus per-county files. parcel-lookup.ts is the dispatch table.

The 45 historic-overlay polygons cover every named historic district in the cities where overlays meaningfully change the permit pipeline. LA HPOZs (35 districts), NYC LPC (143 districts, but we ship the 6 highest-volume), Boston Article 11 (3 districts), Charleston BAR (one large overlay), Savannah HSPB, San Francisco Article 10, the LA Mills Act overlay (separate from HPOZ). Each polygon is GeoJSON in lib/personalization/historic-overlays.ts with a citation to the city's open-data portal. The lookup is point-in-polygon, computed at request time, served from the edge.

hoa-detection.ts uses a heuristic stack: zoning district hints, master-association lookups in counties that publish them (Maricopa, Orange, Riverside), and a fallback "we don't know — ask the homeowner" mode that does not pretend to be definitive. We do not publish HOA membership data because most counties do not publish it cleanly.

climate-zones.ts maps city + zip to ASHRAE climate zones (1-8 and the A/B/C subdivisions) so the homeowner gets accurate insulation and HVAC sizing references without us inventing data. building-style-inferrer.ts reads the year-built from the assessor and combines with regional norms to suggest a probable building style — a 1922 LA bungalow is post-and-beam; a 1958 Phoenix ranch is stick-frame; a 1908 NYC brownstone is masonry-bearing wall. The inferrer is best-effort and the confidence is rendered honestly.

67 tests cover the 32 adapters' shape contracts, the 45 polygons' point-in-polygon math, the climate zone lookup, and the inferrer's known-good fixtures. We do not test against live county endpoints (rate limits, instability) but ship recorded fixtures so the suite runs offline. The county adapters fall back to "address could not be resolved against the assessor" gracefully — better to admit a miss than fake a hit.