Methodology

A term is expressed one of four ways:

1. Absolute date:“expires December 31, 2039.” Bucketed directly against today.
2. Relative to observed event:“25 years after project completion (June 3, 2010).” Resolved into an absolute date.
3. Relative to unobserved event:“25 years after project completion (project not yet observed).” Bucketed as needs base date and never silently invented.
4. Perpetual / permanent: displayed as such, bucketed 10+ years.

Non-terminated terms only are considered for the header. Terminated terms remain in the timeline for auditability.

Three sources measure related but different things:

• ACRIS is the text of the recorded regulatory agreement. It is the legal document.
• LL44 (HPD) is an HPD publication of program-level data. Its unit of analysis is the project, not the building.
• Housing Production is a building-level record of completed affordable units.

Discrepancies are surfaced as discrepancy_flag on the field. Neither value is silently discarded. The comparability matrix below documents which fields are and are not comparable across sources.

When ACRIS and LL44 disagree on a horizon-relevant field, the header shows the ACRIS extraction, because it's the legal document. The cross-check panel on the building page shows both values, side-by-side.

When ACRIS confidence is below 0.6 and LL44 has a matching value, we still show the ACRIS value in the header, but visibly de-emphasized with a lower-confidence pill. Both remain in cross-check.

ACRIS GetImage returns a placeholder TIFF for a small number of officially-recorded instruments (misfiles, redactions, or scans held under privacy holds). The extractor flags these pages and the document's scan status becomes undocumented. The metadata (party, doc type, date) still contributes to portfolio counts, but no horizon or unit-count field is emitted.

A scan is marked unreadablewhen OCR quality confidence falls below the retry threshold across at least three consecutive pages. Unreadable scans surface as a portfolio alert; the corresponding building card offers a “Rerun extraction” action but does not silently guess.

“35 years after project completion” is not a date until we observe the completion date. Records with unobserved base events are bucketed needs base date and cross-checked against Housing Production and DOB completions. If a match is found on later ingest, the record moves out of this bucket automatically; the original relative expression is retained in the audit log.

Some HPD program-level fields (recapture triggers, subordination priorities, exact AMI mix by bedroom) live behind HPD's internal firewall and are not published to open data. This product does not scrape internal systems. When a field is known to exist internally but not on open data, we mark it hpd-internal rather than guess or blank it.

When an upstream source is unavailable at ingest time we retain the last-known-good snapshot rather than dropping rows. Every table view stamps the snapshot date; every stale banner names the source that failed. The ingest run history above is the audit log for what fell over and when.

Alerts fire only on ingest deltas. If a BBL matches your rule but was already matching before the last ingest, no alert. This means alerts are cheap on a static snapshot and loud when the world actually changes.

Suppression: per-alert, either one ingest cycle or 30 days. Suppression is per-user, and per-rule.

HPD and HDC entities appear in ACRIS as free-text party names. We normalize variants (case, punctuation, LLC suffixes, historical name changes) against a published dictionary. If a variant is unknown, the record is stored but excluded from portfolio counts until an operator adds the mapping.

The table below shows the last 200 adjudicated cross-check decisions with the extracted and reference values side-by-side and the operator's reason. Every decision persists; nothing is silently discarded.

The Ask endpoint is scoped to a single document: model context is populated only with page text and metadata for the document you are viewing. External URLs are not followed; user prompts cannot exfiltrate other documents. All Ask traffic is rate limited per session and the endpoint responds 401 when the environment is token-gated. Model output is stripped of HTML before rendering.

Alert deliveries currently support in-app queue only. Email and Slack channels are planned but disabled in this build. When they land, delivery routing and per-user digest windows will appear on the alert rule editor; nothing is emailed today regardless of what a rule is configured to do.

This product surfaces the public data record for informational purposes. Nothing on this site is legal advice, and nothing here supersedes the recorded instrument or the applicable regulatory agreement. Users are responsible for confirming a horizon, unit count, or program status against the primary source before making a decision that relies on it.