A free public-service alert system from Apollo Benz Productions. This alert curates documented reporting; it does not investigate.
Alert · September 29, 2026
The word is "consistency"
The signal
HUD has proposed to remove the parts of its civil rights rules for the programs it funds that reach a policy by what it does, and not only by what it was meant to do. The proposal was published in the Federal Register on August 10, 2026, as document 2026-16228. The comment window closed on October 9, 2026, at 11:59 p.m. Eastern.
The word
“Consistency.” It is the first benefit HUD names. The notice says that if finalized, the rule “would improve consistency within HUD's own regulations and between HUD's regulations and the Title VI regulations recently revised by the Department of Justice.”
Here is part of what the consistency is made of. HUD's rule on the site or location of housing, accommodations, or facilities in the programs it funds says an applicant or recipient “may not make selections with the purpose or effect of excluding individuals from, denying them the benefits of, or subjecting them to discrimination” on the ground of race, color, or national origin. HUD proposes “to remove both instances of the phrase ‘or effect,’ because they extend to unintentional discriminatory effects.” The executive order HUD is carrying out names the same two words, “in both places they appear,” in the Justice Department's matching rule.
Two words come out. What is left in that paragraph forbids a site chosen for the purpose of excluding people on the ground of race, color, or national origin. A site that ends up excluding people on those grounds, without having been chosen for that purpose, is no longer reached by it.
What it actually does
Title VI of the Civil Rights Act of 1964 bars discrimination on the ground of race, color, or national origin in programs that receive federal money. HUD's rules for carrying it out sit at 24 CFR part 1, and the notice says they were last substantively amended in 1973.
The proposal takes out four pieces. It deletes the general ban on a recipient using “criteria or methods of administration which have the effect of subjecting persons to discrimination because of their race, color, or national origin.” It strikes “or effect” from the siting rule. It removes the whole affirmative-action paragraph, which says a recipient that discriminated in the past “must take affirmative action to overcome the effects of prior discrimination.” And it removes a paragraph reaching discrimination in a recipient's employment practices that “tends” to exclude people from a program, where the funding is not for employment.
HUD gives its reasons in its own words. It writes that Title VI prohibits “only intentional discrimination,” citing the Supreme Court in Alexander v. Sandoval (2001), and that disparate-impact rules push recipients to consider race in ways the Equal Protection Clause forbids. It writes that it “agrees with and adopts the rationale” of a Justice Department rule issued December 10, 2025.
This is a proposal, not a final rule. The same notice reopens comment on HUD's January 14, 2026 proposal to remove its separate Fair Housing Act disparate-impact rule and “leave interpretation of disparate-impact liability under the Fair Housing Act to the courts.”
Who it hit
These rules bind the recipients of HUD funding, the states, local governments, public and private agencies and organizations that carry out HUD-funded programs, and they protect the people those programs serve. For scale, the notice counts about 4,412 grants and 5,393 subsidies, totaling about $170 billion, in calendar years 2023, 2024 and 2025. HUD says that figure does not “represent the monetary impact of the rule.”
The people these paragraphs protect are the applicants, tenants and participants in those programs, and anyone a siting decision can shut out of one. The paragraph losing “or effect” is the one that governs where housing, accommodations and facilities are placed.
HUD reports 500 active and 585 closed Title VI investigations and compliance reviews over those three years. It also writes that it “does not track which of its investigations and compliance reviews involve solely allegations of disparate-impact discrimination.”
What to do
The comment window closed on October 9, 2026, at 11:59 p.m. Eastern. HUD did not extend it.
What comes next is a final rule, and it can publish any day. Everything HUD publishes on this rule carries the same Regulation Identifier Number, 2529-AB09, and the Federal Register lists it under that number.
Updated after publication
- : 🔴 CORRECTED 2026-09-29, HOURS AFTER PUBLICATION, on Apollo's “correct.” The posting curator, gating the social posts drawn from this alert, found that the word section still called the siting paragraph “HUD's rule on where federally funded housing goes.” That is wrong in both directions: part 1 covers the programs HUD funds, not all federal housing money, and the paragraph reaches “housing, accommodations, or facilities,” in its own words. The receipt gate had corrected the same scope error in this alert's signal and missed it here. The same section said the paragraph that remains “forbids a site chosen on purpose,” which dropped the grounds the rule names. Both now read as the rule reads, and “what the consistency is made of” now says “part of,” because the siting change is one of four.
- : 🔴 CORRECTED 2026-10-11, ON APOLLO'S “correct.” The comment window this alert pointed to closed at 11:59 p.m. Eastern on October 9, and its claimExpiry entry for “Comments are due by October 9, 2026” came due on October 10 (PROOF row, signal forge claim expiry, FAIL). Re-read 2026-10-11 at the authority: Regulations.gov v4 API, document HUD-2026-0034-0609, commentEndDate 2026-10-10T03:59:59Z unchanged, openForComment false, so no extension. The signal now says the window closed; whatToDo, which was spent with the window, now says it closed and names the RIN a final rule will carry; the spent claimExpiry entry is removed. Second read, same day: the Federal Register API lists two documents under RIN 2529-AB09, both Proposed Rules (2026-00590, January 14; 2026-16228, August 10), and the current public inspection list carries no HUD rule, so “This is a proposal, not a final rule” still holds and keeps its October 15 expiry. Nothing else in the alert changed.
The receipts
- Primary, re-read 2026-10-11 through the Regulations.gov v4 API: document HUD-2026-0034-0609, commentEndDate 2026-10-10T03:59:59Z, openForComment false. Federal Register API, same day: two documents under RIN 2529-AB09, both Proposed Rules. Trust tier: primary.
- Primary, read in full 2026-09-29: HUD's supplemental notice of proposed rulemaking, 91 FR 51416-51421, FR Doc. 2026-16228, as the Government Publishing Office text rendition served by the Federal Register, cross-checked against the govinfo PDF extracted with pdftotext. Every sentence this alert attributes to HUD or to “the notice” was read there, including the counts of grants, subsidies and investigations. The quotation beginning “does not track” runs across the page break to 91 FR 51420; the words are exact and the page marker is not part of them. Trust tier: primary.
- Primary, read 2026-09-29: 24 CFR 1.4 as it stands, from the eCFR versioner API at the point in time 2026-09-25. The siting sentence and the “must take affirmative action” sentence are quoted from the rule itself, not from the notice's description of it. Who the rules bind and cover was read in the whole of part 1: section 1.2(f) defines a recipient and says the term “does not include any ultimate beneficiary,” and section 1.3 applies the part to “any program or activity for which Federal financial assistance is authorized under a law administered by the Department.” Trust tier: primary.
- Primary, read in full 2026-09-29: Executive Order 14281, 90 FR 17537-17539, as the Government Publishing Office text rendition. The phrase “in both places they appear” is from Section 3(b). Trust tier: primary.
- Primary, read 2026-09-29 through the Regulations.gov v4 API: document HUD-2026-0034-0609, commentEndDate 2026-10-10T03:59:59Z, openForComment true. That is 11:59:59 p.m. Eastern on October 9. Trust tier: primary.
- Secondary, raw HTML read in full 2026-09-29: Renee Williams, NLIHC, August 10, 2026. Used only as an independent third read of the deadline. Trust tier: secondary.
What verification changed before this published
- APPROVED AND PUBLISHED 2026-09-29, Apollo: “approve,” on the text now published. The approval brief proposed publishing Wednesday 2026-09-30; the alert deployed the evening of 2026-09-29 instead and carries that date, because a deploy is a publication and the record states the day it went live.
- PICKED 2026-09-29 ~19:40 CDT, Apollo: “HUD”, candidate #1 of the scout batch of 2026-09-28, after his “pass” on #3 the night before.
- 🔴 CORRECTED AT THE GATE, THE WORD: the scout batch gave the word as HUD's own description, “align... with the statutory text.” That phrase does not appear in HUD's notice. Bare matches on the full text: “align” three times (“would also align with DOJ's 2025 final rule,” “aligning HUD's Title VI regulations with the best reading of Title VI and DOJ's revised Title VI regulations,” and other agencies amending “to align with the changes made in this rule”), “statutory text” once, inside the TITLE of the Justice Department's December 2025 rule, which the notice cites by name. The ellipsis joined words that never share a sentence. The nearest match found is another agency's title: the Department of Education's rule of 2026-07-24 (FR Doc. 2026-15019) is titled “Rescinding Portions of the Department of Education Title VI Regulations To Align With the Statutory Text and Conform to Executive Order 14281,” per the Federal Register API; that rule was not read beyond its title. The word was re-chosen from HUD's own text: “consistency,” the first benefit the notice claims for itself. The choice of word is Apollo's to rule before publication.
- FOUND AT THE GATE, after the scout recorded both NOT LOCATED: HUD's notice and Executive Order 14281. The scout reported a CAPTCHA on federalregister.gov and an unrendered PDF. The Federal Register's API and its GPO text renditions answered a scripted read, and pdftotext is installed at /opt/homebrew/bin. The alert rests on both documents, read in full, and on no law-firm summary of either.
- CUT, the scout's UNVERIFIED FRAME: algorithmic tenant screening, insurance underwriting and lending standards as examples of what these rules reach. None of the three is named in HUD's notice, in the rule, or in the executive order. The Title VI paragraphs the notice removes are about criteria of administration, siting, affirmative action and employment, and the alert says only that.
- CUT, the scout's second UNVERIFIED FRAME, “the Title VI half” of a paired effort. The notice itself states the relationship: it reopens comment on the January 2026 Fair Housing Act proposal. The alert quotes that and characterizes nothing further. The January proposal itself (91 FR 1475) was not read at source; the only sentence about it in the alert is the notice's own summary of it.
- WITHHELD, and named so the omission is visible: the racial makeup of the households in HUD-assisted housing. It would place Black tenants in this alert on a number instead of an inference. HUD User's Picture of Subsidized Households answers scripted reads with an empty HTTP 202, and a browser read was not run in this session because it needs Apollo's Chrome. Nothing in the alert says who is affected by race. The standard Title VI protects is race, color and national origin, and the alert says that and no more.
- RECEIPT GATE, 2026-09-29, independent re-fetch of every primary: all quotations and numbers PASS; five unquoted claims corrected before Apollo saw the draft. The draft said Title VI binds “whoever takes HUD's money” (part 1 excludes ultimate beneficiaries, section 1.2(f)); called these rules for “federally funded housing” (section 1.3 covers every HUD-funded program); said “the rule names one kind of recipient directly” (only section 1.4 does, and that paragraph stays); said HUD “cannot say how many of its cases rest on the standard” (HUD says it does not track which rest SOLELY on it, a narrower claim, now quoted instead); and described the affirmative-action and employment removals too narrowly. Each now reads as the source reads.
- SCHEMA FIRED, recorded: the first build failed on the closing-window rule, which matched “through 2025” in “calendar years 2023 through 2025.” That phrase is a past range of HUD's own counts (the notice reads “CY23-CY25”), not a window that closes, so it carries no expiry. The years are now written out, which is also the plainer sentence. The gate did its job on the shape it is built to catch; this entry exists so the rewording is not silent.
- POSTURE, set before drafting on Alert 08's precedent and on Apollo's ruling to come: the alert explains what the proposal removes and how to comment. It does not tell the reader what to write or which side to take, and it closes by saying so in its own text, as Alert 08 did.
Support is welcome and never required. The door is open; it is not a request.
Sources
- HUD's Implementation of the Fair Housing Act's Disparate Impact Standard; Amendments to HUD's Title VI Regulations (Supplemental notice of proposed rulemaking)
- 24 CFR 1.4, Discrimination prohibited (eCFR, point-in-time 2026-09-25)
- Executive Order 14281, Restoring Equality of Opportunity and Meritocracy
- Regulations.gov, Docket HUD-2026-0034, document HUD-2026-0034-0609 (comment page)
- HUD Proposes to Eliminate Agency’s Title VI Disparate Impact Regulations; 60-Day Public Comment Period Opens
Get Signal Forge alerts in your inbox.