# T014 - ACIN Analytical Reach vs Non-Surveillance Classification ACIN places two coherent descriptions side by side. One describes a cross-jurisdiction environment capable of ingesting case material and linking incidents, people, vehicles, locations, devices, communications, and movement through search, geospatial, temporal, relationship, narrative, alerting, and AI functions. The other insists that ACIN is not a criminal-intelligence database, public- or mass-surveillance system, predictive-policing system, or dossier system. The final package supplies agreements, policies, and executed vendor terms that deepen the tension but still does not establish the implemented data scope or resolve the legal and operational classification. ## Statement A ACIN has surveillance-relevant analytical reach even if much of its data originates in agency records rather than public camera feeds. - ACIN says agencies can "share and analyze incident-report information in near real time" and lists cross-jurisdiction case linking, relationship analysis, dashboards, pattern identification, and real-time investigative alerts ([[ACIN Executive Overview 2026-05-15]], pp. 2-3). - Peregrine's executed terms describe comprehensive search, dashboards, real-time alerts, trend, geospatial, link, and temporal analysis across integrated sources ([[Peregrine and Carahsoft Executed Contract]], `CON-002_Peregrine_Carahsoft_Executed_Contract_2026-03-17.pdf`, p. 5). - LeadsOnline's executed terms cover automated case searching, AI-generated narratives and timelines, phone-extraction material, communications and movement, GPS and other location references, LPR hits, link charts, and cross-agency collaboration ([[LeadsOnline Executed Contract]], `CON-001_LeadsOnline_Executed_Contract_2026-07-13.pdf`, pp. 15-17, 25, 46-47). - The policy manual expressly classifies case notes, attachments, and suspect associations as investigative data, even though another section excludes investigative files ([[ACIN Policy and Operations Manual]], `POL-301_ACIN_Policy_and_Operations_Manual_REDACTED_2026-01.pdf`, pp. 16, 47). That data-scope conflict is tracked separately at [[T030 - ACIN Incident-Report-Only Scope vs Investigative Data Services]]. ## Statement B ACIN classifies the platform as factual incident-data sharing and investigative support, not surveillance or a Part-23 criminal-intelligence repository, and it adopts human-review and access-control language. - "ACIN is not a criminal intelligence database and does not maintain standalone criminal intelligence files as defined under 28 CFR Part 23" ([[ACIN Executive Overview 2026-05-15]], p. 2). - "ACIN is not a public surveillance system and is not designed for mass surveillance activities" ([[ACIN FAQ 2026-05-15]], p. 1). - The AI fact sheet says ACIN is not "A predictive policing system targeting innocent citizens," "A mass surveillance platform," or "A system for collecting intelligence dossiers on citizens" ([[ACIN AI Fact Sheet]], p. 1). - The standard MOU and integration policy limit shared RMS material to incident-report information and expressly exclude investigative files ([[ACIN Agreements and Participation Terms]], `AGR-201_El_Dorado_PD_MOU_EXECUTED_2026-05-15.pdf`, p. 1; [[ACIN Policy and Operations Manual]], `POL-301_ACIN_Policy_and_Operations_Manual_REDACTED_2026-01.pdf`, p. 16). - The contract addendum and AI-policy materials require human review of AI-supported decisions and prohibit autonomous or unauthorized uses ([[Peregrine and Carahsoft Executed Contract]], `CON-002_Peregrine_Carahsoft_Executed_Contract_2026-03-17.pdf`, p. 22; [[ACIN AI Policy and CLEST Training Packet]], `GOV-202_Arkansas_AI_Acceptable_Use_Policy_Final_2026-02-26.pdf`, pp. 1-4). ## Why it matters The classification affects which governance, retention, dissemination, auditing, access, public-notice, and legal-accountability questions investigators and policymakers ask. Accepting ACIN's label without testing the configured system could obscure the practical reach of case, relationship, location, and movement analysis. Treating every form of incident-data collaboration as equivalent to public-space surveillance could erase important distinctions among source data, access predicates, retention, and use. ## Resolution status `open` - the final package resolves the earlier absence of contracts, participant forms, and written policies, but it does not establish which capabilities or data classes were funded, activated, configured, or used. Resolution requires the operative data dictionary and schemas, accepted integration inventory, configuration and permissions exports, live access and audit records, model/feature approvals, retention implementation, representative queries or alerts, and any legal analysis supporting the non-Part-23 and non-surveillance classifications. ## Discovery Surfaced during the 2026-07-21 ingest of [[pulaski-county-prosecutor/2026-07-21-acin-media-package-batch-1/_overview|ACIN Media Package - Batch 1 Overview]] and materially deepened by [[pulaski-county-prosecutor/2026-07-24-acin-final-package/_overview|ACIN Final Package Overview]] on 2026-07-25. ## Notes This tension is descriptive and analytical. It does not decide whether 28 CFR Part 23 applies or whether ACIN meets any statutory or constitutional definition of surveillance. Executed contracts establish assent to available services; the produced record does not prove that funding, payment, activation, or operational use occurred.