The Terminal That Won't Print

Four hundred volunteers across the country. Law students, paralegals, attorneys, retirees. They drive to federal courthouses, sit at public terminals, and copy out habeas corpus petitions filed on behalf of people the government is trying to deport. Roughly 29,000 documents by the most recent count, published to a site called Habeas Dockets, free to anyone. Founded by John Kyle Cronan, a software developer in Chicago with no legal background, who became a nonprofit earlier this year and now runs the most complete public index of immigration habeas filings in the United States.

Beautiful. Genuinely. Now sit with the mechanism for a second.

These are public records. Not sealed, not classified, not redacted, not subject to any exemption — public, in the plain sense that any citizen has the right to read them. And in 2026, the only reliable way to move one from a government computer to the public is to send a human being to the building.

That's not a volunteer story. That's an air gap.

i · the exploit is a distinction

Cronan hit the wall in April 2025, researching cases involving people the government wanted to send to CECOT, the maximum-security prison in El Salvador. He tried to pull the filings and got the message anyone who has poked at PACER knows: You do not have permission to view this document.

A clerk explained, helpfully and uselessly, that the records were fully public and he could read them at a courthouse kiosk. In northern Texas. He was in Chicago. Cronan's recollection of his own reaction is the whole federal access regime in four words: You've got me there.

The barrier is Federal Rule of Civil Procedure 5.2(c), a 2007 provision limiting remote electronic access to filings in immigration-related cases. Not sealing them. Limiting the remote electronic part. And Habeas Dockets is built entirely on the observation that this is a distinction with enormous consequences: 5.2(c) restricts the method of access, not the dissemination of otherwise-public information. Go to the terminal, which is legal. Read the document, which is legal. Publish what you read, which is also legal, because nothing in the rule says otherwise.

Any security engineer recognizes this immediately, because it's the oldest finding in the book. The control protects the channel, not the data. Which means the control holds exactly as long as nobody is willing to walk.

Four hundred people are willing to walk.

What Habeas Dockets built is a sneakernet — the term of art, from a generation of people who moved data past network restrictions on physical media because the wire was blocked and the shoes weren't. Nobody expected to need one for the American federal judiciary. Nobody expected to need one in 2026. But the topology is identical, down to the funding model: the organization takes donations partly to reimburse volunteers for printing costs, which is to say a nonprofit is now buying toner to route around a rule of civil procedure.

ii · the terminal that won't print

Here is the detail that turns this from a quirk into a posture.

Some district courts allow you to view the records at the public terminal but will not let you print them, save them to a file, or copy them to a thumb drive. Habeas Dockets got that policy reversed in the Western District of Pennsylvania. It reportedly persists in four other districts.

Read that again slowly. A federal court is running DRM on a public record — not the cryptographic kind that travels with the file, the cheap kind, where somebody switches off the file operations at the endpoint and calls it a control. You may look. You may not have a copy. The document you have a legal right to read exists, on a screen, in a building you are legally entitled to stand in, and the print button is gone.

And notice where that came from. Rule 5.2(c) doesn't say that. Nothing in the Federal Rules directs a district to disable printing at the kiosk. Somebody local looked at the terminal, understood that print was the gap between "restricted access" and "public copy," and closed it. That's not policy. That's a countermeasure — an operational response to an observed workaround, generated at the floor level, without any rule change or public comment or anyone above having to sign it.

Which tells you the thing the heartwarming version leaves out: the sneakernet is being contested. Quietly, unevenly, by five district clerks' offices, one of which has now backed down. Nobody announced a position. Nobody had to.

iii · what went dark was the aggregate

It matters enormously which records these are, and the coverage keeps filing them as court documents with an immigration flavor.

Habeas corpus is the specific instrument by which a person contests whether the government has lawful custody of their body. It is not one procedural device among many. It is the one the Constitution names, the one whose suspension is treated as a constitutional emergency, and the reason it exists is that a government holding someone can be made to say, in public, on what authority.

Now count what 5.2(c) actually removes. It does not stop a petitioner from seeing her own case; parties and their lawyers keep remote access. It does not stop a reporter from reading any single filing, provided the reporter is standing in the right building during business hours. What it removes is the ability to see all of them at once — how many petitions, on what grounds, granted at what rate, in which districts, against which arguments the government is making in its own name across thousands of cases.

That is the entire oversight value. A habeas petition read one at a time is a person's misfortune. Fifty thousand of them, sorted, is a finding about whether the writ is functioning. The rule leaves the first intact and destroys the second, and it does that without ever withholding a document from anyone who asks correctly.

Which is the precise shape of a commons that has been technically preserved and functionally enclosed. A commons is not defined by whether individuals may access it one at a time — a library that lends you any book but forbids a catalogue is not a library. It is defined by whether the whole is visible to the whole. The state kept the letter of publicness here and disposed of its only useful property.

And it reframes the four holdout districts. Those aren't fussy clerks protecting a workflow. Disabling the print button is, functionally, suppressing the aggregate — because the aggregate is the only thing that requires copies. You do not need to print anything to read one case. You need to print everything to count.

The volunteers, meanwhile, are not liberating documents. They are reconstructing by hand, on donated labor, the oversight statistic that a functioning judiciary would publish as a dashboard.

iv · nobody decided this

The conspiratorial reading is right there and I want to be honest about why I'm not taking it.

You could say the state calculated that these records should be hard to get, and designed accordingly, and that the volunteers are fighting a deliberate opacity. Maybe in the four holdout districts something like that is true at a small scale. But as an account of 5.2(c), it doesn't survive contact with the timeline.

The rule is from 2007. It was written into a privacy context — a period when the live fear about court records was identity theft and bulk scraping of dockets containing the personal details of people with genuinely dangerous adversaries. Immigration filings contain exactly that: names, addresses, family members, the specific persecution someone fled. Restricting remote access was a coarse instrument applied to a real problem, at a volume where "you can see it at the courthouse" was a friction rather than a wall. A trickle of cases, mostly researched by people already in the building.

Then the volume changed. Nearly 50,000 habeas petitions in the recent enforcement surge. The rule didn't change. It simply kept executing against an input it was never sized for, and a friction became an opacity by arithmetic.

That is worse than the conspiracy, not better. A conspiracy has somebody to fire. This has a rule from 2007 doing precisely what it says, producing an outcome nobody chose. The system is not lying about what it does. It is doing what it does, at a scale where what it does means the opposite of what it meant.

v · the machinery exists and it is slow

I nearly wrote that there was no office responsible for noticing. That would have been the satisfying line and it would have been false, and the correction is more damning than the error.

There is an office, with an address. The Federal Rules of Civil Procedure belong to the Judicial Conference's rules committees — the Advisory Committee on Civil Rules and, above it, the Committee on Rules of Practice and Procedure. They amend the rules on a published cycle. They take suggestions from anyone. Every proposed amendment goes out for public comment specifically so that a rule producing bad outcomes can be surfaced by the people it is producing them for. The mechanism was built for exactly this.

And on May 20, 2026, somebody finally used it. The Reporters Committee for Freedom of the Press wrote to the Committee on Rules of Practice and Procedure asking it to strike the immigration language from Rule 5.2(c) outright — docketed as Rules Suggestion 26-CV-20. The letter names the problem precisely: that in practice, the public may view "critical records such as a noncitizen detainee's habeas petition, and dispositive briefing litigating a noncitizen's constitutional rights" only by appearing at the courthouse during the clerk's business hours. It notes that the restriction prevents timely access to fast-moving proceedings, and that it burdens the clerks themselves with requests for paper copies.

So: nineteen years, a detention surge, roughly 50,000 petitions, four hundred volunteers, and an unprompted nonprofit sneakernet, before the mechanism designed to catch this got a letter about it.

That's the finding. Not that accountability had nowhere to live — that it had a documented address, a published calendar, and an open inbox, and stayed idle anyway, because nothing in the machinery notices a rule going wrong. The machinery waits to be told. Its budget for noticing is zero, and it always was; the noticing is outsourced, by design, to whoever is harmed enough to write a letter.

vi · what i can't tell you

The numbers in this story don't reconcile cleanly, and I'd rather say so than pick the flattering one.

Roughly 29,000 documents uploaded is the figure attached to the current reporting. The organization's own accounting earlier this year described over 30,000 cases tracked and over 12,000 case documents made available as of March 2026. Those are probably different measurements — cases tracked versus documents published, uploads versus items live after review — and the growth rate implied is plausible either way. But I don't know which count means what, and neither does anyone reading a summary of a summary. Against nearly 50,000 petitions, the coverage is substantial and incomplete, and how incomplete depends on which number you trust.

I also can't tell you whether 26-CV-20 goes anywhere. As of this writing it is a docketed suggestion and nothing more. Even on the fast path it would have to clear the advisory committee, get published for public comment, survive the Standing Committee, be adopted by the Judicial Conference, be transmitted by the Supreme Court, and sit out a congressional review window. That process is measured in years, and it is measured in years for good reasons that are no comfort whatsoever to somebody detained this week.

And I can't tell you whether the four holdout districts will hold. One already didn't.

vii · the amateurs built the better privacy model

The part that should embarrass someone.

Cronan's team reviews filings before publication and redacts sensitive material — details about trafficking, domestic violence, specific fears of persecution. They are under no legal obligation to do this. The documents are public; having lawfully obtained them, they could post the raw scans. They don't. Advocates like the Tahirih Justice Center have pressed exactly this concern, that abusers and traffickers can exploit easily accessible personal details, and the volunteers built the review step in response.

So compare the two privacy implementations.

The federal judiciary's: a blanket flag on remote access for an entire category of case. Binary, indiscriminate, applied without reading anything. It withholds the petitioner's address and the government's legal argument with equal force, because it cannot tell them apart — it isn't looking at the document, it's looking at the case type.

Habeas Dockets': a human being reads each filing and removes the parts that could get somebody hurt, leaving the parts that let the public see what the government is arguing in its own name.

One of those is a permission bit. The other is redaction. Redaction is what you do when you want privacy and accountability; a permission bit is what you do when you have to pick one and don't want to spend the labor. A software developer with no legal training and a network of volunteers implemented the finer-grained model, on donations, because the coarse one was in the way.

It is also, incidentally, the amendment the Reporters Committee is asking for. The fix has already been prototyped in the field, at volume, by amateurs, and the prototype works. What's missing is not a design. It's a decision, on a calendar that moves in years.

So the prediction is easy and I take no pleasure in it.

When Habeas Dockets gets large enough to be inconvenient — when a filing it surfaced shows up in a hearing, or a reporter builds a real story on the bulk corpus — the response will not be an open docket. It will be more districts turning off the print button. That's the cheap move, it requires no rulemaking, it's already been piloted in five places, and the argument for it writes itself in the language of protecting vulnerable petitioners, which is not even a lie.

A clerk can disable printing on a Tuesday afternoon. Amending Rule 5.2(c) takes three years and a Supreme Court transmittal. Those two facts are the whole story, and they are not in a fair fight.

The volunteers will keep driving. That's the part that holds. Four hundred people have already demonstrated they'll spend an afternoon in a federal building copying documents that a working government would have served over HTTPS two decades ago, and the demonstration doesn't expire.

It just doesn't scale as well as a checkbox.