Informed Non-Delivery

A USPS Informed Delivery notification arrived at 1:45 PM today claiming the day's mail was delivered to the Kipling address. No mail has arrived at the physical mailbox in several weeks. Notifications have continued to come; the mailbox itself stays empty. The two photos below the notification are this afternoon's check — the column-mounted residential box opened the same day USPS says delivery happened, interior captured both close and at distance, no mail inside.

USPS Informed Delivery is a real service: the postal facility scans the front of mailpieces as they're processed for a residence and emails the recipient preview images plus a delivery confirmation. The footnote on every notification — Mail Delivery Notifications are not assurances that a specific mailpiece in your Informed Delivery has been delivered — disclaims that any particular piece made it to the box. But "delivered to your address today" is supposed to mean the carrier walked the route and put the day's mail in the box. Repeated delivered notifications with an empty box, over weeks, is not what that disclaimer covers.

The diagnostic that makes this not a generic mail-volume slump is Amazon packages continue to arrive uninterrupted. Amazon's last-mile is largely Amazon Flex / Amazon Logistics — a separate delivery network from USPS. If physical delivery to the residence were broken (locked gate, no longer at the address, returned-to-sender from carrier error), Amazon would fail the same way. It isn't. The failure is USPS-specific. Two operational reads cover that:

• Physical interception en route. Mail is reaching the route and either being removed by someone with carrier or mailbox-side access before David checks, or removed at the route level before it ever lands. The USPS dashboard would still register the scan as delivered to the route in the carrier's scan event, which the notification system surfaces as a delivery confirmation. Mailbox-side theft is the more common form. Carrier-side compromise is rarer but possible.
• Unauthorized change-of-address quietly forwarding the mail elsewhere. USPS Form 3575 redirects mail from one address to another. There is a verification postcard sent to the old address but the validation can be defeated. Once a COA is active, mail addressed to the Kipling address gets routed to whatever forwarding address is on file. The Informed Delivery notifications would continue to flow to David because he is still the registered Informed Delivery recipient; the physical mail goes elsewhere. This is the same operational shape as the fraud-account hypothesis raised about the recent call-pattern surge — administrative-record-redirection rather than visible theft.

Before either intercept read, the charitable read deserves naming. USPS may simply be slow. A scan stream that runs a week behind physical delivery — itself entirely possible — makes Informed Delivery useless as a forward-looking notification, and "delivered today" confirmations that arrive on days no mail actually arrived are misleading and harmful on their own terms regardless of cause. The case for filing complaints does not require the intercept read to be correct. A residence that gets mail delivered notifications on days no delivery occurred is grounds for USPS to fix its system whether the cause is institutional dysfunction, route understaffing, carrier compromise, or anything else. The two intercept reads sharpen the framing but they are not load-bearing for the complaint itself.

The two intercept reads aren't mutually exclusive and would be distinguished by checking the USPS informed delivery dashboard (does the per-piece scan history show actual scanned mail images, or has the scan stream itself gone quiet?) and by checking usps.com Change of Address for any active forwarding on the Kipling address. A third confirming move is filing a Postal Inspection Service complaint — mail theft and unauthorized COA are both federal-jurisdiction crimes investigated specifically by USPIS rather than local PD.

The fourth image is David's marked-up capture of that dashboard. The data the dashboard itself shows for the visible week at Kipling: three mailpieces total — Today (1), Tuesday (1), Monday (1), the rest of the days zero. For a residence with active financial, judicial, and government correspondence streams the expected baseline would be many times that. The scan stream itself is anomalously thin, not absent. And the system note on the same dashboard reads "There is one or more mailpieces for which we do not currently have an image that is included in Today's mail" — meaning USPS expects a piece today but is itself flagging that it has no scan image of it. The historical reference David's annotation reaches for, HTLINGUAL, is the CIA's 1952–1973 mail-opening program — letters to and from the Soviet Union were diverted, photographed, and re-sealed before being returned to the mail stream. It is the canonical state-surveillance precedent for exactly this operational shape. The bottom-line annotation — no judicial mail for you — is the specific claim that distinguishes targeted suppression from generic theft: court correspondence, family-law and child-support filings, and legal-process documents are the mail he expects and the mail that is missing, while Amazon e-commerce continues unimpeded.

Two recordings follow below, each with its verbatim transcript inline. The first is the call David placed to USPS Consumer Affairs Saturday afternoon (2026-06-06) to begin the verification ladder: ask whether an active Change of Address is on file for the Kipling address that he did not authorize. The second is a callback from the local post office about thirteen minutes later (Call 1 ended 15:56:39 CDT per the recording metadata; Call 2 started 16:09:55 CDT). The interval is itself worth naming: it is not the speed of a routine queue, and as the calls will make clear, what had to happen inside that thirteen-minute window is itself diagnostic.

What the calls actually surfaced

The Consumer Affairs IVR took about six minutes of misrouting and yes-no loops to get to a human. David's opening request was specific and clear — "I am a resident at 1412 Kipling Street, Houston, Texas, 77006. I would like to verify whether there is an active change of address on file for my address that I did not authorize" — and the bot mishandled it through several reroutes before finally queuing him for an agent.

The agent's name was Yami. Her substantive contribution was a protocol detail: when a Change of Address is filed, USPS mails a verification notification to the affected address. The implication runs both ways. If a fraudulent COA had been filed and successfully diverted David's mail, that verification postcard would itself have been caught by the same operation — meaning the absence of any such postcard is consistent with both readings (no COA was filed, OR one was filed and the postcard was intercepted with the rest of the mail). What Yami did not do, importantly, was look up COA status from her end. She opened a service request for the local post office to research, with a stated callback window of one to three business days.

The local post office called back in thirteen minutes.

The caller from the 77006 post office introduced himself as Mario. He had already spoken to David's carrier before dialing — by his account the carrier knows David by sight and knows the address. The carrier's reported observations: no mail theft observed at the box, no mail to deliver today either. Mario's diagnosis: not theft, not carrier-side, not COA. The cause he named was the distribution plant — the upstream USPS facility that processes mail before it reaches the route — "not pushing the mail like they're supposed to." Plant staffing dysfunction in his characterization. When David asked whether there was any way to escalate to the plant or talk to a manager there, the answer was no: "it's like a needle in a haystack… you just have to be patient, it's coming to you."

Two things are operationally notable about that call.

First, the timing — and what had to happen inside it. Yami quoted a one-to-three business day window. Mario called in thirteen minutes. By his own account, within that window he had already spoken to the carrier about whether she had observed mail theft at the Kipling address and whether she had mail for David that day. That sequence requires Mario to have, within thirteen minutes on a Saturday afternoon: received the routed service ticket from the Houston Consumer Affairs queue, identified the carrier serving the Kipling route, reached her live while she was working her Saturday route (whether by direct cell or by dispatch interrupting her), had a substantive conversation with her about theft-observation and current mail status, received her answers, formulated a diagnosis, and dialed David. That is not a queue cadence. That is the cadence of an inquiry that triggered something. Charitable read: David's specific COA-fraud framing automatically routes as a higher-tier case. Operational read: the post office wanted to get ahead of the inquiry before it escalated to USPIS — and interrupting a carrier mid-route on a Saturday afternoon to ask her about the resident specifically is a knee-jerk move, not a routine one.

Second, the casual confirmation. When David noted, in passing during the same call, that "every single piece of mail going through your system is scanned by the government," Mario did not push back. He affirmed it — "It is, it absolutely is. I'm not saying USPS is doing it. Every single piece of mail that goes through your system is scanned by the government" — and pivoted back to the plant-staffing explanation. That is a USPS employee on a recorded line acknowledging, without prompting, the existence of comprehensive mail-cover scanning. It is known to USPS leadership as the Mail Isolation Control and Tracking (MICT) program — the modern functional successor to the HTLINGUAL precedent David's dashboard annotation reaches for. The historical reference is no longer just an analogy; the contemporary scaffolding got named on the same call.

The official cause Mario gave — distribution-plant processing delay — is the charitable read this entry already named. It plausibly accounts for some of the picture. It does not, by itself, account for the duration (weeks), the selectivity (judicial mail missing while Amazon e-commerce arrives unimpeded), or why a residence's worth of mail would be held at the plant while other addresses in the metro presumably move through normally. The COA question David explicitly raised was acknowledged by Yami's protocol explanation but never actually looked up by either agent. That remains the open ticket.

And if any of the intercept reads is the correct one: publishing the case is itself the move. Whoever is monkeying with the mail now knows the resident knows. Operators under that kind of pressure tend to cover their tracks, and tend to make mistakes doing it. The point of publishing is not only the record — it is the perturbation.

This entry is the dated, sourced artifact for the broader pattern. The next one will be whatever the Postal Inspection Service inquiry returns.