Confirm solver picks at interval precision instead of flat spread - #40
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Problem
The fresh-input solver gate added in #38 fails any selected plan whose 9-round max/min spread exceeds the 5% margin and aborts regeneration with "recapture on a quieter GPU". Two independent idle-box captures on the RTX 5090 (one with the desktop compositor's GPU client alive, one with it killed) reproduce the same failing cells with matching medians (±1%) and matching spreads:
The spread is a property of those plans, not of the environment, so the flat gate can reject every capture the machine will ever produce — it aborted Capture B on two consecutive nights.
Change
require_stable_solver_picksbecomesconfirm_solver_picks: stability is judged on the decision, not the spread.Docs (TUNING.md, tuning.rst) updated to match.
Validation
test_tuning_tools.pyreworked: demotion, guaranteed-win survival, noisy-native-is-not-fatal;test_tune_isolation.pyunchanged).Receipt
Test sources changed, so the receipt
verifyjob stays red until a fresh signed all-shard receipt is attested. The GPU is inside a protected final-capture timing window today; I will re-attest on this branch as soon as it frees, before merge.🤖 Generated with Claude Code