fix(erp): validate readouts against existing state evidence - #635
Merged
zzylol merged 1 commit intoSep 11, 2026
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.
A shared UnivMon state can have valid measured evidence for several readouts even when a smaller configuration is cheaper for one of them. Previously, validating an installed state re-ran cheapest-configuration selection and rejected the state whenever that cheaper configuration differed.
This change filters evidence by the actual state parameters before bounded shape matching. New-state sizing still chooses among eligible configurations; existing-state readout validation uses only evidence for that state. A missing metric cannot borrow a bound from a cheaper sibling.
Verification: the focused existing-state regression passed, and independent source review passed. The regression uses synthetic evidence to check selection behavior; it is not an accuracy calibration or performance measurement. Full CI is pending. Stacked on #619.