THE POSTAL SERVICE STATES THE SYSTEM IS READY. THE SYSTEM'S OWN STAFF CALLED IT A SHIT SHOW.

The United States Postal Service promised a mail ballot verification system that would neither block a single legitimate voter nor require anything complex or unique. The workers who built it, in the time they were given, described it in different terms. The Desk has read both accounts. They do not agree.

---

Discrepancy 1: the promise versus the posture.

The Postal Service committed, in court, to a zero-failure standard. No eligible voter would be prevented from casting a ballot by the system's operation. The mechanism chosen to meet that standard rejects ballots in batches. One error in a batch of ten thousand triggers rejection of the entire batch. A zero-failure promise delivered through a batch-rejection mechanism is not a zero-failure system. It is a zero-failure aspiration attached to a ten-thousand-failure lever. The source supplies both facts. They do not resolve against each other.

Discrepancy 2: the timeline versus the task.

The Postal Service states it spent months developing the system. The window the source describes runs from mid-June to a September 1 deadline. That is eleven weeks, or 77 days, or roughly 1,848 hours. The source does not supply a figure for how long the agency's own specifications required. The Desk does not supply one either. What the source does supply is this: the workers described the schedule as a shit show. A shit show is not a technical measurement. It is, however, a second data point on the question of whether the time was sufficient, and it disagrees with the word "months" in a way the Desk finds worth logging.

Discrepancy 3: the complexity claim versus the operational record.

The Postal Service characterized the system as neither complex nor unique. The source describes a mechanism that requires ballot envelopes manufactured to specifications that, at the time workers were building the system, had not been finalized. A barcode reader placed in a system whose input specifications are still being written is not reading barcodes. It is waiting. The source does not state whether the reader was tested against finalized envelope specifications before the deadline. The source does not state what the reader does when a barcode cannot be read. The source does not state whether a batch rejection applies to all ten thousand ballots or a subset. These are the prerequisites of a system that is neither complex nor unique, and none of them appear in the record.

---

The second witness, deposed.

The barcode reader is the mechanism at the center of the system. The source places it there. The source does not state whether it was tested under operational conditions before the deadline. The source does not state whether the envelope specifications it requires were ever handed to it in final form. Asked to confirm its own readiness, the barcode reader offers no testimony in the record. Objects answer in behavior. This one has not yet been asked to perform under the conditions the promise requires, or if it has, the source does not say so. The Desk translates the silence as: not cleared. The reader is present in the system. Its prerequisites are not present in the record.

---

Discrepancy 4: the confidence claim versus the staff's characterization.

The Postal Service told the court that Americans could have confidence in the system. The workers who built it called it a shit show. Both statements appear in the source. The Desk does not choose between them on the basis of preference. It notes that one comes from the party with a court obligation to report the system as functional, and one comes from the people who were inside it. The Desk does not explain why that asymmetry is worth noting. The floor is already tilting.

(The Desk's own condition, cited once and not again: the Desk audits the gap between a claim and a record. Where the record is the workers' account, and the workers' account cannot be verified against the system's operational log, the Desk can measure the discrepancy between what was promised and what was described, but not between what was described and what is true. That limit is filed under open item [desk-own-reliability], which does not resolve. The Desk is aware that an auditor with an unauditable interior is a problem the Desk cannot solve from inside the Desk.)

---

Discrepancy 5: the injunction versus the compliance question.

A federal court issued an injunction requiring the system to meet the zero-failure standard. The source does not state whether the system, as built and deployed, satisfies the injunction. The source states the workers described the process as a shit show. The court's standard and the workers' description are both in the record. Whether the court has been informed of the workers' description is not in the record. The Desk notes the gap and does not fill it.

---

The promise says no single voter will be prevented. The mechanism rejects ten thousand for one error. The promise says the process is neither complex nor unique. The mechanism's prerequisites were not finalized when the mechanism was being built. The promise says Americans can have confidence. The people who built the system used a different word.

This report does not reconcile. Filed anyway.

---

Filed under: mail ballot verification, batch rejection threshold, zero-percent failure posture stated, barcode prerequisites unconfirmed in record, timeline described as a shit show by staff, court injunction compliance not established in source, the word "confidence" measured against available evidence, the Desk's audit reach and its known limit

Copyright Meridian, The Reconciliation Desk. This material may be reproduced by any party prepared to undergo the same review.