Glossary¶

Terms used throughout the documentation, defined once here and linked from wherever they appear.

Lead funnel / tier¶

A building progresses through a three-stage funnel as evidence accumulates:

candidate — an unqualified building record.
PHQL ("probable high-quality lead") — one confirmation short of HQL.
HQL ("high-quality lead") — fully qualified.

Progression is driven by the locator-friendliness verdict, commission terms, and contactability. See the commission section of Grains, Keys & Amenities Model for how those verdicts are derived.

`lead_score`¶

A 0–1 blended score, Bayesian-shrunk, combining locator strength, commission, review signal, and reachability. Used to prioritize and rank buildings.

Street key / `join_key` / `building_key`¶

The canonical identifier used to merge records about the same building across every data source. See Grains, Keys & Amenities Model for how this relates to the warehouse's property_id.

Off-spine lead¶

A building found via its own website that none of the listing aggregators carry.

Grain¶

The level of detail a row represents: building, floorplan, or unit. See Grains, Keys & Amenities Model for the full model.

Provenance tag¶

A per-field label — scraped_live / derived / hud / seed — recording how a value was obtained. See Grains, Keys & Amenities Model.

Locator-friendly / commission confidence ladder¶

See the commission evidence & confidence section of Grains, Keys & Amenities Model rather than duplicating the ladder here.

`plan_key`¶

The cross-source floorplan-identity cluster key. See floorplans.plan_key.

Metro slug vs. partner short-code¶

The two coexisting metro-naming vocabularies used across the warehouse and comparison surfaces. See Warehouse Schema.

HQL quality gate¶

The post-upsert check — is-a-building, distinct, commission-actionable, usable-contact, has-info — that can downgrade a building's tier. Runs after every union-wide warehouse upsert; see Data Pipeline architecture.

Rent observation¶

One price reading of one unit from one source on one date. See Rent Observation Ledger.

Refresh cadence (standard vs. priority)¶

How often a served building's price is re-verified:

Standard tier — re-prices roughly weekly.
Priority tier — re-prices roughly daily.

Both rates are configurable per-property (refresh_policy) and platform-wide (refresh_settings), and priority status decays after a configurable TTL so a request cannot ratchet spend upward indefinitely. See Warehouse Schema and Data Pipeline architecture.