Data engineering surface · read-only

Data, provenance & field coverage

Everything on this page is fetched from a live PostgREST view when the page loads, and the view name is printed next to each panel so it can be queried independently. Nothing on this page is a stored number in the HTML, and nothing here is a rent reasonableness determination — this is the evidence layer underneath the determinations, not a determination. Where a value is not available it reads unknown; it is never shown as zero.

Field coverage Derived scores Provenance lineage Gap remediation Source documents Roadmap

Field coverage Per-field fill rate across the comparable pool

Derived scores Grade and confidence distribution, plus what MQI actually is

Why the MQI coverage figures read "unavailable this session". MQI coverage is measured against the rent pool of one specific state, which is only loaded once you sign in and pick a PHA. Rather than display a national average as if it were your state's, this page leaves it unresolved. Sign in on the workspace to see it for your own state.

Provenance lineage Identity discovery and rent observation, tracked separately

Gap remediation What is missing, how much of it, and what is being done about it

Source documents The register of documents behind the identity lineage

Roadmap Adjacent compliance work, not yet shipped

COMING NEXT IN THIS WORKFLOW

HOTMA income & asset module. Mandatory PHA compliance for HOTMA §102 / §104 begins January 1, 2027 (Notice PIH 2026-15). Asset limits are already in effect as of 1/1/2026 — net-asset ceiling ≈ $105,574, self-certification threshold ≈ $52,787. The HOTMA income/asset engine (TTP → HAP → Family Share, with the 40% initial-occupancy cap) is planned as the next step in this workflow.