Police abuse Flock camera search logs with no meaningful oversight

The real story isn't that cops searched cameras for bad reasons. It's that Flock's logging infrastructure created a paper trail at all, and that trail shows zero operational consequence for abuse. This suggests the vendor designed for compliance theater rather than actual deterrence.

This connects directly to Microsoft's governance framework from earlier today, which explicitly prioritizes human oversight and safety constraints as a competitive differentiator. Microsoft's bet is that enterprises will pay for transparent, auditable systems. Flock's audit reveals the inverse: when oversight exists but carries no friction or penalty, it becomes decorative. The two stories expose a market failure: vendors can claim safety architecture while deploying systems where the safeguards don't actually constrain behavior. If Microsoft's framework is genuine (not marketing), it should include mechanisms that make frivolous queries costly or visible to decision-makers. Watch whether Flock responds by adding friction to search justification (requiring supervisor sign-off, public logging, or query-level retention limits) or by arguing the audit was an outlier.

If Flock announces new search authorization controls or query logging transparency within 60 days, that signals the EFF audit created market pressure. If they don't, and law enforcement adoption continues unchanged, that confirms oversight mechanisms alone don't constrain vendor behavior without external enforcement (regulation or customer defection).