Heads or Tails, Statelessly — Part 3

Part 1 and Part 2 of this series covered what happened to me — the antisemitic threats, the assault, the retaliation, the chemical exposure — and how four institutions’ responses to it seem to converge on one outcome without needing to coordinate directly. This part is about a mechanism I’m living inside of right now, as I write this: a federal civil-rights document-intake process that appears built so that whatever I do with it gets used against me.

I want to name it precisely, because I think the precision is what makes it visible. This isn’t a complaint that a government office is slow or disorganized. It’s a claim that the specific shape of the requests — expanding, then narrowing, then characterizing my compliance as excessive regardless of what I produce — converts a document-intake process into something that functions differently than it’s presented.

Two goals that work together, not against each other

The request for “ALL communication” reached into my Proton account — encrypted, mine, with no clean mechanism for anyone to simply take its contents. At the same time, as Part 2 laid out, there’s an evident interest across several institutions in casting me as someone who obstructs, who’s difficult, who can’t be relied on.

These two goals aren’t in tension. They reinforce each other. One track gets material handed over voluntarily that couldn’t otherwise be reached. The other builds a record that I’m a problem. Together, they let my cooperation be used regardless of outcome, and my credibility undercut regardless of what I produce — and the claim gets closed either way.

Where the record gets built

I filed a HUD Fair Housing complaint — Inquiry No. 887655 — against my former landlord and its property manager. Here is the sequence of requests I received from the intake office, reproduced as close to verbatim as I can manage from my own records:

Over more than forty hours and roughly twenty emails, the specific request changed with nearly every submission, under short deadlines, while I was recovering from documented chemical exposure. That record — the shifting asks, the “voluminous” characterization, the 36-hour clocks I couldn’t always perfectly meet — can be read one way: look how hard he is to work with. Look how he can’t produce what’s asked. Look how he obstructs.

The pincer: there is no clean move

Cooperation gets converted into extraction, and extraction produces no protection in return. Resistance gets converted into difficulty, and difficulty gets used to discredit the complaint. Both exits feed the same outcome. I can’t step outside the trap by trying harder or by refusing, because the framework catches both directions. This is the mechanism I expect to face again if I bring a civil suit, since the Fair Housing Act preserves that right for two years after HUD’s administrative closure.

I wrote that down for myself while living through this, because I needed a fixed point to hold onto. A corollary I added: ability does not always exclude culpability, but a lack of ability cannot justify inferring culpability. Whatever I could or couldn’t manage to produce in a given week was being read as a verdict on my character. It isn’t one.

“ALL,” then not ALL — and my encrypted email

There’s a second layer to the June 10 request worth naming specifically. “ALL communication” — explicitly including all emails — reaches into my personal, end-to-end encrypted email account. That account is encrypted and mine; there’s no clean mechanism for an outside party to simply take its contents. So the sweeping demand does that work instead: if I hand everything over in the name of complying, the record obtains, voluntarily, what couldn’t otherwise be reached or compelled.

The later narrowing — we don’t need ALL, only this specific slice — doesn’t undo that. The broad demand already did its job the moment it got me reaching into that account to satisfy it. The contradiction between the two requests resolves into one of two outcomes, and both serve the same end: either I hand over material that couldn’t have been taken directly, or I’m shown to have been asked for “everything” and to have fallen short of it.

Read this way, “ALL, then never mind ALL” isn’t disorganization. It’s a mechanism — use the maximalist request to get voluntary handover of what’s otherwise out of reach, and let the built-in contradiction resolve into either the material itself, or a record that I failed to produce it.

The contrast that proves it isn’t me

Here’s the part I keep coming back to. The same facts, assembled by the same person — me — moved through the Philadelphia Fair Housing Commission without any of this friction. Staff drafted the amended complaint, sent it to me for signature, and I signed it electronically. One clean amendment, docketed, done.

If the difficulty at HUD were about my competence, or the sufficiency of my allegation, 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 no friction at all. What changed between the two experiences isn’t me. It’s the process, and the people running it. That contrast is itself evidence that the difficulty is being generated, not caused.

The Fair Housing Commission later used my own published documentation — a page from this site, submitted as a PDF — to help amend that complaint. An institution acting on a record I’d already written down, instead of asking me to reconstruct it from memory under a new deadline, is the clearest proof I have that a public record can do something a live intake process, run this way, seems built to prevent.

Why the shape matters

I want to be careful here, because this is the part where I’m offering an interpretation, not just a record. Antisemitic scapegoating doesn’t require constant antisemitic language to operate. In many cases, its defining feature is quieter: a Jewish person gradually gets recast as the source of institutional problems, rather than the person to whom those problems happened. The focus shifts from the original wrongdoing toward the character and credibility of the complainant. The subject of the inquiry quietly changes from what happened to this person to what kind of person is this.

If requests continually expand, deadlines keep shifting, and compliance gets called excessive no matter what’s produced, the administrative record starts documenting the complainant instead of the discrimination that was reported. That inversion is a recognized feature of scapegoating — it redirects attention from institutional conduct onto the individual’s supposed defects.

This is an analytical framework, not a finding. Whether it accurately describes what’s happening to me would depend 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 setting the structure out so it’s legible, in my own words, and leaving the finding to whoever reviews the record.

Why I’m publishing this instead of just living through it

A process presented as routine document intake can, in effect, extract material that couldn’t otherwise be compelled, manufacture a “difficult complainant” record, and place a complainant in a position where both compliance and resistance get turned against them in a parallel proceeding. I’m setting that structure out in full because the alternative — letting the record accumulate silently, one shifting email at a time — is exactly what makes the mechanism work in the dark.

If the outcome any of this is aiming at is a complainant who looks too difficult to be believed, then a public, dated, cross-linked record is the thing built to survive that outcome. It doesn’t depend on my memory holding up under scrutiny five different ways at once, in a future proceeding, years from now. It’s already written down.

The rest of the series

This part covers the mechanism. Parts 1 and 2 cover what happened and why it converges.