The first program tranche: 100,000 REGEN from the community pool, paid out only against accepted stewardship hours

Original Proposal Text

The second half of the program fund, and it can be voted on its own. The standing stream routes a share of community-pool inflow; this moves one bounded amount out of the pool BALANCE into a payout account that pays only against work that is settled on a public board and accepted by a human, at a rate this proposal states, and returns what it does not spend. THE NUMBERS, READ AT BUILD TIME: the pool holds 5,035,750 REGEN. The rate is 10,000 REGEN per accepted hour of verified stewardship work, the unit proposal #75 added to this registry as VSH. The board has 0 accepted hours settled to date across 0 settlements, and the program asks for a forward budget of 10 hours on top of that. 10 hours at 10,000 REGEN is 100,000 REGEN, which is inside the stated ceiling of 5.0% of the balance, so the ask is: 100,000 REGEN, 1.99% of the pool, funding up to 10 accepted hours. THE RATE IS A STARTING FIGURE AND I WILL NOT DRESS IT UP: the board has settled no hours-denominated work yet, so there is no settlement history to derive a rate from. 10,000 REGEN per hour is a stated governance number, chosen to be legible and conservative against a pool this size, and it changes only by a later vote. Nobody is paid a REGEN of this until an hour is worked, proven, and accepted. THE RECEIPT SHAPE: every payment out of the payout account carries, publicly and before the payment counts, the work packet it settles, the place it was done at, the hours claimed by the worker and accepted by the human who accepted them, the settlement transaction, and the content hash of the proof anchored on Regen's own x/data module. A payment without that record does not exist and cannot be counted against this tranche. The running total is published beside the pool balance, so the spend can be audited against the chain rather than against a report from the party spending it. RETURN OF UNSPENT: whatever is not paid against accepted hours within 365 days returns to the community pool with a /cosmos.protocolpool.v1.MsgFundCommunityPool from the payout account. The tranche is custody, not income: it buys nothing, it pre-pays nobody, and it is not a grant. MECHANICS: one standard /cosmos.protocolpool.v1.MsgCommunityPoolSpend, effective the moment it passes, no chain upgrade, no new module. The message type is the whole risk on this chain and it is deliberate: proposal #63 won 43,683,675 REGEN to 0 and still ended FAILED at execution, because it carried x/distribution's identically-named MsgCommunityPoolSpend while the balance sits in the x/protocolpool module account. This carries the protocolpool one, the module the 5,035,750 REGEN is actually in, and the shape was run against this chain in check mode before it was proposed. The one thing a passing vote cannot guarantee is a balance at execution time, so if the pool has fallen below the ask when this executes, the spend fails and nothing moves. WHAT THIS IS NOT: it is not a burn. The steward closed proposal #68 because it spent the pool on a burn; spending the pool on verified regeneration is the opposite of that, and this proposal is the first instance of it. DISCLOSURE: the proposer is the current Regen Tokenomics working-group steward, and the payout account regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j is the proposer's own address, the same identity that signed proposals #64, #66, #67, #72, #73, #74 and #75 from this chain. No new wallet was created for this. Stated plainly so the network can weigh it on the merits. CONFIRM WITHOUT TRUSTING ME: the pool balance is at /cosmos/protocolpool/v1/community_pool; the credit type is at /regen/ecocredit/v1/credit-types; the board's settled work and its accepted hours are at https://vealth.net/labor/settled. More details: https://vealth.net/regen-network/roadmap