# T041 - Jacksonville Tenant Audit vs Network Audit Scope Jacksonville produced two same-period Flock audit exports whose scale and organization fields differ by orders of magnitude. The smaller file is clearly tenant-attributed; the larger file is multi-organization. The absence of a data dictionary prevents attribution of the larger rows to Jacksonville personnel, devices, data, or results. ## Statement A `6_29_2026-7_29_2026-Jacksonville AR PD-Audit.csv` contains 317 rows, and every row states `"Jacksonville AR PD"` in `Org Name`. Its fields include `"Total Networks Searched"`, `"Search Time"`, and `"Search Type"`; the values span 1 to 6,009 networks searched ([[Jacksonville Flock Search Network and Event Audit Exports]], header and full-file parse). ## Statement B `6_29_2026-7_29_2026-Jacksonville AR PD-Network-Audit.csv` contains 990,877 rows and 3,135 distinct `Org Name` values over the same general 2026-06-29 through 2026-07-29 period. The production supplies no schema note defining whether these are activity across searched networks, activity visible to Jacksonville, activity against Jacksonville data, or a broader platform export (same source, header and full-file parse). ## Why it matters Treating every network-audit row as a Jacksonville search would falsely attribute other organizations' activity to Jacksonville. Treating every row as a search against Jacksonville data would likewise convert scope ambiguity into a data-access fact. The distinction is load-bearing for cross-jurisdiction activity counts and any synthesis connecting configured topology to actual searches. ## Resolution status **Open.** Resolution requires the export data dictionary, tenant/filter parameters, vendor-generated report description, and an agency explanation of what inclusion in the network-audit file means. ## Discovery Discovered during the 2026-07-30 ingest of Jacksonville's supplemental release. ## Notes The tension does not negate the 317 tenant-audit rows or the 1,205-row SharedNetworks topology. It keeps tenant activity, multi-organization activity, and configured relationships separate.