# Federal LE Data-Sharing Pipeline *Erratum, 2026-07-30: an earlier version treated every federal-search row as proof that Conway data was touched. The search export does not name the networks searched or returned; the topology and activity files cannot be joined row by row.* *Erratum, 2026-08-02: a full-file timestamp parse corrected the search interval to 2026-03-14 through 2026-04-13, across 31 calendar dates; the full-file network-count range is 586–2,878.* The record set pairs two Flock artifacts produced by Conway PD: the [[Federal Searches CSV]] (5,929 federal-tagged lookup rows across 31 calendar dates) and the [[SharedNetworks 2025-12-17 Snapshot]] (Conway's configured relationship topology). The search export records organization, network-count, reason, timestamp, and search type but not network identity or result. Neither export has a field for a warrant, MOU, elected-body authorization, or separate approval record; absence from those fields is not proof that no such record exists elsewhere. ## How it appears in the corpus **Mechanism (operational):** 1. The search export labels the FBI, USPIS, and NPS rows with Flock's `[Federal]` organization prefix. 2. Each row carries a `Total Networks Searched` count, but the CSV does not enumerate those networks or identify results. 3. The separate SharedNetworks export records Conway's incoming, outgoing, and bilateral configuration, including federal-tagged counterparties. 4. The artifacts document federal-tagged activity and Conway topology separately. The corpus does not contain a row-level key proving which search reached which Conway record. **Volume (corpus-confirmed, March 14, 2026 – April 13, 2026):** | Agency | Searches | Share | |---|---:|---:| | US Postal Inspection Service | 3,502 | 59.1% | | Federal Bureau of Investigation | 2,385 | 40.2% | | Natchez Trace Parkway NPS | 42 | 0.7% | | **Total** | **5,929** | **100%** | **Notable absences (March–April 2026 window):** - ICE / Homeland Security Investigations - DHS / Customs and Border Protection - DEA / ATF / US Marshals - Arkansas State Police (state-level analog) These absences are *information*, not evidence of non-access — a different window or a non-`[Federal]`-prefixed login (e.g., JTTF officer with state-police credentials) would not appear in this export. ## Stakeholders - **Federal LE agencies** — the searching organizations named in the export's `Org Name` field. - **Local LE (Conway PD)** — the producing agency and the anchor of the separate SharedNetworks topology. - **The vendor (Flock)** — the platform operator that mediates the relationship, records the activity, and generates the exports. **Flock is the choke point**: relationships exist only inside Flock's product; activity exists only because Flock's platform enables cross-organizational queries. - **The public** — this activity became visible through the produced audit export. The corpus does not identify another Conway disclosure channel. ## Timeline - 2025-12-17 — Flock platform cutover; [[SharedNetworks 2025-12-17 Snapshot]] dated. - 2026-03-14 → 2026-04-13 — [[Federal Searches CSV]] window: 5,929 federal lookups. - 2026-04-17 — Joshua's FOIA filed. - 2026-04-23 — Conway PD completes production including the Federal Searches export. ### In PDFOI-2026-1874 (LRPD Flock emails) The Little Rock PD production surfaces vendor-described controls but — unlike Conway — produced no Federal Searches export to quantify activity. Flock's February 2026 newsletter announces “Agency-Level Control for Federal Data Sharing” and a “Federal Opt-In capability” ([[Federal Data-Sharing Controls and Federal-Access Posture]], `Emails 36-63.pdf`, pp. 305, 565, 573, 656). Those notices establish a configurable feature, not the earlier tenant default or LRPD's setting. The same corpus carries Flock's ICE-does-not-use-Flock messaging — a vendor claim, not an LRPD fact — and a CJIS login disclaimer addressing authorized use (`Emails 36-63.pdf`, pp. 521, 523). No Federal Searches CSV appears in the LRPD production, so that record set does not quantify whether or how federal-tagged users searched LRPD-associated data. ## Notes - The findings bearing most directly on oversight are: 1. **Topology plus activity, without a row-level join** — one file documents Conway relationships and another documents federal-tagged searches; neither identifies the initial default or every authorization record. 2. **Search reasons** — FBI uses “Other - Not Applicable” uniformly; USPIS uses “Financial Crime (Embezzlement/Fraud) - Inspections.” The export shows those labels on completed searches but does not expose the interface's validation rules or underlying case facts. 3. **Volume scale** — the export contains 5,929 federal-tagged rows across 31 calendar dates, each carrying a three- or four-digit network-count field. It does not say which networks returned data. 4. **Vendor centrality** — Flock operates the platform and generates the exports. The corpus does not show independent agency-side copies of the underlying platform records. - See [[Federal Searches CSV]] for the specific data anchor and the open questions about other windows, non-`[Federal]`-prefixed federal logins, and missing agencies.