# T007 — ASP No-LPR-System Position vs Documented ELSAG Operation In April 2025 the Federal Public Defender quoted ASP's FOIA response that ASP *"does not 'have' a license plate reader system,"* and contested it — arguing the ALPR statute turns on *"use,"* and citing an Arkansas State Trooper's report admitting ELSAG use. The same corpus documents ASP procuring, siting, naming, training on, and operating an ELSAG ALPR network. The tension is **factual**: whether ASP's "no LPR system" position can be squared with its documented ELSAG operation, or whether it was a contestable characterization. ## Statement A — ASP does not "have" a license plate reader system ASP's FOIA-facing position, quoted back by the requester: > *"Regarding your response that ASP does not 'have' a license plate reader system…"* ([[Federal Public Defender FOIA and the No-LPR-System Position]]; Tier-1 corpus, `RE_ Freedom Of Information Request from Arkansas Federal Public Defender.msg`). A cognate posture appears in ASP's internal FOIA coaching: Overton advises that camera-location requests are *"an easy denial,"* distinguishing ASP from Flock users who *"must reply"* because Flock publishes locations ([[Citizen Flock FOIA and ASP Withholding Strategy]]; Tier-1 corpus, `RE_ Flock FOIA - ASP.msg`). ## Statement B — ASP owns, operates, and uses an ELSAG ALPR system The corpus documents ASP's ELSAG system in detail: - **Procurement and ownership:** the [[Term Contract 4600055190 and PO 4502235324 — Initial Leonardo ELSAG Buy|Leonardo/ELSAG term contract and POs]] (2026-06-05 fiscal production). - **Deployment:** 39 F4 fixed cameras plus solar Street Sentry across Arkansas Interstates, named to the HIDTA EOC ([[F4 Installs and Site Nomenclature]]; Tier-1 corpus, `RE_ ARKANSAS STATE POLICE - FIXED LPR Project - Budget (2).msg`, `RE_ Names for Sites.msg`). - **Operation and access:** an ASP-administered ELSAG domain, hot lists, a silent list, operator training, and analyst query access ([[ASP–Houston HIDTA MOU and ELSAG Domain Architecture]], [[Cross-Network Analyst Access and the Arkansas State Fusion Center]]). - **Admitted use in the field:** the Federal Public Defender cites Trooper Tanner Hess's report — *"Entries on the ELSAG license plate reader system showed that a white Sprinter van…"* ([[Federal Public Defender FOIA and the No-LPR-System Position]]; Tier-1 corpus, same file). ## Why it matters The [[Arkansas Automatic License Plate Reader System Act]] (per the [[Act 668 of 2025 — Internal ALPR-Law Summary|Act 668 summary]]) imposes duties — retention limits, six-month public reporting under § 12-12-1805, published data-handling rules — on governmental **users** of ALPR. If ASP is a "user" (Statement B), those duties attach and its FOIA obligations are broader; if ASP genuinely "does not have" a system in the relevant sense (Statement A), it might argue reduced obligations. The Federal Public Defender's point — that § 12-12-1805 keys on "use," and ASP demonstrably uses ELSAG — is the crux. The disposition affects both FOIA-transparency expectations and statutory-compliance questions. ## What the record supports and does not support The record **overwhelmingly supports** Statement B: ASP's ownership, deployment, and use of ELSAG is documented across both productions and admitted in a trooper's report (Tier-1 corpus, multiple files). Statement A is now located verbatim in the produced thread — "Please be advised that ASP does not have a License Plate Reader system," Ryan Roach, 2025-04-14 — with the scare quotes around "have" originating in the requester's rebuttal rather than in ASP's sentence. What the sentence does not resolve on its face is any term-of-art qualification ("own" vs. "access," ASP-hosted vs. HIDTA-hosted servers). [[D004 Synthesis]] settles the tension in Statement B's favor: the dated procurement and deployment paper predates the sentence, the custody framework said to ground it postdates it by a month, and the Act is keyed to use, which every voice in the record concedes. *(Erratum, 2026-07-23: an earlier version of this section described Statement A as documented only as quoted by the requester.)* ## Resolution status **resolved-via-D004** (2026-07-23). The three-phase dialectic fixed Statement A's verbatim wording and resolved the tension in Statement B's favor: ASP's own August 2024 purchase order and term contract, December 2024 installs, and January 2025 expansion predate the April 14, 2025 sentence; the HIDTA custody MOU said to ground it was not executed until May 15, 2025; and use is conceded by every voice in the record under a use-keyed statute. The sentence was false in substance as a description of the agency's documented holdings and immaterial to the § 12-12-1805 duties the request invoked. Preserved as narrower open questions for successor work: Roach's personal knowledge on April 14, the scope of Gough's "own" statement, the ASP-owned cameras' live-and-queryable date, and whether any correction ever reached the requester. See [[D004 Synthesis]]. ## Discovery Surfaced by the 2026-07-07 internal-comms ingest (2026-07-07), reading the Federal Public Defender thread against the deployment, domain, and training records. ## Notes - Dialectic phases: [[D004 Thesis]] · [[D004 Antithesis]] · [[D004 Synthesis]] (run 2026-07-23). - Complements an inline `> [!contradiction]` callout on [[Arkansas State Police]]. - Distinct from [[T006 - ASP ALPR Oversight Disclaimer vs Statewide Coordination Role|T006]] (which concerns ASP's coordination role over the wider ALPR field); T007 concerns whether ASP concedes operating an ALPR system at all.