One provenance surface, two views. The Data register tab is our engineering-grade register —
written for your IT staff, data analysts, and auditors who want to verify our numbers at the database
level. The Source status tab is the plain-English board of every named source behind the
workspace and where each one stands right now. For controls and audit posture, see
the Compliance Register.
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 coveragePer-field fill rate across the comparable pool
Derived scoresGrade 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
signed-in workspace to see it for your own state.
Provenance lineageIdentity discovery and rent observation, tracked separately
Gap remediationWhat is missing, how much of it, and what is being done about it
Source documentsThe register of documents behind the identity lineage
All live countersEvery production metric the platform tracks, not just the homepage's featured six — read live at page load
Loading the live counter catalog…
Planned workAdjacent 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.
Everything the workspace shows you comes from a named public source that was qualified before a single
row rendered. This board reads the live source registry each time you open it and tells you plainly:
what has arrived and is on your desk, what is loading right now, what is qualified
with a load scheduled, and what is still under review. A source under review renders nothing
to you until it graduates. Counts are measured rows in the database, never estimates.
Reading the live source registry… every count on this page is fetched from the production database at load, so a slow moment here is the real read, not a spinner over cached data.
The source registry could not be reached just now. Nothing is hidden — this page only shows live-read data, so it declines to show anything it cannot verify. Refresh to retry.
What this board is not: none of these context sources ever enters a rent reasonableness
determination. Determinations use only the nine 24 CFR 982.507(b) factors from directly observed,
source-linked comparables. Neighborhood and building context is shown to you as context, labeled with
its geographic grain, and nothing here is ever blended into a score. Sources listed under review are
candidates surfaced by our catalog harvester; each must pass terms-of-use and fitness review before
it loads. This page never shows a modeled or projected number.
Regulatory Watch polls a subset of the regulators that oversee a public housing
authority — not all of them. This board lists every authority in our own Oversight Authority Atlas
(compiled September 2, 2026, sourced line-by-line to Federal Register, eCFR and agency pages) and states
plainly whether RegWatch’s harvester actually polls it on a feed (automated), whether it is tracked
by a person instead of a feed (manual), or whether RegWatch does not track it at all (untracked).
Every count on this board is read from a file generated directly from the atlas document and the harvester’s
own registered-source list at build time — nothing here is hand-typed prose that could drift from what the
harvester actually does.
Reading the generated authority atlas…
The generated authority atlas file could not be read. Nothing is hidden — this board only shows generated data, so it declines to show anything it cannot verify. Refresh to retry.
What “automated” means here. RegWatch’s harvester (regwatch/harvest.py) polls the
Federal Register API and the Grants.gov Search2 API on a daily schedule for the authorities marked automated
below. Every authority marked manual or untracked renders no live feed entries in RegWatch today — a PHA
relying on RegWatch for those authorities should keep its own watch. This board is refreshed whenever
data/authority_atlas.json is regenerated (npm run authority-atlas-build); today that is a manual
step run alongside each atlas or harvester change, not yet wired to the harvester’s own daily cron —
see the Regulatory Watch page’s own honesty notes for why that wiring is out of scope for this update.