HUD already scored the property. The household still lives with an outlet, a door, or a heat source that the score did not count. Starting October 1, those items count. That join is the product.
The idea mills keep minting a tenant chatbot, a work-order filler, and a “pass your REAC” micro-SaaS. Three names. One object. A defect in the unit that does not sit next to the public inspection file the department already posted.
The unit is not the file
Most residents treat the inspection as weather. A clipboard appears. Someone knocks. A number lands on a HUD USER spreadsheet months later. The household never sees the join: last score, last inspection date, property identifiers, and the six affirmative requirements that were cited but not deducted.
Notice PIH 2025-27 / H 2025-06, issued September 30, 2025, pushed the scoring date for those new affirmative requirements to October 1, 2026. HUD had already delayed once, to October 1, 2025. The extra year is over. The notice names the items that start taking points: fire-labeled doors; an unprotected outlet within six feet of a water source; guardrails; HVAC; interior lighting; and minimum electrical and lighting. HUD USER posted physical inspection scores through April 8, 2026 as downloadable files for public housing and multifamily assisted properties.
That is not a vibe. That is a published scoring clock landing on the same week vision models can read a kitchen outlet and a property score without a REAC consultant in the room.
The HUD Office of Inspector General’s July 24, 2026 evaluation (2026-OE-0802) pulled NSPIRE results for properties that scored 70 or below from March 1, 2025 to February 28, 2026. Of 469 public housing properties in that slice, 373 — 79.5 percent — scored below 60. Those inspections covered 5,491 buildings and 8,658 units and recorded 20,360 life-threatening and severe deficiencies. OIG also wrote that scores are expected to decline once habitability items are scored. NAHRO’s analysis, cited in the trade press this week, found public housing scores rose about 13 points after the switch from UPCS, and multifamily scores rose about 6, with unscored affirmative requirements as part of that cushion. The cushion ends tomorrow.
Who checks, who does not
The gap is not “people hate housing authorities.” The gap is who can put a photo of the unit next to the last published score before the next inspection window, the next work order, or the next complaint that becomes a record.
A resident already holds the object. Address on the lease. Outlet by the sink. Door closer that does not latch. Heat that does not reach 68. HUD already published a property-level score and an inspectable-area rulebook. The product is the join.
Do not build “AI for property managers” or “AI for tenant rights.” Those slogans die in a demo. The customer is holding a phone in a kitchen. They want to know if the outlet is the unprotected kind the notice now scores, if the last file already flagged the property, or if the unit is fine.
Two primitives, one wedge
Primitive one is photo-and-PDF review. The mills have been shipping receipt readers and home-health paperwork agents for months. Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting that reader into a work-order bot, a “pass REAC” coach, and a housingcheck.ai. The input here is a photo of the inspectable item plus the address on the lease or the property name on the building. Outlet. Door label. Guardrail. Thermostat. Kitchen light.
Primitive two is the public inspection file. HUD USER already ships comma-delimited scores. The NSPIRE standards and the scoring notice already list what an inspector must cite. The checker does not invent a fair apartment. It joins the photo to the last published score and the defect family that starts taking points on October 1, or it says the join failed and why.
The first action a stranger will take this week is upload. Phone photo of the outlet by the sink. No account required to see the first verdict: scored item, not scored, property not in the HUD file, or photo too thin to judge. If it matches a scored family, you still captured a labeled pair. If the property is not assisted housing, you say so and stop. That honesty is the product.
That is the only honest offer on day one. Do not ask them to connect a Yardi feed. Do not ask a housing authority to install anything. Do not scrape every PHA work-order system before you have watched a hundred kitchens fail a join.
The chatbot is a flag, not the company
A product that only talks will recreate the old legal-aid intake gap in cheaper clothes. The wedge is the labeled join, not another chat pane on top of a blurry outlet.
Hallucinated inspection IDs are how this category gets banned from the front desk. Cite the HUD USER file date. Cite the notice. Cite the defect family. Do not cite a score the model dreamed.
A checker that points at the real PHA complaint process or the real HUD hotline is useful. A checker that invents a federal “housing refund request” is a scam adjacent. Same rule as the tax essay: point at the real form or shut up.
What compounds
The first useful output is a three-line verdict. The business is the labeled corpus.
After a few thousand photos you know which properties post a passing score while kitchens still show unprotected outlets, which authorities close work orders without touching the scored item, which multifamily owners pass building systems and fail in-unit electrical, which files on HUD USER are current and which are theater. That map is what a legal-aid housing desk, a PHA inspector trainer, an owner’s insurance desk, or a city council watchdog will pay for. Not another portal. A ranked list of properties where the unit photo and the published score refuse to meet.
Do not sell the map first. Close real questions on real photos. The dashboard of “possible habitability savings” is how this idea dies in a pitch.
Irreversible steps stay human
A model can draft the work order. It can pull the last score and write the mismatch paragraph. It can calendar the mitigation window that already exists under NSPIRE severity categories. A person owns the send. A formal complaint, a request for tenancy termination, or a claim that the unit is uninhabitable creates a record a court will treat as a claim. Same rule we use on every filing in this shop: the model drafts, a named human signs.
Do not let the product call itself counsel of record. Do not let it file the complaint, accept a contingency check, or speak at the informal hearing. Those are seats, not features. Charge after the join shows a scored defect the file did not absorb, or do not charge.
What not to build
Do not build a nationwide housing platform in month one. You will drown in HCV units that are still on a later NSPIRE clock, city code that is not NSPIRE, and market-rate buildings that have no HUD file at all.
Do not scrape every PHA site on day one and call it a marketplace. Most addresses will fail a join. Your first hundred uploads teach you which columns actually exist.
Do not brand this as an agentic housing copilot. The sentence attracts the wrong first ten users and the wrong first ten housing lawyers.
A build order that will survive contact
- Week 1–2: one checker. Photo plus address in. Scored item, not scored, not in file, or photo too thin. No account for the first answer. One metro, public housing and multifamily only.
- Week 3–4: a draft work-order or complaint pack with a human signer. Defect family, last published score, notice citation. Contingency or a cheap per-letter fee only after the first free verdict.
- Month 2: add a second photo type for the same unit — door closer, heat register, bathroom fixture. Keep one metro until the join rate is honest.
- Month 3: publish the first ugly internal scoreboard. Properties, defect families, mismatch rates against HUD USER. That scoreboard is the seed of the B2B SKU.
If you cannot get a stranger to photograph one outlet this week, you do not have a company. You have a policy thread.
Why this cut, not the last one
The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. The tax essay was a notice against the roll. The utility essay was a statement against a filed tariff. This one is the housing version of the same primitive pair: a photo the resident already can take, plus a public file the institution was forced to publish, joined on the week the grace period ends.
The noticing used to require a housing counselor and a weekend. It now requires a model that can read the outlet and a person who will sign the form. Recovery still works because the first check costs the resident almost nothing. Charge them after the score file and the photo refuse to meet, or do not charge them.
Someone will own the labeled map of unit versus score. The mills will keep proposing a new .ai name for each inspection form. Ignore the names. Join the line. Keep the map.
Will Tygart — Tygart Media.
This is the idea-mill series.