# D002 — Antithesis: The Chief Cannot Promulgate a Directive Against a Structural Authorship He Does Not Hold ## Counterclaim The structural remedy for the platform-era data-sharing topology operates at the level of vendor product design and state statute, not at the level of an internal department directive — and the vendor's own description of the architecture makes the point against the agency-directive remedy directly. Flock SVP Chris Colwell, writing officially to Conway PD in August 2025, locates the dispositive structural restrictions in Virginia's and Illinois's *statutes* enforced through the *product*, not in any chief's internal rule. The 471 inbound-only relationships in the December 2025 SharedNetworks snapshot are configuration outcomes whose *authorship* is distributed across 1,384 independent counterparty administrators and a default-on platform interface — not authored by any Conway-side actor on whom an internal directive could operate. Demanding the Conway chief draft a successor directive demands what cannot be done coherently; the absence is not a culpable abdication but the institutional recognition that the remedy lives elsewhere. ## Attack on the thesis The thesis's central architectural mistake is on display in its very title — "*The Successor Directive Conway PD's Chief Has Not Issued Is the Agency's Act*." The mistake is to treat "internal-directive authority" and "structural-configuration authority" as the same thing because they share the word "authority." They do not. The thesis's `## Claim` paragraph asserts the chief's authority "produced [[CPD Policy 800-32 — License Plate Reader Vehicle Operations]] in 2013 and its R3 revision in 2023 under [[William Tapley]]'s signature alone" and reasons from there that the same authority can reach the platform-era configuration moment. This is a category error. The signature on the 2023 R3 page is dispositive proof of one thing only: that a Conway chief can unilaterally promulgate a written internal rule about *Conway personnel's conduct*. It is not proof — and it cannot be proof — that any such rule can reach the configuration outcomes of a multi-party platform whose default-on architecture and 1,384 counterparty administrators are entirely external to the Conway chain of command. The thesis treats institutional capacity as homogenous; the evidence shows it is not. The thesis's `## Argument` paragraph claiming the chief's unilateral authority is "institutionally established" and "dispositive" is exactly where the argument collapses on the verbatim text it relies upon. The thesis insists that "the chief did not need vendor cooperation: an internal directive governs Conway personnel's configuration practice in the Flock administrative interface — what relationships [[Lt. Andrew Burningham]] (the Flock administrator…) and any successor administrator turn on, turn off, or escalate to the chief for approval — not what Flock's interface itself permits in the abstract." This concession is fatal to the thesis. The thesis has admitted, in its own words, that an internal directive can govern only "what Conway personnel turn on, turn off, or escalate" — i.e., the affirmative-Conway-action vector. But the SharedNetworks snapshot shows that the 471 inbound-only relationships are precisely *not* relationships Conway personnel turned on. They are relationships *counterparty* personnel turned on, sharing *into* Conway from the counterparty's side of the platform, on a default-on baseline that does not require Conway approval. A directive that "governs what Conway personnel turn on, turn off, or escalate" has, by the thesis's own framing, *no purchase* on the 471 inbound-only configurations. The thesis has built its own argument's defeat into the argument. The thesis's `## Argument` paragraph claiming "the doctrinal mismatch was operationally visible from the first weeks of Conway's Flock deployment — and the office that had drafted 800-32's elaborate evidentiary regime in the first place had every demonstrated tool to draft a successor regime for the standing-relationship moment instead" is doctrinally bankrupt because §D.4 is the proof of the limit, not the proof of the capacity. The §D.4 verbatim text — "Data sharing with other LE agencies 'if evidence of an offense is indicated'" ([[CPD Policy 800-32 — License Plate Reader Vehicle Operations]] §D.4) — is the most elaborate sharing-directive any Arkansas municipal LPR policy in the corpus produces. It carries the unmistakable signature of an agency that *tried* to govern sharing through an internal directive: it specifies a standard ("evidence of an offense"), it designates the counterparty class ("other LE agencies"), and it implies a per-event review structure (the standard is evidentiary, which requires events to which evidence attaches). And, as the prior dialectical record settles, it cannot reach the configuration moment. The directive-level remedy was attempted, in its strongest available form, and the per-event evidentiary grammar was found to be doctrinally prior to the events the standard purports to regulate. Any successor directive a Conway chief might draft inherits the same grammatical problem in a more general form: it would still be *an agency rule about agency conduct* applied to *a joint act between the agency administrator and a vendor-designed default-on platform configured by 1,384 independent counterparty administrators*. The thesis demanding "more of the same instrument" mistakes a structural exhaustion for a personnel-attribution gap. The thesis's `## Argument` paragraph asserting "the chief did not need legislative reform: an internal directive is an internal rule of practice within a single municipal law-enforcement agency, not a state law" is precisely where the Virginia/Illinois evidence catches the thesis in flagrant overreach. The thesis writes as though "legislative reform" and "internal directive" are *alternative paths to the same destination*. The Flock SVP's August 2025 official explainer to Conway PD says exactly the opposite. The verbatim text, from [[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]: "**In some states, sharing is automatically restricted as required by law, and searches with search terms that indicate a purpose prohibited by law have been disabled in our product. For example, in Virginia, out-of-state sharing is disabled and in Illinois, accessing data for certain purposes is not allowed. However, you are responsible for knowing your agency's laws and policies.**" Read what this actually says. The restriction is "*as required by law*" — i.e., by statute, not by chief's directive. The implementation is "*disabled in our product*" — i.e., at the product surface, not at the agency level. The Virginia example is not "every Virginia police chief has issued an internal directive forbidding out-of-state sharing." It is "Virginia statute prohibits out-of-state sharing, and Flock's product enforces the prohibition by disabling the configuration option." The Illinois example is parallel. The two structural-restriction precedents the platform vendor itself cites locate the operative authority at the statutory-and-product level — and the thesis's claim that the chief had a directive-level alternative to this is contradicted by the vendor's own description of how structural restriction actually works in jurisdictions where it works. The thesis's `## Argument` paragraph leaning on "across that window the investigation has assembled four document productions covering the policy-and-personnel side of the agency on multiple cuts… In all of it, no successor internal directive amending, supplementing, or replacing 800-32 surfaces" mistakes a corpus-wide absence for a culpable abdication when the same absence is more parsimoniously explained as the chief's *recognition* that no such directive could coherently operate. The thesis treats the absence as a finding requiring positive justification — as though the default expectation is "a directive should have been written." But that default expectation is exactly what is contested. If the structural-grammar problem is general (and §D.4's failure shows it is), then the rational institutional response from a chief who reads §D.4's text honestly and understands what the platform deployment does is: "There is no internal rule I can write that will govern the configuration moment, because the configuration moment is jointly authored by the platform and 1,384 counterparties, none of which my directive can reach. The remedy needed is structural, and it lives at the statute-and-product level the vendor's own SVP described as the operative architecture." That is not abdication. That is competent institutional reading of the text and the architecture. The thesis's `## Argument` paragraph on organizational structure — "the chief's office sits at the apex of an organizational structure that already contains, on its own staff side, the institutional functions a configuration-governance directive would naturally consult: O.P.R. for review, the F.O.I.A. function for disclosure-posture analysis, and the operational Flock administrator three steps down the line" — does not establish what the thesis needs it to establish. It establishes that Conway PD has standard police-department staff functions reporting to the chief. It does not establish, and cannot establish, that any of those staff functions has authority over Flock's product defaults, over the 1,384 counterparty administrators' configuration decisions, or over the platform's default-on architecture. The organizational-chart move is the rhetorical sleight of the entire thesis in microcosm: building an inventory of *internal* institutional capacity, then pivoting to the *external* configuration problem as if the inventory addresses it. It does not. The Office of Professional Responsibility cannot review what a Texas police department's Flock administrator toggled. The FOIA function cannot analyze the disclosure posture of an Air Force base's inbound-only sharing relationship. The chief's chain of command cannot supervise what counterparty administrators do on their side of the platform. The thesis's organizational argument confirms only that the chief is institutionally well-positioned to write rules about *Conway* — which has never been the contested point. ## Independent argument for the counterclaim The positive case for Statement B rests on three structural facts, each anchored in the corpus, that the thesis cannot accommodate. First, the platform vendor's own official description of where structural restriction lives places the operative authority at the statutory-and-product level, not the agency-directive level. The verbatim Flock SVP text, from Chris Colwell's August 2025 explainer to [[Lt. Andrew Burningham]]: "**In some states, sharing is automatically restricted as required by law, and searches with search terms that indicate a purpose prohibited by law have been disabled in our product. For example, in Virginia, out-of-state sharing is disabled and in Illinois, accessing data for certain purposes is not allowed. However, you are responsible for knowing your agency's laws and policies.**" ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]). This is the vendor's contemporaneous description of how the platform actually operates. Read carefully, it tells us two definitive things about the architecture. (1) Where structural restriction governs — Virginia, Illinois — it does so because *statute* mandates the *product* be configured a particular way, and the *product* enforces the configuration as a disabled option. The agency-level rule is downstream of the product-level enforcement; it is not an alternative path. (2) Where structural restriction does *not* govern — the trailing clause, "you are responsible for knowing your agency's laws and policies" — the vendor's framing is "the agency carries the burden because no structural mechanism applies." The Arkansas posture is the latter. The remedy contemplated in the explainer is not "Conway issues an internal directive"; it is "the state's law and the product's enforcement coincide." That is structural reform, not chief-level rule-making. Second, §D.4 is the doctrinal proof that the directive-level instrument cannot perform the function — and the proof is general, not specific to Conway. The verbatim text, "Data sharing with other LE agencies 'if evidence of an offense is indicated'" ([[CPD Policy 800-32 — License Plate Reader Vehicle Operations]] §D.4), is *the* attempt to govern sharing through an internal rule. It specifies a sharing standard, designates the counterparty class, and implies a per-event evidentiary trigger. And it cannot reach the configuration moment because the per-event evidentiary grammar is logically prior to the events the standard purports to regulate — the events arise *from* the configured-toggle state, not *under* it. Any successor directive a Conway chief might draft inherits the same general problem: it would be *an agency rule about agency conduct* governing *a joint act between an agency administrator and a vendor-designed default-on platform*. The grammar problem is not "the per-event language is wrong; pick a different language." The grammar problem is "a rule whose subject is the agency cannot govern an act whose authorship is partially distributed elsewhere." A successor that said "no Conway personnel shall affirmatively enable a sharing relationship without supervisor sign-off" could govern affirmative-Conway-side toggles — but it could not govern the 471 inbound-only relationships, which are not Conway-side toggles in the first place. A successor that tried to address the inbound-only problem would have to bind counterparty administrators across 38+ states, two federal agencies, a tribal LE, and an NGO — which an internal Conway directive lacks any authority to do. The directive instrument has a fixed reach, and the configuration problem exceeds it. Third, the asymmetric configuration pattern in the December 2025 snapshot is the empirical evidence that the configuration's authorship is structurally distributed and not unilaterally Conway's. [[SharedNetworks 2025-12-17 Snapshot]] enumerates 1,384 total organizations — 486 bidirectional, 471 inbound-only, 427 outbound-only. The 471 inbound-only relationships are organizations sharing *into* Conway from the counterparty's side. The page itself notes the asymmetric pattern is "unexplained in the corpus" and "reflects either deliberate Conway-side configuration or default-on settings the configuring administrator did not actively curate." What it cannot reflect is unilateral Conway authorship. By definition, an inbound-only relationship requires a counterparty-side action (the counterparty toggled "share with Conway") and either a Conway non-action (Conway did not affirmatively configure the relationship and inherited it through a default-on mechanism) or a counterparty unilateral act paired with Conway's passive acceptance. In either case, the directive remedy the thesis demands has no actor on whom to bite. The chief cannot order an Ohio Air Force base, a Texas county sheriff, or a Georgia Home Depot administrator not to toggle sharing-to-Conway on. The chief cannot, by internal directive, retroactively undo the default-on baseline that caused inbound-only relationships to populate without Conway's affirmative consent. The 471 inbound-only number is the structural shape of an authorship problem that no agency-internal rule can reach. These three structural facts together establish the counterclaim. The vendor's own description places the operative authority at the statute-and-product level (the Virginia/Illinois precedent). The §D.4 verbatim text proves the directive instrument is doctrinally exhausted in its strongest form. And the 471 inbound-only configurations are empirical evidence that the configuration's authorship is distributed across counterparties an internal directive cannot reach. The thesis demands the chief act on a problem whose causation lies entirely outside his command authority and whose structural remedy lies entirely outside the directive instrument. The absence of a successor directive is therefore not a culpable abdication but a competent institutional reading: the chief has not issued the directive the thesis demands because no such directive can do the work the thesis claims it would do. The remedy operates at the product surface (vendor-side enforcement of statutory restriction, the Virginia model) and at the statutory level (Arkansas General Assembly legislation mandating product-level restriction). The chief's office is not where the demanded action could meaningfully occur. The omission is not culpable because the action is structurally vain. ## Evidence - **The Flock SVP's verbatim description of structural restriction locates the operative authority at the statutory-and-product level:** "**In some states, sharing is automatically restricted as required by law, and searches with search terms that indicate a purpose prohibited by law have been disabled in our product. For example, in Virginia, out-of-state sharing is disabled and in Illinois, accessing data for certain purposes is not allowed. However, you are responsible for knowing your agency's laws and policies.**" Chris Colwell, SVP of Customer Experience, Flock Safety, in the August 20, 2025 vendor-explainer to [[Lt. Andrew Burningham]] ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]]). - **§D.4's per-event evidentiary grammar is verbatim — and is the corpus's strongest attempt at directive-level sharing governance:** "Data sharing with other LE agencies 'if evidence of an offense is indicated'" ([[CPD Policy 800-32 — License Plate Reader Vehicle Operations]] §D.4). The same concept page notes: "Section D.4 limits sharing to 'evidence of an offense is indicated' but does not address pre-configured platform sharing relationships that enable thousands of one-off queries by counterparty officers. The policy contemplates a per-event sharing decision; Flock's product enables a per-relationship sharing configuration." - **The 471 inbound-only configurations are structurally not unilateral Conway authorship:** the SharedNetworks export of 2025-12-17 lists 1,384 total organizations — 486 bidirectional, 471 inbound-only, 427 outbound-only ([[SharedNetworks 2025-12-17 Snapshot]]). The page itself notes: "Asymmetric sharing posture… Conway has 427 outbound-only relationships (Conway shares, receives nothing back) and 471 inbound-only (Conway receives, shares nothing back). The asymmetry is unexplained in the corpus — it reflects either deliberate Conway-side configuration or default-on settings the configuring administrator did not actively curate." - **The platform topology's external counterparties exceed any Conway-internal directive's authority:** the snapshot enumerates relationships across 38+ states plus DC, federal entities including `[Federal] Wright Patterson OH Air Force Base` and `[Federal] US Postal Inspection Service`, tribal LE (`Quapaw Nation OK Marshals Service`), a national NGO (NCMEC), and private parties (six Arkansas Home Depot stores) — 94% of relationships out-of-state ([[SharedNetworks 2025-12-17 Snapshot]]). - **The Virginia/Illinois product-enforced restrictions are the structural precedent, not agency-level directives:** the same Flock SVP explainer establishes that in jurisdictions where structural restriction governs sharing, it operates by statute-mandated product configuration disabling specific options — not by chief-level directives in each agency ([[Audit-System Policy Emails (Aug 2025 - Apr 2026)]], 2025-08-20 Colwell explainer). - **The thesis's own framing concedes the directive instrument's reach is internal:** [[D002 Thesis]] § *Argument* states that an internal directive "governs Conway personnel's configuration practice in the Flock administrative interface — what relationships [[Lt. Andrew Burningham]]… and any successor administrator turn on, turn off, or escalate to the chief for approval — not what Flock's interface itself permits in the abstract." By this framing, the directive cannot reach the 471 inbound-only configurations, which are not relationships Conway personnel turn on.