Guard PUF support clone top tail#166
Merged
Merged
Conversation
61df773 to
f7104fd
Compare
This was referenced Jun 2, 2026
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.
Summary
Why
The combined #163/#164 artifact regressed against latest-local eCPS because one arbitrary MD PUF-support clone row moved from about $37M rough income to about $109M. Since PUF has no state geography, that single state-inherited row dominated the Maryland AGI top-tail target after calibration. This is a temporary production guard until MP has state-aware top-tail support records.
Checks
Review Fix
An independent read-only review found the first version double-counted
capital_gainswith LTCG/STCG and dividend totals with dividend leaves. The branch now computes rough AGI on a canonical nonredundant basis and has a regression test proving below-cap rows with both totals and leaves are left unchanged.Follow-up
If this merges, rebuild the CPS-spine Gate-1 artifact and rerun the primary latest-local eCPS sound comparison. The guard should remove the #163/#164 state AGI blow-up; SNAP remains the next separate loss lane.