You Can Watch the Count. You Can't Read the Code That Runs It.

COMELEC has reopened its search for a vendor to run the automated count in 2028, and the young volunteers who spent the last cycle staring at machine receipts want a different kind of access this time. They can stand inside the precinct. They can photograph the printed tally. What they cannot do is read the code that decides what the machine prints, or trace where the votes travel after they leave the room.

That gap is the whole problem. Election watchdogs and campus poll-watching networks have asked for years for meaningful source-code review, and each cycle the review that happens is narrow, late, and closed to the citizen groups who actually staff the precincts. You get to trust the box. You don't get to verify it.

The audit trail exists. You just can't touch it

Automated systems keep logs of every action a machine takes, and those logs are the closest thing to a paper conscience the process has. Advocacy organizations have repeatedly pushed for independent access to that audit trail, and the answer keeps landing somewhere between "proprietary" and "after the fact." A trail nobody outside the vendor can inspect in real time is a trail that settles arguments only for the people who already control it.

The same logic covers the random manual audit, the hand recount of a sample of precincts meant to check the machines against reality. When the sample is small, drawn slowly, and reported after results are already declared, it functions as reassurance rather than a real test.

Where the votes go after the precinct

The part that gets least attention is transmission. Once a machine finishes counting, it sends results up the chain through servers, and questions about where those servers sit, who administers them, and whether any leg of the transmission runs through foreign-hosted infrastructure have never gotten a clean public answer. For a generation raised on data-privacy fine print, "trust the hosting arrangement" is not a sentence that lands.

This is not paranoia about a rigged machine. It is a plain accounting question. If a citizen group cannot name the server, review the code, and inspect the log without a court order and a waiting period, then the transparency on offer is the printed receipt and nothing behind it.

Vendor selection is the moment to fix that, because the contract sets the terms. What the vendor is required to disclose, what review the public gets, and where the servers physically live are decisions made in the procurement documents, not on election day.

Young poll watchers are not asking to run the count. They are asking to check it, on their own time, with their own eyes, against a record they can actually open. The 2028 contract can require published source code, an audit trail that citizen groups can inspect, and a transmission map that names every server on the route. Or it can seal all three again, hand out a printed receipt, and call that verification.