How a federal intake process built to protect you can be built, instead, so that neither cooperating nor resisting ever counts in your favor.
Part 1 and Part 2 of this series covered what happened — the threats, the assault, the retaliation, the chemical exposure — and how four institutions’ responses to it keep converging on one outcome without any apparent need to coordinate. This piece is about something I’m inside of as I write it: a federal civil-rights document-intake process that seems engineered so that whatever I do with it gets turned against me.
I want to name this mechanism precisely, because precision is what makes it visible in the first place. This isn’t a complaint that a government office is slow, understaffed, or disorganized. It’s a claim that the specific shape of the requests — expanding, then narrowing, then labeling my full compliance excessive regardless of what I actually produce — quietly converts an ordinary document-intake process into something functioning very differently from how it’s presented.
In the parallel criminal matter — Commonwealth v. Talley, the case charging my assailant with aggravated assault, ethnic intimidation, simple assault, and reckless endangerment — the District Attorney’s office needs me as a witness. At the same time, as Part 2 documented, there’s a clear institutional interest in painting me as someone who obstructs, who’s difficult, who can’t be trusted.
These aren’t competing goals. They reinforce each other. One track keeps pulling me in as a witness they can use. The other quietly builds a record that I’m a problem. Together, the two let me be used exactly when useful and discredited exactly when inconvenient — and the HUD intake process is where that second record actually gets constructed.
I filed a HUD Fair Housing complaint — Inquiry No. 887655 — against my former landlord and its property manager. Below is the sequence of requests I received from the intake office, reproduced as closely to verbatim as my own records allow:
June 10, 2026. The office asks for “ALL communication to/from the Respondents, its agents and or assignees, including but not limited to ALL: lease agreements and addendums, forms, applications, complaints, notices, correspondence, letters, notices, emails, text messages, etc.” I hand over the full requested set of communications and supporting documents.
June 30, 2026, morning. The request narrows sharply: forward only the actual emails and texts reporting the antisemitic threats, nothing else. I send the messages with full dates and times, along with a screen recording of the entire thread so the content would be easy to review at a glance.
June 30, 2026, later the same day. The identical demand comes back — “PLEASE DO NOT FORWARD ANY OTHER INFORMATION/DOCUMENTATION AT THIS TIME OTHER THAN THE ACTUAL EMAILS AND TEXT MESSAGES…” — with my earlier, fuller submission now characterized as excessive. I resend the actual messages and note, again, that the screen recording had already been provided.
July 1, 2026. A new requirement appears: a typewritten statement — date, time, location, name and title of who I spoke with, exact format, what was said — for every in-person meeting where I reported the threats, on top of resubmitting the messages once more. I provide it that same day.
Over more than forty hours and roughly twenty emails, the request changed almost every time I responded, always under a short deadline. I was recovering from documented chemical exposure the entire time. What’s left behind — the shifting asks, the “voluminous” label, the 36-hour windows I couldn’t always hit exactly — reads, if you squint, one particular way: look how hard he is to work with. Look how he can’t produce what’s asked. Look how he obstructs.
Here’s the mechanism, in plain terms.
Comply fully — put in the hours, produce everything, clear each new hoop the moment it appears — and that becomes proof that I’m capable: capable of participating, of producing, of functioning under sustained pressure. Which means, by that logic, there’s no reason I can’t take the stand and testify, whatever the chemical exposure has actually done to my memory or my health.
Push back instead — challenge the shifting requests, decline to redo hours of work for a demand that’s already changed twice, name the moving goalposts out loud — and that becomes proof that I’m difficult: obstructive, uncooperative, not someone to be trusted.
Cooperation gets translated into capability, and capability gets used to obligate me as a witness. Resistance gets translated into difficulty, and difficulty gets used to discredit me. Either way, the same narrative gets fed. There’s no way to step outside the trap by trying harder or by refusing outright, because the structure catches both directions — a coin that never gets to land, held instead in whatever state is useful to whoever’s reading it that particular week.
While I was living through this, I wrote down a phrase for myself, because I needed something fixed to hold onto: Facultas non est culpa — ability, on its own, is not culpability. A corollary I added later: ability doesn’t always rule out culpability, but the absence of ability can never be used to infer it. Whatever I did or didn’t manage to produce in a given week was being quietly read as a verdict on my character. It was never that.
There’s a second layer to the June 10 request worth calling out on its own. “ALL communication” — explicitly including every email — reaches directly into my personal, end-to-end encrypted email account. That account is encrypted and mine; there’s no clean way for an outside party to simply take its contents. The sweeping request does that work instead: if I hand everything over in the name of compliance, the office obtains, voluntarily, something it couldn’t otherwise reach or compel.
The later narrowing — we don’t actually need ALL, just this specific slice — doesn’t undo any of that. The broad demand had already done its job the moment it got me reaching into that account to satisfy it. Whatever happens next resolves into one of two outcomes, and both serve the same purpose: either I’ve handed over material that couldn’t have been obtained directly, or I’ve been shown to have fallen short of an “everything” standard nobody could actually meet.
Read that way, “ALL, then never mind ALL” isn’t sloppiness. It’s a mechanism: use the maximalist request to obtain a voluntary handover of material otherwise out of reach, then let the built-in contradiction resolve into either the material itself or a documented record of failure to produce it.
Here’s what I keep coming back to. The exact same facts, compiled by the exact same person — me — moved through the Philadelphia Fair Housing Commission without any of this friction whatsoever. Staff there drafted the amended complaint themselves, sent it to me for signature, and I signed electronically. One clean amendment. Docketed. Done.
If the difficulty at HUD were actually about my competence, or about whether my allegations were sufficient, it should have shown up at the local agency too. It didn’t. I cleared intake at a housing agency working from overlapping facts, with zero friction. What changed between the two experiences wasn’t me — it was the process, and the people administering it. That contrast is itself evidence that the difficulty is being manufactured rather than caused.
The Fair Housing Commission later used my own already-published documentation — a page from this exact site, submitted as a PDF — to help amend that complaint. An institution acting on a record I’d already written down, instead of demanding I reconstruct it from memory under a fresh deadline, is the clearest evidence I have that a public record can do something a live intake process, run this way, seems designed to prevent.
I want to be careful here, because this is where I’m offering interpretation rather than simple record-keeping. Antisemitic scapegoating doesn’t require overt antisemitic language to operate. Its defining feature, more often, is quieter: a Jewish person gradually gets recast as the source of institutional problems, rather than the person those problems happened to. Attention drifts from the original wrongdoing toward the complainant’s own character and credibility. The question underneath the inquiry silently shifts from what happened to this person to what kind of person is this.
When requests keep expanding, deadlines keep moving, and full compliance keeps getting labeled excessive no matter what’s actually produced, the administrative record starts documenting the complainant instead of the discrimination that was reported. That inversion is a recognized hallmark of scapegoating — it redirects scrutiny away from institutional conduct and onto the individual’s supposed flaws.
I’ll restate the maxim I wrote for myself while living through this: ability doesn’t always rule out culpability, but the absence of ability can never justify inferring it. This is an analytical framework, not a finding of fact. Whether it accurately describes what’s happening to me depends on evidence I don’t fully have yet — disparate treatment compared to similarly situated non-Jewish complainants, direct statements reflecting bias, and more. I’m laying out the structure so it’s legible in my own words, and leaving the conclusion to whoever reviews the record.
A process presented as routine document intake can, in practice, extract material that couldn’t otherwise be compelled, build a “difficult complainant” record out of nothing, and place someone in a position where both compliance and resistance get used against them in a completely separate proceeding. I’m laying that structure out in full because the alternative — letting the record accumulate quietly, one shifting email at a time — is exactly what allows the mechanism to keep working unseen.
If the outcome all of this is aimed at is a witness who becomes unreliable and a complainant who looks difficult, then a public, dated, cross-linked record is precisely the thing built to outlast that outcome. It doesn’t depend on my memory holding together under five different lines of cross-examination at once. It’s already written down.
Consider this an artifact of knowns and unknowns. The real question was never heads or tails — it’s what stays stateless between the two. One face reveals nothing. The other reveals everything. What can honestly be said about a coin held in superposition, correct on both faces, until someone with the power to decide forces the collapse? Facultas. Ability. That was always the only thing either face was meant to measure. Never guilt.
The full documented version of this piece — every request in its own words, the underlying source documents, and the four-institution pattern this series is built on — is archived at jlegal.pro/heads-or-tails-part-3.html. This is part of a three-part series; start at the hub page, jlegal.pro/heads-or-tails.html. This is a personal account, not legal advice. I am not an attorney.
↑ ↓