The line between passive infrastructure and active surveillance is dissolving faster than most people realize — and it’s happening in our own neighborhoods, under the banner of routine traffic enforcement.
By trade, I spend my days inside data systems: parameters, automation, targeting logic. So when I see those same architectures deployed in public space under the guise of simple traffic enforcement, I look at the underlying design a little more closely than most. Automated License Plate Readers (ALPRs) are a good example of a system that’s been badly undersold to the public it monitors.
The pitch is simple: a camera reads a plate, cross-references a database, flags a stolen vehicle. In practice, these are not narrow tools. They’re 24/7 recording networks that log the movement of every vehicle, pedestrian, pet, and object that passes in front of them — whether or not anyone involved has done anything wrong.
There’s a meaningful difference between targeted enforcement and ambient surveillance. A red-light camera or a speed sensor is triggered by a specific, defined violation. That’s a reasonable trade-off most people accept. Continuous, unprovoked recording of an entire area is a different category of thing entirely — and it shows in where some of these cameras end up pointed: neighborhood playgrounds, quiet residential streets, stretches of river where no vehicle could ever travel. At that point, the tool has stopped enforcing a rule and started building a permanent record of everyone’s movement, just in case.
The human cost isn’t hypothetical. In one case that drew local news coverage, a driver was detained at gunpoint after automated software misread his plate and flagged his car as stolen — despite the fact that he’d done nothing wrong. Facing consequences for breaking a law is one thing. Facing an armed response over an unverified software match is a different order of problem, and it’s one we’ve built for ourselves by trusting these systems more than the evidence supports.
It’s also worth asking why our default response leans so heavily on overwhelming force in the first place. Peers in other countries are routinely surprised by the intensity of American vehicle stops and pursuits, particularly when a plate is already logged in a database and the situation could be handled with far less urgency. In the large majority of these cases, sending an armed response to intercept someone over an unconfirmed data match is a mismatch between the risk and the reaction.
Interestingly, some of the proposed “next steps” for this technology may actually point toward something better. Vendors have begun pairing stationary ALPR networks with autonomous drones that respond to camera alerts by verifying the situation visually before any officer is dispatched. That’s a meaningful improvement over dispatching an armed unit off an unverified alert — even though it simultaneously expands the footprint of the surveillance system itself. It’s a trade worth naming honestly: better verification, more infrastructure.
This is exactly the kind of decision that shouldn’t be made quietly at the vendor-contract level and left there. These are civic questions — about what data our public infrastructure collects, who has access to it, how long it’s retained, and what triggers should exist before force is used. They deserve the same scrutiny we’d apply to any other system with this much power over ordinary people’s lives.
If we want better-designed systems in our communities, someone has to be willing to ask the unglamorous questions about how they actually work — not just whether they sound reassuring in a press release. That’s the conversation I’d like to keep having, in public, with anyone willing to look at the details with me.
Trevor Durgin 
Leave a comment