# Little Rock PD `PDFOI-2026-1874` — Production Overview The Little Rock Police Department's response to the **Item 2** ("internal communications referencing Flock Safety or any other ALPR vendor, deployment or expansion, hot-list configuration, network-sharing relationships, or audit-log review") portion of Arkansas FOIA request **`PDFOI-2026-1874`**, completed **2026-06-16** and downloaded **2026-06-17**. This is the **first LRPD email-correspondence production** in the corpus — the operational and relationship counterpart to the procurement **contracts** already documented in [[little-rock-pd/PDFOI-2026-1874/_overview|the City of Little Rock CLR-2026-778 production]] (`wiki/sources/city-of-little-rock/CLR-2026-778/`). It is the Little Rock analog of Conway's [[little-rock-pd/PDFOI-2026-1874/_overview|PD-2026-354]] email corpus. Where `CLR-2026-778` mapped *what LRPD bought*, this production shows *how LRPD operates and shares it* — and, inadvertently, surfaces platform-generated notifications documenting a subset of overlap-triggering searches. The correspondence does not clearly say that LRPD disposed of Item 3 as "no records," and the notifications are not a complete console audit log. ## Form of the production Three image-only PDFs — **`Emails 1-24.pdf`** (1,593 pp), **`Emails 25-35.pdf`** (569 pp), **`Emails 36-63.pdf`** (1,228 pp) — **3,390 pages / 779 MB total**, printed from the mailbox of FOIA custodian [[Domikia Davis]] (whose name banners every page) and scanned. The PDFs carry **no text layer**; the corpus was recovered by OCR (Tesseract 300 DPI) to `extracted/little-rock-pd/PDFOI-2026-1874/`. The "63 emails" are produced items; each expands to dozens of pages because most carry long threads, inline attachments, and — overwhelmingly — **bulk automated and marketing mail reproduced once per recipient**. Underlying records span **2023-05 to 2026-06**, with the bulk in **February–May 2026**. File integrity was verified against a local SHA-256 and size manifest. ## The through-line: a live operating record, not a contract file Two features define this production: 1. **It is dominated by automated Flock-platform mail** — above all hundreds of **[[Flock Deconfliction Advisory|Deconfliction Advisories]]**, each of which records a particular overlap-triggering hot-list search (searching agency, target plate, UTC timestamp, and the overlapping "Alert Owners"). The advisories are simultaneously a cross-agency information-sharing broker and a contemporaneous **partial event trail**. They identify the searching agency, not the individual user, and omit searches that triggered no overlap notice. 2. **It exposes the human and machine network behind the cameras** — a regional Arkansas hot-list-sharing web, an out-of-state and fusion-center reach, private-business camera ingest, a parallel Axon-Fusus RTCC platform, the Flock–Axon interoperability rupture, an active drone unit, and LRPD's FOIA-disclosure posture. ## What's inside — by theme (per-thread source pages) - **[[Flock Deconfliction Advisories and the LRPD Sharing Network]]** — the analytic core: the deconfliction mechanism; the regional Arkansas network ([[North Little Rock Police Department]], [[Sherwood Police Department]], Springdale, Pine Bluff, Morrilton, Haskell PDs, [[Pulaski County Sheriff's Office]], and [[Arkansas State Police]] via `asp.arkansas.gov` alert owners, distinct from ACIC); the RTCC as a first-class Alert Owner (`[email protected]`); ~20 out-of-state/fusion-center Search-access requests. - **[[Home Depot Camera Sharing into LRPD]]** — six Arkansas Home Depot stores (#1401/1402/1405/1407/1412/8919) sharing private Flock cameras into LRPD's searchable network (Feb 2026) — the *same* store numbers that shared into Conway. - **[[Flock-Axon API Dispute and the Dual RTCC Stack]]** — LRPD runs Axon **Fusus** in parallel with Flock; the Flock↔Axon API rupture and competing fixed-ALPR pitches. - **[[Flock LPR Deployment Expansion and Permitting Delays]]** — intersection-level fleet mapping; an expansion project; ~$27,000 of cameras stuck ~1 year in city permitting; the "Full City Coverage Plan." - **[[Resolution 16489 and the 30-Cameras Discrepancy]]** — public "30 new cameras" framing vs internal "renewal only." - **[[LRPD FOIA Handling and Disclosure Posture]]** — partner-site withholding to The Markup; a death-investigation footage denial under Ark. Code 12-12-211; press/citizen FOIAs; Flock-supplied case law. - **[[Chief Helton RTCC Defense Thread]]** — Chief Helton's internal response to the national "de-flocking" news cycle. - **[[LRPD sUAS Drone Unit]]** — an adjacent surveillance program in the same Technology & Equipment Unit. - **[[Federal Data-Sharing Controls and Federal-Access Posture]]** — Flock's federal opt-in toggle, ICE-denial messaging, and the *absence* of the Federal Searches CSV / SharedNetworks CSV here. - **[[Flock Audit and Compliance Controls and Gaps]]** — required NIBRS offense type, `***` masking, the out-of-state Network Audit filter, and the documented Axon "confidence changes are not logged" gap. - **[[SoundThinking ShotSpotter and CaseBuilder Correspondence]]** — gunshot-detection correspondence swept in by keyword. - **[[Vendor Marketing Saturation and Competitor ALPR Pitches]]** — the marketing long tail and competitor ALPR pitches (Axon, Motorola, SoundThinking, and others). ## Key takeaways - **Item 3 remains procedurally unresolved.** LRPD's May 26 email said, *"There are no records that meet the request for the portion of the audit-log review,"* but did not identify that sentence as an Item-3 disposition. Joshua's June 5 reply expressly asked LRPD to clarify Items 3 and 4; live Gmail review on 2026-07-21 found no answer. The Item-2 production contains Deconfliction Advisories documenting particular searches at the agency/plate/time level, while the named **Federal Searches**, **SharedNetworks**, and monthly Audit-view exports are absent. The current evidentiary boundary is documented at [[T004 - Ambiguous Audit-Log-Review Response vs Unresolved Item 3]]. - **LRPD sits inside a regional Arkansas Flock hot-list network** — North Little Rock, Sherwood, Springdale, Pine Bluff, Morrilton, Haskell PDs, Pulaski County SO, and Arkansas State Police — with reach extending to ~20 out-of-state agencies and at least one fusion center (Missouri Information Analysis Center). The default posture pushes sharing onto "each individual Alert Owner." - **Private-business cameras flow in by the same mechanism documented at Conway** — the identical six Arkansas Home Depot stores. See [[2026-02 Home Depot Shares Cameras with Little Rock PD]]. - **LRPD runs a dual RTCC stack** — Flock LPR alongside Axon **Fusus** — and is caught in the **Flock↔Axon API dispute** ([[2025-07 Axon Terminates Flock API Partnership]]), which contests the agency's ability to use its own Flock data in Fusus. - **The production restores sixteen exact device/corridor/direction names but no coordinates.** Twelve are in the 2024 permitting/relocation list and four in maintenance/support records. They are preserved verbatim — with visually verified source misspellings disclosed — at [[Flock LPR Deployment Expansion and Permitting Delays]] and [[Arkansas ALPR Camera Coordinates and Directional Nomenclature]]. - **A public-record discrepancy:** the Feb 2025 renewal was framed publicly as "30 new cameras" while this production's internal Board Communication and staff email describe a subscription renewal plus one camera — tracked at [[T005 - Thirty New Cameras vs Renewal-Only]]. - **Disclosure posture leans toward withholding:** partner-site identities omitted from a Markup production; Flock footage denied in a death investigation; vendor-supplied case law ([[ALPR-Favorable Case Law as Vendor Messaging]]) circulating internally. - **An anomalous citizen complaint** alleging ALPR/surveillance misuse is present — but it is the complainant's own document of doubtful authenticity, **not** an LRPD work product. Handled with caveats at [[2025-03 Civilian ALPR-Misuse Complaint]]; no misconduct is asserted. ## FOIA correspondence trace Correspondence is retained in Gmail, not duplicated in the produced-record corpus. Portal: `[email protected]` (the LRPD "Little Rock Police FOIA Requests" portal); completion from `[email protected]`. | Date / time (UTC) | Event | Gmail thread | |---|---|---| | 2026-05-19 00:32 | Request filed to `[email protected]` (4-item ALPR template) | `19e3d8f1e79eb989` | | 2026-05-20 01:00 | Confirmed as **`PDFOI-2026-1874`**, security key retained in private correspondence | `19e42e6038f6ad6d` | | 2026-05-27 00:11 | Davis response: Item 1 → City Hall FOIA; *"no records"* for *"the portion of the audit-log review"* without assigning the sentence to a numbered item; Flock emails by June 16 | `19e66c584957444d` | | 2026-06-05 14:47 | Requester follow-up states the two plausible readings and asks LRPD to clarify the status of Items 3 and 4; no later answer located as of 2026-07-21 | `19e66c584957444d` | | 2026-06-16 17:52 | Production **completed**; portal release | `19ed190634d2e935` | | 2026-06-17 | `Records_Request_Download_PDFOI-2026-1874_*.zip` downloaded (779 MB) | — | **Distinct from `CLR-2026-778`.** That is a City-Hall procurement-records request (the contracts); this is the **LRPD operational portal** request. Item 1 (procurement) of `PDFOI-2026-1874` was referred to City Hall and is substantially answered by `CLR-2026-778`; Items 3 (usage/audit) and 4 (asset-forfeiture authorization) were not clearly disposed of in the correspondence reviewed. This production is the **Item 2** Flock-email portion. ## People and orgs mentioned - LRPD (existing pages): [[Heath Helton]] (Chief), [[Courtney Bewley]] (Lt., Technology & Equipment Unit), [[James Phillips]] (Sgt., RTCC), [[Jonathan Prater]] (Major), [[Latreasa Mullins-Sanders]] (Finance), [[Micheal Miller]] (Asst. Chief), [[Brittany Gunn]], [[Christna Plummer]], [[Abdoul Kabaou]] (City CIO). - New people this production: [[Debra Pitts]] (RTCC technician), [[Domikia Davis]] (FOIA custodian), [[Garrett Langley]] (Flock CEO). Hundreds of LRPD officer "Alert Owners" appear in the deconfliction series and are named within source pages by official role, not individually paged. - Vendors: [[Flock Safety, Inc.]], [[Axon Enterprise, Inc.]] / [[Fusus]], [[SoundThinking]], [[Motorola Solutions]], [[Insight Public Sector, Inc.]] (reseller), [[Blue to Gold LLC]]. - Sharing counterparties: [[North Little Rock Police Department]], [[Sherwood Police Department]], [[Pulaski County Sheriff's Office]], [[Arkansas State Police]], [[The Home Depot, Inc.]], [[Federal Bureau of Investigation]]. ## Concepts invoked - [[Flock Deconfliction Advisory]] · [[Flock Network Sharing - Hot Lists]] · [[Surveillance Data Sharing — Default-On Posture]] · [[Hot List]] - [[Private-Business Camera Sharing into LE Networks]] · [[Federal LE Data-Sharing Pipeline]] · [[Flock Audit Logs and Retention]] - [[Real-Time Crime Center (RTCC)]] · [[Automatic License Plate Reader (ALPR)]] · [[CJIS Compliance]] · [[ACIC NCIC Hot-List Feed]] - [[Vendor Platform Lock-In and the Flock-Axon API Dispute]] · [[ALPR-Favorable Case Law as Vendor Messaging]] · [[Cooperative Purchasing Vehicle]] ## Events documented - [[2026-06 Little Rock PD PDFOI-2026-1874 FOIA Response]] (this FOIA-correspondence event) - [[2026-02 Home Depot Shares Cameras with Little Rock PD]] - [[2025-07 Axon Terminates Flock API Partnership]] - [[2025-02 Little Rock Amends Resolution 16489 Flock Renewal]] - [[2025-03 Civilian ALPR-Misuse Complaint]] (caveated anomaly) ## What the records contain This is an operational production and is **saturated with PII**: hundreds of target license-plate numbers, officers' personal cell numbers, cross-agency contact details, specific camera intersections, BOLO suspect plates/VINs, ShotSpotter activation addresses, and the name of a death-investigation decedent. The agency applied few redactions of its own. ## Open questions / follow-ups 1. **Item-3 reconciliation (bracketed).** The Deconfliction Advisories are existing notification emails that document a subset of searches at the searching-agency/plate/time level; they do not identify the searching officer or prove that LRPD held the requested console exports. The Federal Searches CSV, SharedNetworks CSV, and monthly Audit-view exports named in the request were not produced. No supplement was filed. If Joshua later chooses a successor filing, [[T004 - Ambiguous Audit-Log-Review Response vs Unresolved Item 3]] recommends a new, narrow request for existing configuration, retention, administrator-access, export-capability, and actually saved export records. See also [[Arkansas FOIA Electronic Records and Vendor Custody]]. 2. **Item 4 (asset-forfeiture authorization)** was never directly addressed for the LRPD ALPR procurement; `CLR-2026-778` shows the Flock renewal funded from a **general-fund** line (105225-63360), but the original-procurement and any forfeiture-funded components remain to be confirmed. 3. **The "30 new cameras" discrepancy** ([[T005 - Thirty New Cameras vs Renewal-Only]]) — whether a drafting error or a pared-back expansion. 4. **Axon Fusus as a second ALPR system** generates its own audit/sharing records not covered by this request — a candidate for a follow-up. 5. **Completeness:** Lt. Bewley's partner-site withholding to The Markup raises whether partner-site identities were similarly limited here.