# 2025-12-17 Flock Platform Cutover A Flock platform-side change that (a) reduced audit-log schema from 14 columns to 13 columns, and (b) coincides with the date of the only [[SharedNetworks 2025-12-17 Snapshot]] in the production. Flock's rationale, per the announcement email `Important Update to Flock Audit Logs to Protect Officer Safety Active Investigations.msg`, is to "Protect Officer Safety [during] Active Investigations" — language that implies the removed column carried information that could compromise undercover or sensitive operations if FOIA-released. ## Sources - [[Conway PD Audit Logs Series]] — schema change visible across the boundary file: `12_1_2025-12_17_2025-Conway AR PD-Audit (1) - Redacted.csv` (14 cols) → `1_1_2026-1_31_2026-Conway AR PD-Audit - Redacted.csv` (13 cols). - [[SharedNetworks 2025-12-17 Snapshot]] — dated to the same day. - `Important Update to Flock Audit Logs to Protect Officer Safety Active Investigations.msg` (raw / extracted; full review of the announcement email remains pending). ## Significance - The platform-change moment is a small but meaningful detail: it shows Flock proactively modifying the audit-log schema in response to (presumably FOIA-related) public-records pressure. The "Protect Officer Safety" framing suggests Flock has internalized that audit-log data is being FOIA-released; the change reduces what is visible. - For investigators, the cutover establishes that **the audit-log content available via FOIA is not stable over time** — Flock can and does modify what is logged. Any deliverable that relies on audit-log content should be careful to specify which schema version it cites. - A closer reading of the announcement email itself is the next step to confirm which column was removed and Flock's official rationale. ## Open - Exact column dropped: pending verification (provisionally `Text Prompt` or `Moderation`). - Whether Conway PD or Flock initiated the related SharedNetworks snapshot on the same day, and for what purpose, is not clear from the corpus.