# ACIN Media Package - Batch 1 Overview The Office of the Prosecuting Attorney for the Sixth Judicial District delivered these seven PDFs on 2026-07-21 as the first rolling-production batch for Joshua's Arkansas Criminal Intelligence Network request. They are agency-produced public-facing fact sheets, FAQs, privacy materials, and a biography - strong evidence of how ACIN describes its own architecture and governance, but not substitutes for the requested contracts, participant agreements, board records, data schemas, policies, budgets, or audit exports. ## What's inside - [[ACIN AI Fact Sheet]] - AI-supported pattern, relationship, and cross-jurisdiction analysis; human-review and audit claims; explicit mass-surveillance and dossier disclaimers. - [[ACIN Executive Overview 2026-05-15]] - partnership, near-real-time RMS federation, AWS GovCloud, security controls, governance board, and analytical capabilities. - [[ACIN FAQ 2026-05-15]] - concise answers on data, access, AI, governance, CJIS alignment, and ACIN's non-surveillance self-classification. - [[ACIN One-Page Fact Sheet]] - states that ACIN was founded in 2024, is headquartered in Little Rock, and is governed by a multi-agency board. - [[ACIN Privacy and Security Overview 2026-05-15]] - originating-agency ownership, Third Agency Rule, auditability, privacy, and annual-review claims. - [[ACIN Privacy and Security Overview 2026-05-11 Variant]] - near-duplicate earlier layout with a different Casey Clark title line. - [[Casey P. Clark Executive Biography]] - ACIN's self-authored account of Clark's LRPD career, founder role, and platform-development work. ## Key takeaways - **Statewide incident-data federation.** ACIN says it connects participating agencies' records-management systems in a CJIS-aligned cloud environment and lets them share and analyze incident-report information "in near real time" ([[ACIN Executive Overview 2026-05-15]], pp. 1-2, "Connects participating Records Management Systems (RMS)"; "share and analyze incident-report information in near real time"). - **Analytical and alerting layer.** The materials identify cross-jurisdiction case linking, relationship analysis, dashboards, pattern identification, real-time alerts, and AI-assisted links among "people, vehicles, locations, and events" ([[ACIN Executive Overview 2026-05-15]], p. 3, "relationship analysis, investigative dashboards, pattern identification, and real-time investigative alerts"; [[ACIN AI Fact Sheet]], p. 1, "possible connections between people, vehicles, locations, and events"). - **Institutional origin.** ACIN says it was developed through a partnership between the [[Sixth Judicial District Prosecuting Attorney's Office]] and the [[Little Rock Police Department]], and the one-page sheet identifies a 2024 founding date ([[ACIN Executive Overview 2026-05-15]], p. 1, "Developed through a partnership between the 6th Judicial District Prosecuting Attorney's Office and the Little Rock Police Department"; [[ACIN One-Page Fact Sheet]], p. 1, "Founded 2024"). - **Federated-control claim.** Participating agencies are said to retain ownership and control, with the "Third Agency Rule" preventing one participant from releasing another's information without originating-agency authorization ([[ACIN Privacy and Security Overview 2026-05-15]], p. 2, "Participating agencies retain ownership and control"; "cannot release another agency's information without authorization from the originating agency"). - **Security and audit claims.** ACIN identifies AWS GovCloud hosting, multi-factor authentication, role-based access, encryption, continuous monitoring, and full activity logging ([[ACIN Executive Overview 2026-05-15]], p. 2, "Hosting within AWS GovCloud (US)"; "Full audit logging and monitoring"). The batch supplies no configuration export, audit report, policy, or independent certification that tests those claims. - **Framing tension.** The same package describes a statewide, near-real-time analytical network while repeatedly stating that ACIN is not a criminal-intelligence database, surveillance system, mass-surveillance platform, or dossier system. That is tracked as [[T014 - ACIN Analytical Reach vs Non-Surveillance Classification]]. - **First-batch boundary.** No participating-agency roster, vendor contract, federal award, approved budget, board membership record, MOU, data-governance policy, retention schedule, AI model/vendor specification, or audit export appears in this media package. Those requested categories remain open in the rolling production. ## People and orgs mentioned - [[Casey P. Clark]] - Chief of Investigations, ACIN founder, and Executive Director. - [[Arkansas Criminal Intelligence Network]] - statewide initiative described by the package. - [[Sixth Judicial District Prosecuting Attorney's Office]] - development partner and Clark's employer. - [[Little Rock Police Department]] - named development partner and Clark's former agency. - [[ACIN Oversight and Governance Board]] - multi-agency governing body; no roster is produced. - [[Amazon Web Services]] - AWS GovCloud hosting environment named by ACIN. - [[Federal Bureau of Investigation]] - CJIS Security Policy is named as a governing security framework. - [[National Institute of Standards and Technology]] and [[United States Department of Justice]] - generic frameworks/guidance are invoked without identifying a specific instrument or version. ## Concepts invoked - [[Federated Incident-Data Sharing]] - [[Law-Enforcement AI-Assisted Analytics]] - [[Third Agency Rule]] - [[CJIS Compliance]] ## Events documented - [[2026-05 ACIN Materials Define the Statewide Incident-Data and AI Platform]] - [[2026-07 ACIN Acknowledges FOIA and Sends First Rolling Production]] ## Open questions / follow-ups - Which agencies participate, what data fields and historical depth are ingested, and how frequently does each RMS synchronize? - Which vendor or vendors supply the integration, search, alerting, relationship-analysis, and AI components? - Who sits on the oversight board, what authority does it possess, and what minutes, charters, policies, and review records exist? - What are the actual retention, dissemination, correction, access-review, misuse-response, and FOIA procedures? - What federal award, approved budget, procurement, and executed agreements govern the project? - Do the eventual policies and schemas support or narrow the package's non-surveillance and non-Part-23 classifications?