# T030 — ACIN Incident-Report-Only Scope vs Investigative Data Services ACIN's MOU and core integration policy repeatedly say only incident-report information enters the network and investigative files are excluded. Other provisions in the same manual and the executed LeadsOnline package expressly cover investigative case notes, attachments, suspect associations, narratives, phone extractions, communications, movement, device, vehicle, and location data. The records do not establish which scope controls the implemented system. ## Statement A - The MOU says, "(ONLY INCIDENT REPORT INFORMATION) Not to include investigative files" ([[ACIN Agreements and Participation Terms]], `AGR-201_El_Dorado_PD_MOU_EXECUTED_2026-05-15.pdf`, p. 1). - The manual says, "Only incident report information (not investigative files) may be shared" and defines case data as non-narrative identifiers ([[ACIN Policy and Operations Manual]], `POL-301_ACIN_Policy_and_Operations_Manual_REDACTED_2026-01.pdf`, p. 16). - The kickoff packet describes incident-level RMS data and again says "NOT investigative files" ([[ACIN Governance Board and Controlled Repository]], `GOV-102_ACIN_Governance_Board_Kickoff_Packet_2026-04.pdf`, p. 1). ## Statement B - The manual's Security and Privacy Governance Policy defines Tier 2 "Investigative Data" as "Case notes, attachments, and suspect associations" ([[ACIN Policy and Operations Manual]], `POL-301_ACIN_Policy_and_Operations_Manual_REDACTED_2026-01.pdf`, p. 47). - LeadSuite accepts case files, AI-driven narrative material, summaries, timelines, phone extractions, and complete-case sharing ([[LeadsOnline Executed Contract]], `CON-001_LeadsOnline_Executed_Contract_2026-07-13.pdf`, pp. 15-17, 25). - NightHawk accepts communications and movement data for devices, vehicles, and other entities, including locations (pp. 46-47). - Peregrine's general platform supports link, temporal, geospatial, alerting, and multi-source analytical functions ([[Peregrine and Carahsoft Executed Contract]], `CON-002_Peregrine_Carahsoft_Executed_Contract_2026-03-17.pdf`, p. 5). ## Why it matters The scope determines what individuals, events, communications, locations, and investigative material can be searched or linked across agencies. It is load-bearing to ACIN's non-surveillance and non-Part-23 framing, retention obligations, discovery, access control, audit design, and public description. ## Resolution status `open` — resolution requires the implemented data dictionary, interface mappings, agency configurations, source-specific exclusions, approved LeadSuite/NightHawk/CellHawk use, and representative audit records. ## Discovery Surfaced during the 2026-07-25 ingest of [[pulaski-county-prosecutor/2026-07-24-acin-final-package/_overview|ACIN Final Package Overview]]. ## Notes The contract capabilities do not prove that every capability was activated. The incident-only language likewise cannot be treated as the implemented boundary without configuration and usage evidence.