Repository navigation
Decide Washington Cascade Care Savings eligibility on the exact FPL ratio - #10314
Conversation
WAHBE's PY2026 and PY2027 Cascade Care Savings policies cover an enrollee who "has income up to 250% of the Federal Poverty Level" (Section 4(1)(c)). The gate compared the truncated aca_magi_fraction with 2.5, so every income from 250.00% to 250.99% passed. Test the exact ratio of nonnegative ACA MAGI to the prior-year guideline instead. Exactly 250% stays eligible, as before. Tests that supplied aca_magi_fraction now supply aca_magi against a prior-year guideline of $10,000, since the gate no longer reads the fraction; new cases use the real 2025 guideline at the edge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Divide the exact income ratio by aca_fpg, the poverty line the premium tax credit has used since #10041, and divide in float64 so a ratio just above 250% can't round down onto the limit. Washington's policy defines the Federal Poverty Level by 26 U.S.C. 36B(d)(3)(B). Pin aca_fpg in the test fixtures for the coverage year. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10314 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 24 18 -6
=========================================
- Hits 24 18 -6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
hua7450
left a comment
There was a problem hiding this comment.
Thanks, David. The Washington rule checks out: the WAHBE PY2026 and PY2027 policies say "Has income up to 250% of the Federal Poverty Level", define income and the poverty level by section 36B, and say nothing about truncation, so max_(aca_magi, 0) / aca_fpg <= 2.5 is right. The fpl_limit.yaml edit only changes the comment. Approving, with one test fix before merge.
Before merge
Two household-level cases still drive the gate through aca_magi_fraction. household_health_benefits.yaml Case 18 (lines 381-401, "single age 40 at 140% FPL") and healthcare_benefit_value.yaml Case 17 (lines 299-334, two tax units) set only aca_magi_fraction: 1.4, which the gate no longer reads. With no aca_magi, both now pass at $0 of income, so Case 18's comment is false. Please replace the fraction with aca_magi: 14_000 and aca_fpg: 10_000 in each tax unit, as you did in the other 52 cases; the expected values don't change.
Also, the Microsimulation job (run 44371406793) was cancelled at this head; please rerun it.
Optional
- References.
fpl_limit.yamllists the PY2026 policy twice (#page=11and#page=10) and doesn't cite PY2027, though the limit now carries into 2027. One entry per policy: PY2026 with the href on#page=10and a title ending"#page 10-11", and PY2027 with the href on#page=2and a title ending"#page 2-3". - Zero guard (see below), and Cases 3c and 3d cover the same scenario.
Series-wide (follow-up, not for this PR). The exact ratio max_(aca_magi, 0) / aca_fpg is now computed inline in each PR of this series, plus two California copies on main, and only 10312 guards a zero poverty line (territories, where aca_fpg is 0; the formula runs before the state mask, so a mixed simulation emits NumPy warnings, though outputs are unaffected). One guarded tax-unit variable for the untruncated ratio, read by every gate, would be a good follow-up PR once these merge.
Done: the fix, the YAML cases and the update onto current main. Pending: full impact run, Axiom parity line, GPT-6.1 Sol review.
Update onto current main (2026-11-18)
upstream/mainwith no conflicts. Max's commit stays in the history.aca_fpg, the poverty lineaca_magi_fractionand the federal credit have used since Keep a filer who can be claimed as a dependent out of the premium tax credit family, and apply each state premium program's rule #10041, and divides in float64, followingca_premium_subsidy_eligible. The PY2027 policy, Section 3(9) defines the Federal Poverty Level by 26 U.S.C. 36B(d)(3)(B).tax_unit_fpgfor the prior year now pinaca_fpg: 10_000for the coverage year. No expected value changed. The cases Keep a filer who can be claimed as a dependent out of the premium tax credit family, and apply each state premium program's rule #10041 added, where the tax family can be smaller than the tax unit, stay on the same side of 250%.pa-10314-a), all passing: the five Cascade Care Savings YAML files (82 cases),healthcare_benefit_value.yaml(22),household_health_benefits.yaml(19) andtest_claimable_filer_ptc_invariants.py(14).healthcare_benefit_value.yamland Case 18 ofhousehold_health_benefits.yamlstill supplyaca_magi_fraction: 1.4, which this gate no longer reads. They pass withaca_magiat $0, so they check that the amount flows through, not the income test.Bug
wa_cascade_care_savings_eligiblecompared the truncatedaca_magi_fraction(np.floor(100 * magi / fpg) / 100) with<= 2.5. Truncation maps every income from 250.00% to 250.99% of the poverty line to 2.50, so all of them passed. WAHBE's PY2026 Cascade Care Savings Policy, Section 4(1)(c) makes an individual an eligible enrollee who "Has income up to 250% of the Federal Poverty Level"; the PY2027 policy keeps the same words. RCW 43.71.110(4)(a)(ii) leaves the threshold to the appropriation or the exchange. No source prescribes truncating the percentage."Up to 250%" leaves exactly 250% open to either reading. The model already treats it as inclusive and this PR keeps that. Income above 250% is not "up to 250%" on any reading, so the truncation sliver is unambiguous.
Executed on
main(645fcd3; the file is unchanged at 740e1eb), single filer in Washington, 2026, 2025 one-person guideline $15,650, Group 1 member:aca_magi_fractionThe end-to-end run (wages only, nothing supplied) gave the same results, since the federal credit continues to 400%.
Fix
Decide eligibility on the exact ratio
max(aca_magi, 0) / aca_fpg, the pattern of #10305. Nothing else in Cascade Care Savings reads the fraction. Thefpl_limitcomment now says the limit applies to the exact ratio.Invariants
For every input, with the program in effect and a Group 1, Group 2 or Group 3 member:
r <= 2.5,r = max(MAGI, 0) / aca_fpg.rin (2.50, 2.51), sowa_cascade_care_savingscan only fall. Deduced:floor(100r)/100 <= 2.5holds exactly whenr < 2.51.No Hypothesis test is added: the gate is one comparison on a ratio, and the YAML cases hit the limit, 0.003 and 0.994 points above it. The repo's test-design rules keep such cases in YAML.
Tests
wa_cascade_care_savings_eligible.yaml,wa_cascade_care_savings.yamlandintegration.yamlthat suppliedaca_magi_fractionnow supplyaca_magiagainst anaca_fpgof $10,000, so each still drives the gate (the gate no longer reads the fraction; nothing else in these files did). The derived fraction outputs are unchanged.pa-10314-aon the updated branch: the Cascade Care Savings YAML folder, 82 passed.Run before this update, on the earlier
tax_unit_fpgdenominator, and not repeated since:main's gate fails exactly the two new above-limit cases.mainthe same draws give 58 mismatches, all in the truncation sliver.Impact
Pending: full-file microsimulation via the US hub impact queue, 2026 and 2027.
Coordination
#10041 merged on 2026-11-13, and this gate's exact ratio now uses its
aca_fpgdenominator. Part of theaca_magi_fractionaudit (table: #10329) begun with #10305; federal edge in #10312.axiom: pending
🤖 Generated with Claude Code