Align validator budget caps with approved 100k/25k pilot - #190
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The maintainer accepted a revised seven-day budget of 100,000 AIPG total and 25,000 per independent operator after reviewing the indicative dollar value. This replaces, rather than adds to, the earlier 4,000/1,000 approval. Updates the explicit allocator validation ceilings; does not set defaults, reprice frozen contracts, activate a campaign or send funds. Retains operator review, exact release, consent and duplicate-payment protections. Tests cover maximum-sized allocations, one atomic unit above each bound, value conservation, replay deduplication, unchanged old terms and real database finalization. Local verification: 65 passed on disposable PostgreSQL 14.19/Python 3.13; scratch database removed. New acceptance tests failed against the old ceilings first. CI must still qualify production Python/Postgres versions. Diff-check and staged Gitleaks passed. No production mutation.