# D003 — Thesis: ASP Holds No Statewide ALPR Oversight or Coordination Role ## Claim The [[Arkansas State Police]] conducts no oversight, audit, or approval of any other agency's ALPR use, and it holds no state-level, CJIS-Systems-Agency-style coordination role over Arkansas ALPR deployments. The single on-record documentary statement that speaks directly to the FOIA's structural question settles it. [[Ryan Roach]], attorney for the [[Arkansas Department of Public Safety]], stated on counsel that ASP "does not conduct any reviews, audits, or approvals of other agencies or municipalities and their use of ALRPs" ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e9863c17b09083). Every artifact later adduced against this conclusion shows ASP administering its own domain or representing itself outward to a federal network; none shows ASP exercising authority over a municipal or county deployment. Counsel's Item-4 disclaimer is the accurate characterization: ASP is one ALPR operator among many, and its point-of-contact and domain-administration activity is internal self-administration plus external self-representation, not authority over other agencies. The coordination locus the FOIA was built to find, if it exists in Arkansas at all, sits at the [[Arkansas Crime Information Center|ACIC]], not at ASP. ## Argument ### (a) The disclaimer is an on-counsel, effective no-records disposition, and it is Tier-1 The Item-4 disclaimer is not a stray aside. It is a written representation by the agency's own attorney, made inside the FOIA correspondence thread in direct response to the request's CJIS-Systems-Agency question. Roach used epistemic qualifiers — “to my knowledge” and “I do not believe” — but gave the substantive position that ASP conducts no reviews, audits, or approvals of others and that his office likely held no Item-4 records ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e9863c17b09083). The thesis treats that as an effective no-records disposition on the question asked. It carries the documentary weight of the agency speaking through counsel about what it does and does not do. The production overview identifies it as the batch's most analytically important documentary moment; [[D003 Synthesis]] ultimately narrows the thesis by distinguishing formal authority from functional coordination. ### (b) "Point of contact for Arkansas" is a directory label, not a grant of authority The point-of-contact designation originates in an external survey circulated by a federal and interstate network, soliciting one named coordinator per state. Being the name a federal network writes down for Arkansas is a liaison and representation function. It tells you whom the network contacts about Arkansas; it does not tell you that the contacted party commands other Arkansas agencies. A point of contact is a mailbox, not a magistrate. The tension page concedes exactly this: the point-of-contact role is "external representation plus its own footprint, not documented supervision of municipal/county deployments" ([[T006 - ASP ALPR Oversight Disclaimer vs Statewide Coordination Role]], "What the record supports and does not support"). Self-representation to outsiders is not authority over insiders. To read a survey-line entry as a delegation of statewide supervisory power is to confuse a directory with a chain of command. ### (c) Administering the ELSAG/HIDTA domain is running one's own house The domain ASP administers in the ELSAG/HIDTA platform is "AR Arkansas State Police," with "AR Arkansas Highway Police" nested inside it. Both are Department of Public Safety entities: [[Arkansas Highway Police]] is a DPS component, as is [[Arkansas State Police|ASP]] itself. Administering hot lists, points of contact, and user access within a domain that contains only your own agency and a sister DPS agency is internal self-administration. It is exactly what one expects of an operator managing its own footprint, and nothing more. It reaches no municipal police department and no sheriff's office. The tension page states the point without qualification: "the domain it administers contains ASP and [[Arkansas Highway Police]] (both DPS)" ([[T006 - ASP ALPR Oversight Disclaimer vs Statewide Coordination Role]], "What the record supports and does not support"). Read at its strongest, the coordination evidence stops at the DPS boundary. It never crosses into the "other agencies or municipalities" that Item 4 was about. Running the DPS family's own domain is emphatically not overseeing the wider field of Arkansas ALPR operators. ### (d) The genuine state-level CJIS/oversight locus, if any, is ACIC The CJIS-Systems-Agency role is a term of art: a CSA holds audit, compliance, and approval authority over the agencies whose federal-database access it sponsors. That authority is exactly the content Roach disclaims. And Roach points elsewhere for it: the information "would likely need to be requested directly from the agency with control over the ALPRs" ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e9863c17b09083). The source overview treats ACIC as the next entity to test, not as a proved ALPR oversight authority. The FOIA tested ASP for formal review/audit/approval and got a negative response. Locating formal oversight at ASP would therefore require evidence beyond the functional coordination records later produced; the still-un-FOIA'd ACIC remains an open target rather than a resolved locus. ### (e) The absence of any documented ASP audit of another agency is itself evidence After a rolling-release production, in which the Lieutenant in charge of ASP's ALPRs "has a large amount of emails responsive to this request" and later released them ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e984750bf856da), there is no produced record of ASP reviewing, auditing, or approving another agency's ALPR use. The narrower defensible conclusion is absence from the reviewed production, reinforced by counsel's disclaimer; it is not proof that no such record could exist elsewhere. ### The two statements are not a factual contradiction The tension between Statement A and Statement B is framing, not fact. The tension page itself concedes the statements are "not a clean factual contradiction" and are "compatible descriptions of different things (formal oversight of others vs. functional statewide coordination)." Statement B survives only by sliding from "coordination point," a label, to "coordination authority," a supervisory power. Item 4 asked about the latter. Roach answered the latter. The answer is no. On the question the FOIA actually posed, Statement A is not merely defensible; it is the only reading the record supports. ## Evidence Primary Tier-1 source, the Item-4 disclaimer: > "to my knowledge ASP does not conduct any reviews, audits, or approvals of other agencies or municipalities and their use of ALRPs. I do not believe our office would have any records related to request number 4, and that information would likely need to be requested directly from the agency with control over the ALPRs." ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e9863c17b09083) Supporting Tier-1 source, the routing message documenting a good-faith production by the operational custodian (relevant to point (e), the evidentiary weight of the missing audit records): > the Lieutenant "advised that he has a large amount of emails responsive to this request, and I planned to release these to you on a rolling basis as I receive them." ([[arkansas-state-police/2026-06-05-batch-1-fiscal/_overview|ASP fiscal production overview]], Gmail thread 19e3d8ec9e0f6ccd, msg 19e984750bf856da) Tension-page concessions relied upon (shared reading, "What the record supports and does not support"): > the record "does not show ASP reviewing, auditing, or approving *other* agencies' ALPR use: the domain it administers contains ASP and [[Arkansas Highway Police]] (both DPS), and the point-of-contact role is external representation plus its own footprint, not documented supervision of municipal/county deployments." ([[T006 - ASP ALPR Oversight Disclaimer vs Statewide Coordination Role]]) Cannot verify, and the record does not establish, any instance of ASP auditing, approving, or reviewing a municipal or county agency's ALPR deployment. No such record appears in the production, and counsel affirmatively states none should exist. That absence is load-bearing for this thesis, not a gap in it. ## Anticipated counterarguments The antithesis will marshal Statement B and press three objections, which this thesis names but does not engage here (rebuttal is the antithesis's task): 1. **The point-of-contact designation.** [[Dennis Overton|Lt. Overton]] appears as the "ALPR Point of Contact for Arkansas" in a federal and multistate coordinator network, a survey soliciting one per-state coordinator who "manages ALPR resources; training, policy, deployment, servers." 2. **Domain administration.** ASP administers the Arkansas ALPR domain inside the HIDTA/ELSAG platform, including hot lists "seen by all in that domain," designated points of contact, and delegated admin rights. 3. **Cross-network analyst access.** ASP analysts are provisioned across ELSAG, Motorola LPR, Flock, AR Advance, ATLAS, and ACIC via the Arkansas State Fusion Center, which the antithesis will frame as functional statewide centrality. These are acknowledged as the live objections. The thesis maintains that none of them reaches the "other agencies or municipalities" that Item 4 concerned, and that counsel's disclaimer accurately characterizes the record on that question.