The Argument
Sanctuary/welcoming-city resolutions govern what officers do; vendor contracts govern what the city’s systems do. When those two documents are written by different people for different purposes, the systems don’t know what the resolution intended. Atlanta’s Flock Safety audit is the evidence: 15 immigration-tagged searches in a four-day March 2025 window (15 named searches + 3,383 unnamed immigration-keyword searches by external agencies against APD cameras), all while APD publicly stated it had not assisted federal immigration enforcement in 2025. The resolution was real. So were the searches.
Structure
- The Glitch — APD’s own open-records response contained both the denial and the audit. David Stribling (FBI fraud task force) ran 12 searches tagged “locate alien”; Keya Chavies (ATF, non-APD employee) ran 3 more tagged “ERO assist” using APD-issued Flock credentials. APD’s denial is technically defensible; it’s also incomplete.
- The Source Code — Georgia law (2009) bans sanctuary cities; Atlanta uses “welcoming city” to avoid that prohibition — no law backs it, any mayor can change it. HB 1105 (2024) required Atlanta City Jail to honor ICE detainers, state-overriding local jail policy. Flock’s official position: “No” ICE access — ICE never needed its own account because local agencies searched on its behalf. CEO Langley August 2025 admission: CBP/HSI pilot programs ran while official denial was public. Flock deployed immigration keyword filter June 2025 (opt-in, bypassable); federal data-sharing block January 2026.
- The Upgrade — 30+ Flock cancellations since early 2025. Atlanta City Council passed two resolutions April 20, 2026 opposing ICE detention and requiring new APD guidelines. Neither resolution mentions Flock or touches the vendor contract.
- My Debug — The two governance layers (policy layer: resolutions; system layer: vendor contracts) are not governed by the same document or the same people. A sanctuary resolution that doesn’t reach into the vendor contract doesn’t govern the cameras.
Key Insight
The Atlanta piece identified the structural pattern the 3,000-arrests piece operates in: the visible policy (what officials say) and the system layer (what the machines do) are governed by separate documents. The cameras don’t attend council meetings. The resolution doesn’t talk to the API. Fixing the gap requires going into the vendor contract — which is a procurement decision, not a political one.
What It Leaves Open
- Whether APD has activated Flock’s immigration keyword filter or federal data-sharing block (unknown)
- The outcome of Mayor Dickens’s review of the two April 20 resolutions
- Whether the Atlanta Community Press Collective or other local reporters will follow up on the Chavies ATF angle (non-APD employee using APD credentials)
- How many of the 5,000+ Flock-client agencies have similar gaps between resolution language and vendor contract terms
Connections to Research Wiki
- Flock Safety — the vendor at the center; sources now 13+
- Flock Safety Surveillance Network — structural surveillance context
- Operation Metro Surge — cited directly; the “visible” enforcement vs. invisible camera network contrast
- Killing of Renée Good — Santa Cruz canceled Flock six days after Good’s killing; cited as turning point
- Vendor-State Governance — the pattern (recorded here earlier as “Vendor-Intermediary State,” now consolidated into the canonical concept page): cities contract surveillance infrastructure that enables federal enforcement the city’s official policy opposes
- Surveillance Infrastructure — broader pattern
Series Note
Published as the teaser-closer for the 3,000 Arrests, 335 Names, One Court Order piece. Closing graf explicitly names the sequel: “In the next piece, I’m looking at the federal government’s claimed 3,000+ ICE arrests across one metro area — and what the public record actually shows when you map it.”