Cops Keep Getting Arrested for Using Flock to Stalk People

The pattern here is not a single rogue officer but a documented series of over a dozen cases, which shifts the liability question from individual misconduct toward vendor negligence. Flock's exposure is now a product design problem, not just a customer relations one.

The Jedify funding covered the same week illustrates the inverse of this story: enterprise AI infrastructure is attracting serious capital precisely because context-aware access controls and audit scaffolding are hard to build. Flock apparently shipped without that layer, or shipped it too thin. The Jedify thesis, that grounding and access governance are table stakes for production AI, reads as a direct diagnosis of what went wrong here. The surveillance-tech category is largely disconnected from the agent-infrastructure conversation on Modelwire so far, but these two stories together suggest a convergence point: any AI system that touches sensitive operational data will face the same governance pressure, whether it is a cop's license-plate query or an enterprise agent reading internal financials.

Watch whether Flock publishes a mandatory audit-log requirement or access-tiering update within the next two quarters. If they do not, expect a procurement freeze from at least one major municipal contract as political cover for city councils facing constituent pressure.