# T004 — Ambiguous Audit-Log-Review Response vs Unresolved Item 3 ## The tension On 2026-05-26, LRPD custodian [[Domikia Davis]] wrote: "There are no records that meet the request for the portion of the audit-log review" (Gmail thread `19e66c584957444d`, message `19e66c584957444d`). The sentence followed the Item-1 procurement referral and preceded a three-week schedule for the Flock-email portion of Item 2. It did **not** say "Item 3," identify the named console exports, or state that no usage/audit records existed. Joshua's 2026-06-05 reply expressly identified two possible readings and asked LRPD to state the status of Items 3 and 4 (same thread, sent message `19e984151966cde2`). Live Gmail reconciliation on 2026-07-21 found no LRPD answer to that clarification. The later Item-2 production contains many Flock Deconfliction Advisory emails. Each records an overlap-triggering search's agency, target plate, UTC time, and overlapping hot-list owners. Those emails prove that particular searches occurred and that LRPD retained the notifications. They do **not** identify the individual who ran the search, cover searches that triggered no hot-list overlap, or establish that LRPD possessed a complete console audit log, a Federal Searches CSV, a SharedNetworks CSV, or a monthly export. The tension is therefore not a proved conflict between a categorical Item-3 no-records certification and an existing formal audit log. It is an unresolved records-disposition problem created by ambiguous correspondence, partial search evidence, and unverified console custody. ## Statement A — the May 26 sentence was a narrow Item-2 finding The original request's Item 2 sought internal communications about several topics, including "audit-log review"; Item 3 separately sought usage and audit data. The request text appears at `Emails 1-24.pdf` pp. 1474-1475, not `Emails 36-63.pdf` as this page previously stated. Because Davis immediately described LRPD's large body of retained Flock email and scheduled "this portion" for production, the most natural narrow reading is that LRPD found no internal communications meeting Item 2's audit-log-review topic while continuing to process other Flock email. Joshua contemporaneously preserved this reading in his 2026-06-05 reply: one possibility was "a narrow no-records finding for one topic strand within Item 2" (Gmail thread `19e66c584957444d`, sent message `19e984151966cde2`). Under this reading, the sentence never disposed of Item 3 at all, so the Deconfliction Advisories do not contradict it. ## Statement B — the sentence could have been intended more broadly The phrase "audit-log review" is not a defined item label, and LRPD never answered Joshua's request to disambiguate it. A broader reading could encompass some or all of Item 3. If LRPD intended that broader reading, the later production raises a search-adequacy question because LRPD retained platform-generated emails reflecting a subset of searches ([[Flock Deconfliction Advisories and the LRPD Sharing Network]], `Emails 1-24.pdf` p. 562, "a Flock Safety hot list search was conducted by Little Rock AR PD"). Even on the broader reading, however, the present record does not prove the three named console exports existed as LRPD-held records. The Deconfliction Advisories are notification emails generated only when hot-list entries overlap; they are not formal Audit-view exports and do not identify the searching officer. Flock product newsletters describe a Network Audit filter, search-usage analytics, and masked audit fields, but they are vendor capability notices and expressly do not establish LRPD's configuration or administrative access ([[Flock Audit and Compliance Controls and Gaps]], `Emails 1-24.pdf` pp. 564, 645, 1330). Conway's production proves that another Flock tenant produced analogous exports, not that LRPD generated, retained, or controlled them. ## Arkansas FOIA boundary Ark. Code § 25-19-105(d)(2)(B)-(C), as reproduced in the official handbook, distinguishes copies of existing records in readily available or readily convertible formats from compiling information or creating a record. Section 25-19-109 permits discretionary summarizing, compiling, tailoring, or non-routine conversion and says custodians should agree when time and cost are relatively minimal. Vendor custody does not defeat FOIA when an established public record remains under the public entity's custodial responsibility, but that doctrine does not itself prove that a particular unsaved console export existed as a public record. (primary public record, [Arkansas Freedom of Information Act Handbook, 21st ed.](../../web%20archive/2026-07-20/healthy.arkansas.gov/arkansas-foia-handbook-21st-edition-2025.md), PDF pp. 13-14, 19, 23, 25; see [[Arkansas FOIA Electronic Records and Vendor Custody]]) This makes the operational distinction decisive. An existing saved CSV, report, database record, or notification email can be requested as an existing record. Requiring LRPD to run a new console query or generate a never-saved export may fall under § 25-19-109 instead. The present production does not establish which side of that line the requested Flock exports occupy for LRPD. ## What the record supports and does not support The record supports: - LRPD retained many Deconfliction Advisory emails, each documenting an overlap-triggering search at the agency/plate/time level ([[Flock Deconfliction Advisories and the LRPD Sharing Network]], `Emails 1-24.pdf` p. 562). - The advisories are incomplete by design and do not identify the individual searching officer. - Flock marketed audit, analytics, and network-audit capabilities to LRPD recipients ([[Flock Audit and Compliance Controls and Gaps]], `Emails 1-24.pdf` pp. 645, 1330). - The original request named Federal Searches, SharedNetworks, and monthly Audit-view exports (`Emails 1-24.pdf` pp. 1474-1475), and none appears in the production. - LRPD did not clearly state the disposition of Item 3 in the May 26 email and did not answer the June 5 clarification in the live thread. The record does not support: - saying LRPD certified that no Item-3 records existed; - calling the advisories a complete officer-level audit log; - saying they reveal which individual officer searched; - saying the named exports were necessarily generated, retained, or administratively controlled by LRPD; - saying a § 25-19-107 "appeal" exists inside LRPD. Section 25-19-107 supplies judicial remedies; the trashed draft's administrative-appeal phrasing was not a sound characterization. ## Why it matters The correction changes the next step. Re-sending the trashed draft would repeat an overclaim: it says the advisories prove the named exports are producible and treats § 25-19-107 as an agency appeal. A defensible successor, if Joshua chooses to file one, is a new, narrow portal request aimed first at **existing configuration, retention, administrative-access, and export-capability records**, plus any audit or network exports that were actually generated or saved during a defined period. That target tests custody and existence without assuming the answer. ## Resolution status **Bracketed as of 2026-07-21.** The former "open contradiction" framing is withdrawn. Decisive missing evidence is: (1) an unambiguous LRPD disposition for each Item-3 category; (2) records showing LRPD's Flock/Fusus administrator permissions and retention/export settings; and (3) whether any requested export already existed or would have required a new compilation. Until then, the lawful sufficiency of LRPD's response and the existence of the named LRPD records cannot be determined from this corpus. ## Discovery and correction history - 2026-06-17 — created during the Item-2 production ingest under the title "Item-3 No-Records vs Deconfliction Audit Trail." - 2026-07-21 — live Gmail review established that the May 26 sentence did not expressly identify Item 3 and that Joshua's June 5 clarification treated Items 3 and 4 as not directly addressed. Source re-review also established that the original request text is in `Emails 1-24.pdf` pp. 1474-1475 and that the advisories identify a searching **agency**, not a searching officer. The tension was renamed, narrowed, and moved from `open` to `bracketed`. ## Notes - Correspondence remains in Gmail and is cited by thread/message ID; it is not copied into `raw/`. - Plate values, phone numbers, signatures, and other sensitive fields are not reproduced. - No supplemental request or portal submission was made. Gmail draft `19f397f398014969` is in Trash; the user-supplied draft ID was not found. - Historical links using the superseded title resolve through [[T004 - Item-3 No-Records vs Deconfliction Audit Trail]], a correction redirect rather than a second tension page.