Compliance is a Moving Target: What 9.5 Years in Brokerage Operations Taught Me About Fair Housing
Federal Fair Housing is contracting. Cities are expanding. The PDFs go stale in eight weeks. Here's why I stopped writing static compliance documents and started building a live layer.
A few years ago I was sitting across from an Associate Broker in Santa Fe when she asked a question that should have had a clean, fast answer.
"My seller just told me they don't want to sell to a family with young kids — they're worried about wear and tear on the house. What do I tell them?"
I had been in operations for years at that point. I quickly prepared to brief my Qualifying Broker on the situation and gather resources for both the Qualifying Broker and the Associate Broker to reference together. I knew the headline: No. The seller cannot direct that screening, and the Associate Broker cannot relay it. Familial status is a protected class under the Fair Housing Act.
But I also knew the real answer wasn't that simple. One wrong word could trigger a HUD complaint, a state civil rights filing, five-figure penalties, and the kind of reputational damage that takes a decade to rebuild.
So I did what I always did when the stakes were high: I pulled the layers. Federal Fair Housing Act on familial status. New Mexico Human Rights Act. A Santa Fe County provision I'd never read before. The City of Santa Fe's enforcement framework. Twenty minutes later I had the full picture — federal exposure, state penalties, local rules — ready for both the Qualifying Broker and the Associate Broker to review together, including the exact language to use with the seller.
By the time I looked up, she was already gone to her next showing.
That moment never left me. Because every operator in housing — landlords, property managers, brokers, and lenders — runs into a version of it. And almost nobody has a reference that's actually built for the question.
So three weeks ago, I started building one.
The federal floor is moving
Most people who deal with fair housing assume the federal layer is stable. The Fair Housing Act of 1968. Seven protected classes. HUD enforces it. End of story.
That assumption is now wrong.
In 2025 and into 2026, the federal compliance picture has shifted in a series of moves that haven't gotten enough attention outside of policy circles:
- Executive Order 14281 (April 2025) changed how federal agencies enforce disparate-impact theory.
- HUD's FHEO memos in September 2025 rolled back guidance on protected-class interpretation that fair housing practitioners had relied on for years.
- The Turner letter (November 25, 2025) narrowed HUD's posture on criminal screening — undoing a framework that took the better part of a decade to build.
- The DOJ's Title VI guidance rescission (December 2025) removed federally enforceable interpretations that fed directly into housing discrimination cases.
- The AFFH revision (March 2025) gutted the affirmative obligation that local jurisdictions accepting HUD funds had been operating under.
If you compliance-trained your staff in 2023, half the materials you trained them on are now obsolete or contested.
That alone should be the lead story of every real estate operations conference happening this year. It isn't.
Cities are doing the opposite
While the federal layer contracts, cities and counties have been expanding protections at a rate the casual observer would not believe.
A few I keep coming back to:
- Albuquerque added source of income, ancestry, and additional anti-discrimination provisions to its city code (§§ 11-2-1 et seq.).
- Bernalillo County went further — Ordinance No. 2017-13 covers source of income, sexual orientation, gender identity, and gender expression, including in the unincorporated parts of the county that city ordinances don't reach.
- Santa Fe added immigration status to its protected categories. Yes — immigration status. As a fair housing protected class. (Santa Fe Code §§ 28-1.)
- Las Cruces added source of income.
- Los Alamos County, Santa Fe County, and Taos — all expanding past the federal seven.
That's just New Mexico.
Pull up Pennsylvania and you'll find 79+ municipalities with additional protections. Ohio has 33+. Florida has expanded protections in 35+ jurisdictions, including Broward County, Miami-Dade, and Coral Gables. North Carolina cities have been adopting new ordinances on a near-monthly cadence since the 2020 sunset of HB 142.
Source-of-income protection alone — the single fastest-expanding protected class at the local level — now exists in over 100 jurisdictions across 26 states. Michigan added it statewide in December 2024. Delaware extended its existing SOI protection to voucher holders effective January 1, 2026. Guam signed a new SOI law in February 2026 that takes effect this October.
Add it up: 50 states, the District of Columbia, and 250+ municipalities now have fair housing protections beyond the federal seven. Some directly conflict with state preemption laws (Texas, Tennessee, Arkansas, Iowa, Kentucky, Missouri). Some go quietly into effect with no press release. All of them apply to operators in those jurisdictions whether they know about them or not.
The compliance question is no longer "what does federal law say." It's "what does this layer say in this specific zip code on this specific day, given preemption, ordinance scope, and effective dates."
That's a question no Associate Broker should be answering between showings. And it's a question no static document can keep up with.
What I built first — and why it wasn't enough
The reference came out clean.
Fifty-three pages. Four hundred thirty-one municipalities indexed. Federal foundation, fifty state-by-state breakdowns, the full municipal addendum, enforcement pathways, penalty schedules ($16,512 for a first violation, $123,837 for a third within seven years — periodically adjusted for inflation), glossaries, citations.
I wrote it for three audiences in parallel — plain-language summaries for first-time landlords, professional-tier explanations for property managers and brokers, and technical detail for compliance officers. Every protected class. Every preemption flag. Every notable city ordinance I could verify against primary sources.
It looked the way I wanted it to look. Branded, structured, useful.
And the moment I exported the final PDF, I knew it had a shelf life of about eight weeks.
A PDF is a snapshot. Compliance is a moving target. The two were never going to coexist.
While I was finalizing the document, Holly Springs, North Carolina adopted a new non-discrimination ordinance. Northampton County, Pennsylvania expanded source-of-income coverage. The HUD-issued civil penalty maximums got adjusted again for inflation. A handful of state legislative sessions moved bills from committee to the floor.
That's the structural problem with static compliance documents. They go stale on a faster timeline than anyone wants to admit. The good ones get printed, distributed, and quietly become wrong six months later. The bad ones never get updated at all.
So I stopped writing one. Kind of.
Then I made it stop being a PDF
Here's what happened next, and it's the actual point of this post.
The full 53-page reference is now ingested into XolvedAI, powered by xAI's Collections, making it a live, queryable knowledge base powered by Grok-4. Every protected class, every state statute citation, every municipal ordinance, every preemption flag — searchable in real time through the platform's chat interface.
You can ask it questions like:
"My seller wants to exclude families with young children from showings. What's my exposure under federal, New Mexico, and Santa Fe County law, and how do I document my refusal to comply?"
"Does Santa Fe protect immigration status, and does that apply to my application screening?"
"What's the difference between Texas SB 267 preemption and how Austin's local fair housing ordinance still operates?"
"My tenant filed a complaint with the Pennsylvania Human Relations Commission. What's the statute of limitations and what's my exposure?"
It answers in plain English, with citations and the appropriate caveats — and it stays current as I update the source material. When Holly Springs's ordinance gets logged, the platform incorporates it on the next ingestion cycle. When the federal civil-penalty schedule adjusts, the platform learns it. When a state preemption law sunsets or a city council votes, the answer changes. The document on your hard drive doesn't.
That's the move. The reference becomes the floor. The platform becomes the live layer on top.
I'm building it at xolvedai.com.
Why this matters beyond Fair Housing
One reference is one reference. But the pattern matters more than the document does.
Most professional services — real estate, healthcare administration, immigration, accounting, education compliance — sit on top of regulatory frameworks that are too complex for any single person to hold in their head, change too frequently for any printed reference to keep up, and carry penalties severe enough that getting the answer wrong has real financial and reputational consequences.
The traditional response has been: hire a compliance officer, hire outside counsel, buy a quarterly subscription to a print updates service, and hope the staff training holds. That stack worked when regulations changed yearly. It does not work when they change weekly across 50 states and several hundred municipalities.
What I'm building at XolvedAI is the operational layer for professionals who can't afford to staff a compliance department but can't afford to be wrong either. The fair housing reference is the first proof point in housing. There are versions of this for every regulated profession — and that's exactly the work happening behind the platform right now.
I think of it as cerrando brechas — closing gaps. The reason I know exactly where the brokerage workflow breaks down is because I sat behind every role, beginning at the front desk, and ending at Director of Operations. The reason I know what an under-resourced compliance team needs is because I was the under-resourced compliance team. The platform is built around the gaps — not in spite of them.
That's not a marketing line. That's the build order.
What you can do with this
Three things, depending on who you are.
If you're a landlord, broker, Associate Broker, or property manager — get the reference. Use it as a baseline. Then take it further by asking the platform questions about your specific jurisdiction in real time. Both live at xolvedai.com.
If you're a strategist, executive, or independent professional looking to do this for your own domain — the same architecture that makes the fair housing reference work in real time can be built around almost any compliance-heavy field. That's the work I do at Consulting x Darell Anthony.
The compliance gap isn't going to close on its own. The cities are doing their part. The federal layer is doing the opposite. The PDFs are out of date six weeks after they ship.
Build for the live layer now. Or enjoy explaining to your E&O carrier why your 2023 training deck just became exhibit A.
Darell Anthony is the founder of XolvedAI — an adaptive AI learning, marketing intelligence, and brokerage operations platform based in Santa Fe, NM. He also operates Consulting x Darell Anthony, providing strategic AI consulting to independent professionals and legacy businesses. xolvedai.com