What is the control package?

A second certified packet mailed the same week to the U.S. Supreme Court, 700 miles away, which was delivered and signed for in three days — while the 35-mile packet to the Waukegan courthouse stalled in Palatine and was never delivered.

Who controls the tracking data?

USPS. The tracking records are third-party, machine-generated artifacts outside the control of either the sender or Lake County, and both are preserved in the federal exhibit chain.

The Control Package: 700 Miles in Three Days. 35 Miles, Never.

Two certified packets, same week. The one sent 700 miles to the U.S. Supreme Court arrived in three days. The one sent 35 miles to the Waukegan courthouse stalled and never arrived. USPS preserves both trails.

USPS certified mailcontrol experimentcourt access23 CF 1146

This was not an accident of the mail. It was a measurement. When the clerk’s office refused the electronic filing path on June 8, the 82-page packet went out by USPS Certified Mail on June 9 — addressed to a courthouse 35 miles away. It stalled at the Palatine distribution center and never arrived. So a control was run: a second certified packet, mailed the same week, addressed to the Supreme Court of the United States, 700 miles away. That one arrived in three days and was signed for.

Why a control matters

A single failed delivery proves little; postal systems lose mail. That is exactly why the control package exists. When the long route succeeds and the short route fails — in the same week, from the same sender, through the same system — the failure stops being ambient noise and becomes a data point demanding an explanation specific to the route that failed. The route that failed was the route to the Nineteenth Judicial Circuit.

What the tracking records fix in time

USPS tracking is a third-party, machine-generated record that neither the sender nor Lake County controls. It fixes the intake scan, every routing scan, and the terminal status of both packets. The Waukegan-bound packet’s trail ends in Palatine on June 9. The Washington packet’s trail ends with delivery and a signature. Both trails are preserved in the federal exhibit chain of N.D. Illinois No. 1:26-cv-06738.

The context that sharpens it

The stalled packet was not junk mail. It was the same substantive omnibus the clerk’s office had declined to docket electronically the day before — the filing containing the Faretta invocation, the warrant challenge, and the remote-hearing demand. Every channel it traveled — portal, counter, certified mail — terminated short of the docket in the same ten-day window. The one channel Lake County did not control, the federal ECF system, accepted the same material without incident.

The question that remains open

No agency has offered an explanation for why the short route failed while the long route succeeded. The demand on the record is narrow and answerable: produce the full USPS event data for the Waukegan-bound piece and the intake log for certified mail received by the Circuit Clerk that week. Either record would resolve the question. Neither has been produced.

Verify it yourself

Both tracking chronologies are published in this archive with page-level citations into the stamped federal record: the stalled local trail and the signed Washington delivery. Read them side by side — the comparison requires no commentary.