# T001 — Default-On Sharing: Policy Failure or Product Design The Conway PD corpus documents 1,384 organization rows with at least one configured sharing direction as of 2025-12-17, 94% of them out-of-state ([[SharedNetworks 2025-12-17 Snapshot]], `SharedNetworks_2025_December_17.csv`, full-file parse). The production surfaces no relationship-specific MOU or approval history. The tension concerns *how this topology came to exist* and which records governed it. *Erratum, 2026-07-30: D001 previously resolved this tension in favor of a default-on product mechanism. The Tier-1 Flock email used in the dialectic calls National Lookup a network of “participating, opt-in agencies” and lists administrator choices including “Don't share at all” (`Flock Safety Understanding Sharing Search and Audits in the Flock LPR System.msg`, body). The export proves the resulting configuration, not its initial default or authorship. The D001 verdict is no longer operative and this tension is reopened.* ## Statement A **The topology may reflect Conway-side governance choices or omissions, because Flock says agency administrators control whether and how their data is shared. The present production does not identify the decision-maker or approval rule.** The governing local rule is CPD Policy 800-32, R3 (1/18/2023), approved as "Chief of Police" by William Tapley ([[CPD Policy 800-32 — License Plate Reader Vehicle Operations]]). Section D, paragraph 4 establishes the standard: > "**Data sharing** with other LE agencies 'if evidence of an offense is indicated.'" This is a per-event standard: it asks, of a specific sharing act, whether an offense is in view. The policy text predates Flock's cloud architecture (drafted around physical cameras storing data on department servers — the policy text says "stored on the department's computer servers") but it remains in force. Conway PD has the policy authority to apply the "evidence of an offense" standard to platform-level relationship configuration; nothing in the policy says that test attaches only to per-event sharing decisions and not to the upstream act of configuring a standing relationship that enables thousands of subsequent queries. [[Andrew Burningham]] is documented as a Conway Flock administrator and appears extensively in the email production, but neither fact attributes the 1,384 relationship rows to him. The corpus also does not show whether CPD Policy 800-32's “evidence of an offense” clause was applied, rejected as inapplicable, supplemented by another rule, or never considered for standing relationships. Flock's August 2025 explainer says administrators have “full control over whether and how” the agency shares and adds, “you are responsible for knowing your agency's laws and policies” ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]], same `.msg`, body). That supports an agency-control inquiry. It does not prove which side initiated each relationship or that Conway affirmatively chose every row. ## Statement B **The topology may reflect product architecture that makes broad standing relationships scalable, while local policy written for discrete sharing events may not describe the platform configuration process. The record does not establish the interface default.** The Aug 2025 Flock explainer from SVP Chris Colwell to Burningham lays out the sharing model in the vendor's own words ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]): > "Configurable sharing options: Share with agencies in specific states only · Share with agencies with similar laws (for example, regarding immigration enforcement and data) · Share within your state only or within a certain distance · Share 1:1 (only with specific agencies) · Don't share at all." The same email first describes National Lookup as available among “participating, opt-in agencies.” The list establishes available choices, not which choice is preselected or how many actions each choice requires. Cross-state restrictions document Flock's capacity to enforce legal limits in the product: the email says out-of-state sharing is disabled in Virginia and certain purposes are disabled in Illinois (same `.msg`, body). It does not state Arkansas's tenant default or prove that the absence of a statewide product restriction automatically enables a relationship. The 471 incoming-only and 427 outgoing-only rows show asymmetry, but the field directions do not identify who acted, whether approval was unilateral or mutual, or what default preceded the row. Wright-Patterson appears in the relationship export but not as a searching-organization label in the 31-calendar-date federal-activity export ([[SharedNetworks 2025-12-17 Snapshot]]; [[Federal Searches CSV]]). Because the activity file does not identify searched networks, that absence is not proof that no query reached the relationship or evidence of how the configuration arose. The records show standing relationships and later activity, but do not establish the exact configuration workflow, duration, or review cadence. Whether § D.4 applies to a standing permission is a policy-interpretation question the production does not answer. ## Why it matters The two readings point at different evidence and locate the remedy in different places: - **If Statement A is correct (policy failure):** the remedy is documentation. Follow-on FOIA targets Conway's network-admin training records, internal sharing-configuration approvals, any documents showing how the agency reconciles CPD 800-32 with platform-level configuration. The remedy this reading implies is a policy-update mandate: agencies applying per-event evidentiary standards to platform-level configuration, not only to per-event acts. The vendor is policy-neutral; the agency is the regulated party. - **If Statement B is correct (product design):** the remedy is structural. Follow-on FOIA targets Flock's UI default-state documentation, the configuration screens themselves (whether the agency was opted into national sharing on day-1 by default), any vendor onboarding materials that recommend the default-on posture. The remedy this reading implies is product-design regulation: sharing relationships requiring positive per-relationship per-purpose justification at the product level, mirroring Virginia's structural restriction. The vendor's design is the regulated object. The evidence needed to distinguish these readings determines whether the next inquiry should focus on Conway's approval and policy records, Flock's tenant initialization and relationship-history records, or both. The present record does not support a “resting state is on” finding. ## Resolution status **`open` as of 2026-07-30.** [[D001 Synthesis]] is preserved as a completed isolated-phase artifact, but its mechanism verdict depended on an unsupported default-on inference and is superseded by the erratum above. Resolution requires tenant initialization/default documentation, relationship-level history and actor fields, the approval workflow, and records showing how Conway applied its policy to standing relationships. ## Discovery Surfaced 2026-05-23 during the Dialectical Wiki Pipeline application survey. The parent synthesis asked who configured each relationship and whether the platform supplied a starting state. The 2026-07-30 correction removed the unsupported attribution to a likely configuring administrator; the configuration events remain undocumented. ## Notes - This was the first tension tested through the wiki's isolated three-phase dialectic method. The completed phases are collected in [[D001 Thesis]], [[D001 Antithesis]], and [[D001 Synthesis]]; their original verdict is preserved but no longer operative. - The two statements share the same Tier-1 evidentiary base (CPD 800-32 policy text, Flock Aug 2025 explainer, SharedNetworks 2025-12-17 export) — they differ in *what mechanism the evidence implies*, not in *what the evidence says*. This is a framing tension on a shared corpus, not an evidentiary tension on contested facts. - Neither reading is alleged to establish unlawful conduct. The tension is evidentiary and structural: it asks what created and governed the documented configuration, while leaving statutory application to a record-specific legal analysis.