Skip to content

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

Merged
DTrim99 merged 53 commits into
mainfrom
claimable-filer-ptc
Nov 13, 2026
Merged

DTrim99 merged 53 commits into
mainfrom
claimable-filer-ptc

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Someone another taxpayer can claim as a dependent gets no premium tax credit, and a joint return where another taxpayer can claim one spouse computes the credit for the other spouse alone. The model applied neither rule: is_aca_ptc_eligible ignored whether another taxpayer could claim a filer, and aca_ptc, the benchmark premium, the poverty line, household income and the premium cap all counted the whole tax unit.

The PR reads claimable_as_dependent_on_another_return (from #10024: a deduction for the person is allowable to another taxpayer, whether or not that taxpayer claims it). Form 1040 (2025) instructions, line 12a, p.33 has the box checked "If you or your spouse ... can be claimed as a dependent on someone else's return", with no refund-only carve-out, and Form 8962 line 1 keys on that box. The return still claims its dependents when the would-be claimant meets the refund-only filing exception (dependent_claimant_filing_exception; Form 1040 dependents worksheet, p.18; Publication 501's Dependent Taxpayer Test).

  • IRC 36B(c)(1)(D), "Denial of credit to dependents": "No credit shall be allowed under this section to any individual with respect to whom a deduction under section 151 is allowable to another taxpayer". 26 CFR 1.36B-2(b)(3) excludes such an individual from applicable taxpayers.
  • 26 CFR 1.36B-1(d)(2) (taxable years ending on or after 2020-12-31) defines the family as "the taxpayer, including both spouses in the case of a joint return, except for individuals who qualify as a dependent of another taxpayer under section 152", plus the dependents the taxpayer properly claims. IRC 152(b)(1) and Publication 501, p.11: "If you are filing a joint return and your spouse can be claimed as a dependent by another taxpayer, you and your spouse can't claim any dependents on your joint return."
  • Form 8962 instructions (2025), line 1, p.8: "if you are filing jointly and you checked the 'Someone can claim your spouse as a dependent' box on your tax return, you or your spouse is not included in the tax family size calculation". The 2021-2024 editions say the same (p.6 to p.7).
  • 26 CFR 1.36B-3(b)(2), (f)(1): the benchmark is the second-lowest-cost silver plan "offered to the taxpayer's coverage family", the family members enrolled that month.

From #10024, is_aca_tax_family_member reads claimable_as_dependent_on_another_return and is_dependent_elsewhere_without_filing_exception (claimable, and the would-be claimant doesn't meet the refund-only exception). No formula in this PR reads #10024's tax-unit helpers.

Federal change

Variable Rule now
is_aca_tax_family_member (new, person), is_aca_filer (new, person) A filer no other taxpayer can claim; a dependent on the return when it has an applicable taxpayer and no filer is claimable outside the refund-only exception. A return where another taxpayer can claim every filer has no family (36B(c)(1)(D)). is_aca_filer uses supplied or inferred head/spouse roles and completes an incomplete joint-filer set without an adult-age cutoff. It infers the oldest member, or the two oldest on a joint return, respecting supplied dependency hints when some member isn't a supplied dependent. The same inference identifies filers for household income. An age tie between a filer and dependent needs explicit head/spouse roles. A dependent another taxpayer could also claim stays in the family of the return that claims them.
aca_tax_family_size (new) Form 8962 line 1: the number of members. The PR leaves tax_unit_size alone.
aca_fpg (new) Form 8962 line 4: the prior-year guideline for aca_tax_family_size. A return where another taxpayer can claim every filer has no tax family; it keeps the tax unit's guideline as a numerical convention. The credit reads $0 there, and other readers of aca_fpg see the old value. In 2015, the first modeled year, the tax year's guideline stands in (the guard from #10773, moved here so California's two direct reads get it too).
aca_magi_fraction Household income over aca_fpg (was tax_unit_fpg for the prior year, which also took the household size from the prior year; the size now comes from the tax year, as line 1 requires, which differs only when a user supplies a prior-year size).
aca_magi Household income (1.36B-1(e)(1)) excludes tax-exempt interest and Social Security of dependents outside the tax family, while retaining both joint filers' MAGI additions. Return-level AGI still follows the model's general tax-role calculations; the ACA inference does not reconstruct it. With no out-of-family dependent it reads medicaid_magi directly, including a supplied value. When exclusion is necessary, it reconstructs AGI plus MAGI additions, removes the excluded amounts, then floors once at zero; this also handles signed Social Security. Medicaid calculations remain separate.
is_aca_ptc_eligible, is_aca_ptc_eligible_before_premium (new) Both require tax-family membership. The substantive eligibility variable includes the existing income and return-status requirements without the marginal-premium condition; is_aca_ptc_eligible additionally requires pays_aca_premium. This lets CSR distinguish an insured fourth child from someone outside the tax family.
aca_ptc_below_fpl_immigration_exception The lawfully present person must be in the tax family: "the taxpayer or a member of the taxpayer's family" (1.36B-2(b)(5)).
is_aca_coverage_family_member (new), is_aca_marketplace_enrollee (new) Coverage-family membership is Marketplace enrollment plus tax-family membership (1.36B-3(b)(2)). Enrollment is separate from marginal premium payment: a fourth covered child remains enrolled even though the three-child rating cap gives them no additional age-rated premium. A supplied pays_aca_premium of true marks an enrollee.
aca_child_index, pays_aca_premium The whole policy also ranks only Marketplace-enrolled children for its three-child premium limit. Adults and non-enrolled people receive the existing sentinel index 99; older children on employer coverage cannot remove a younger covered child's premium.
aca_ptc_slcsp (new), with aca_ptc_slcsp_family_tier_category and _multiplier The model prices the coverage family separately, using its three oldest covered children in age-rated states (45 CFR 147.102(c)(1)) or its own family tier in NY/VT. Non-enrolled children use no ranking slots. Supplied slcsp_age_curve_amount_person prices, including positive and zero quotes for enrolled nonpayers, flow through an uncapped-price variable. Without a supplied quote, the model reprices a child freed from the original family's cap. When every enrollee belongs to the tax family, aca_ptc_slcsp reads slcsp directly, including supplied values. slcsp still prices the whole enrollment.
aca_ptc, aca_ptc_before_filing_gate Main's aca_ptc filing-gate wrapper remains intact. Its aca_ptc_before_filing_gate calculation uses aca_ptc_slcsp; the filing decision and take-up behavior from main remain in the dependency path.
aca_ptc_coverage_family_premium (new), used_aca_ptc The credit cannot exceed the coverage family's enrollment premiums (1.36B-3(d)(1)(i)). Each month, allocate the selected plan premium by coverage_family_benchmark / (coverage_family_benchmark + other_family_benchmark), pricing the other enrollees separately; then sum the allocated monthly amounts (1.36B-3(a), (h)(1)). This applies to silver and bronze. The share is one when every enrollee is in the family. A premium supplied for the year or for any month, for a tax unit in which the model finds no enrollee and with is_aca_marketplace_enrollee not supplied, is the tax family's, as before enrollment was modeled; otherwise the allocation reads zero when no family member enrolls, and a tax unit with no tax family gets none.
marketplace_csr_eligible The model prices one policy per tax unit. Under 45 CFR 155.305(g)(3), every insured individual must satisfy the substantive PTC conditions for the shared policy to receive CSR. An enrolled claimable spouse blocks CSR even when the rating cap makes their marginal premium zero; an ordinary fourth covered child retains substantive eligibility. Supplied is_aca_ptc_eligible values continue to apply to premium-paying enrollees.
slcsp_family_tier_category, slcsp_family_tier_multiplier Shared functions price the requested enrollment group. Explicitly supplied family-child and NY age-29 predicates remain in the dependency graph, including for enrollees paying no marginal premium and returns with no claimable filer. Calculated family-child values retain the public premium-payment condition; separate-family repricing applies the uncapped child condition to calculated nonpayers.
aca_ptc_700_fpl_cliff, aca_ptc_additional_bracket, aca_ptc_simplified_bracket reforms Each overrides is_aca_ptc_eligible and none changes 36B(c)(1)(D), so each keeps the gate. Without it the reforms would pay claimable filers.
aca_ptc_minimum_premium reform Its benchmark is aca_ptc_slcsp. The enrolled premium in its cap is the larger of that benchmark and aca_ptc_coverage_family_premium, and its used_aca_ptc caps the credit at aca_ptc_coverage_family_premium less the minimum premium.

selected_marketplace_plan_premium_proxy keeps its annual input API and sums monthly_selected_marketplace_plan_premium_proxy. The monthly allocation uses the month-specific selected plan prices. When a user supplies only an annual selected premium, the model distributes that total in proportion to the monthly selected-plan proxies; if those proxies are all zero, it distributes the total evenly. This timing assumption preserves the supplied annual amount. A user who knows the timing can supply monthly premiums through the new monthly variable. Either way, a supplied premium for a tax unit in which the model finds no enrollee, with enrollment not supplied, goes to the tax family.

Cost-sharing eligibility per person requires APTC eligibility (45 CFR 155.305(g)(1)), and 155.305(f)(1)(ii) requires "a member of the tax filer's family within the meaning of 26 CFR 1.36B-1(d)".

Worked cases (aca_ptc.yaml), $500 a month benchmark per enrollee, contiguous US, both spouses aged 30:

Household 2025 (MAGI $22,590) 2026 (MAGI $23,475)
Single, claimable $0 $0
Joint, one spouse claimable (either labelling) family 1, 150% FPL, 0%: $6,000 family 1, 150% FPL, 4.19%: $5,016.40
Joint, both claimable $0 $0
Joint, neither (control) family 2, 110% FPL: $12,000 family 2, 110% FPL, 2.1%: $11,507.03
Joint, one claimable, MAGI $18,000 119% FPL for one: $6,000 (control at 88%: $0)
Joint, one claimable whose claimant meets the refund-only exception, child ($250 a month), MAGI $30,000 family 2 (spouse and child), 146%: $9,000
Joint, one claimable, AGI $20,000, child with $20,000 tax-exempt interest household income $20,000 (was $40,000): $6,000
Lone 17-year-old filer, claimable (no head inferred) $0 (was $6,000)
Joint, one claimable, silver plan at 0.75 of benchmark ($9,000) credit used $4,500 (was $6,000), net premium $4,500; no CSR

The joint fixtures with a positive credit test the rule given the flag; see the note under the readings.

Before this PR, the joint one-claimable couple got the control's credit, and the single claimable filer got $6,000 (2025).

State premium programs, each checked against its own law

Program Its rule for an enrollee outside the federal tax family Change
Massachusetts ConnectorCare Requires APTC eligibility: 956 CMR 12.04(3)(a)2 to 12.04(2)(b) to 45 CFR 155.305(f); "Household" is "the tax filer and the individuals for whom a tax filer properly expects to claim a personal exemption" (12.03, p.4) Gate flows; wrap uses aca_ptc_slcsp
Connecticut Covered Connecticut Enrollees must be "eligible for premium and cost-sharing subsidies for a qualified health plan" (PA 21-2 (JSS) §16(b)(1), p.22) Gate flows; wrap uses aca_ptc_slcsp
Colorado Premium Assistance Payments "for Coloradans who receive the premium tax credit" (C.R.S. 10-16-1205(1)(b)(II), 2024, PDF p.1002, the payment authority Regulation 4-2-78 cites) Gate flows; residual cap uses aca_ptc_slcsp. See reading 2
Maryland premium assistance and Young Adult Subsidy Enrollee must be "a member of a tax filer's tax household" and the filer must meet the APTC requirements (COMAR 14.35.21.03A(1)) Gate flows (including the young-adult reduction); wrap uses aca_ptc_slcsp
California Premium Subsidy (c)(2) "Meets all eligibility requirements of the federal advance premium tax credit"; (d)(7)(B) "No state premium assistance shall be allowed ... to any individual who is claimed as a dependent of another return filer"; (d)(5) benchmark and (d)(10) family size have their 36B meanings (2026 Program Design, p.2 for (c)(2) and (d)(5), p.3 for (d)(7)(B), (d)(10) and (d)(11)) Gate flows; subsidy uses aca_ptc_slcsp; eligibility comment updated. The band test and the rate lookup now divide by aca_fpg, the poverty line the federal credit uses. (d)(10) of the 2026 and Final 2027 Designs both give family size its section 36B meaning, and (d)(11) of both takes the guideline most recently published when open enrollment starts
New Mexico Premium Assistance, base "qualify for the federal Premium Tax Credit" (2026 MAP manual, p.4) Gate flows; benchmark uses aca_ptc_slcsp
New Mexico Middle Income Household (above 400% FPL) "Meet all eligibility criteria for the federal PTC except for household income requirements" (Addendum, p.2) nm_premium_assistance_mih_eligible now needs a coverage family member
Vermont Premium Assistance "An individual or family eligible for federal premium tax credits under 26 U.S.C. § 36B" (33 V.S.A. 1812(a)(1)) Gate flows; cap uses aca_ptc_slcsp
New Jersey Health Plan Savings Treasury's 1332 addendum describes the program as for enrollees "otherwise eligible for the Advanced Premium Tax Credit" (p.8), written for its first plan year; Get Covered NJ: "Tax households with annual incomes up to 600%". We found no current NJ rule on someone another taxpayer can claim, so the PR interprets the program (reading 4) nj_njhps_member_eligible now needs a tax family member (it does not read is_aca_ptc_eligible, to keep the 400-600% band); cap uses aca_ptc_slcsp. #9515 also edits these two files (citations only); land it first
Washington Cascade Care Savings Policy §4(1) needs QHP eligibility, not APTC eligibility, and §4(2)'s exclusions do not include being claimable (2026 policy, p.11); Group 2 is "QHP-eligible residents ... not eligible for APTC Federal subsidies but eligible for CCS" at $250 PMPM (2026 methodology, pp.1, 5) A QHP-eligible enrollee outside the tax family moves from Group 1 ($55) to Group 2 ($250); the cap keeps slcsp, since their premium is in the household's net premium. See reading 1

The PR leaves Colorado OmniSalud alone: it serves undocumented enrollees and reads neither the credit nor its eligibility. The Basic Health Program payment proxy reads aca_magi_fraction and so now uses the tax family's poverty line, as its documentation says it mirrors aca_ptc; the PR leaves its enrollee premiums alone (follow-up 2).

All modeled state programs start in 2026, so the state changes affect 2026 on.

The 2026 state cases use a joint couple aged 30 with one spouse claimable, MAGI of $23,475 and a $500 a month benchmark each, which gives a federal credit of $5,016.40. Each runs under both labellings, beside the nobody-claimable control and the both-claimable case. Before this PR the model treated this couple as the control in every program.

Program This couple Control
Massachusetts $983.60 $492.97
Connecticut $983.60 $492.97
Colorado $960 $492.97
Maryland $983.60 $492.97
New Mexico $1,583.60 $1,692.97
Vermont $352.13 $352.13
New Jersey $240 $0 (below 138% FPL)
Washington $3,660 $492.97
California, at MAGI $22,000 $785.92 $462

Readings

Max accepted readings 1 to 4 as built. Reading 5 sets a timing assumption for annual-only premiums.

  1. Washington, Group 2 poverty line: this PR measures the household's income against the tax family's poverty line for every Cascade Care member. The policy defines income as 36B(d)(2) household income and the FPL by 36B(d)(3)(B), but no retrieved WA source says which family size applies to a Group 2 member. Alternative: the tax unit's size for Washington only. The two readings differ only near the 250% ceiling.
  2. Colorado: this PR follows the statute (payments for "Coloradans who receive the premium tax credit"). Regulation 4-2-78 §4C defines an eligible enrollee as any QHP enrollee at or below 400% FPL, which would keep the claimable spouse in the count and cap: at the 2026 example above, $960 (this PR) against $1,308.
  3. Exchange "tax filer": 45 CFR 155.300 defines a tax filer as one expecting "that no other taxpayer will be able to claim him, her or them as a tax dependent". Read as "either spouse", an Exchange would deny advance payments to the whole couple, and the state wraps keyed to APTC eligibility with them. This PR follows the annual credit's per-member rule (1.36B-1(d)(2), Form 8962 line 1) for both.
  4. New Jersey: the NJHPS exclusion above interprets the program's federal alignment. We found no rule on it in current New Jersey authority.
  5. Timing of an annual-only selected premium: 26 CFR 1.36B-3(a), (h) require monthly amounts and don't identify payment timing when a user supplies only an annual premium. This PR weights that annual amount by monthly selected-plan price proxies, and equal monthly amounts offer an alternative. In the bronze example, the coverage-family allocation comes to $7,794.14 as built and $7,845.60 with equal monthly amounts.

Readings 2 and 3 are source conflicts, so source_conflicts/candidates.yaml records them as us-co:premium-assistance-ptc-recipients (now with its statute and regulation texts and code paths) and us:exchange-tax-filer-claimable-spouse. Readings 1 and 4 fill gaps where no source gives the alternative, so they aren't source conflicts and have no candidate.

Another taxpayer can claim a married person only if the couple files jointly "only to claim a refund of income tax withheld or estimated tax paid". Publication 501 Example 3 (p.11) holds that claiming a refundable credit defeats that. We infer that the example reaches the premium tax credit, so a joint return that claims a positive credit while one spouse is claimable may not arise in practice. The model takes the flag as given and applies the line 1 rule, as it does for recovery rebates. is_aca_tax_family_member's documentation now says so.

Invariants

policyengine_us/tests/core/test_claimable_filer_ptc_invariants.py checks items 1 to 3 with Hypothesis on generated roleful returns in each year 2021-2026, with spouses claimable, claimed or neither, and with and without the refund-only exception. It also runs a seeded population in 2025 and 2026, in Texas, New York, Vermont and the nine wrap states, on #10024's household builders. Separate YAML cases cover role-less minor filers, supplied inputs, changing monthly prices and empty enrollment:

  1. Swap invariance: exchanging the two adults' head and spouse labels leaves the tax family size, aca_fpg, aca_magi, aca_magi_fraction, slcsp, aca_ptc_slcsp and aca_ptc unchanged. It also leaves the coverage-family premium, the used credit, CSR eligibility, the number of eligible members and all nine state amounts unchanged.
  2. Identities:
    • aca_tax_family_size equals the filers no other taxpayer can claim, plus the dependents if one filer counts as an applicable taxpayer and none is claimable outside the exception.
    • Every eligible person belongs to the tax family, and a return with no family member gets no credit.
    • The generated benchmark falls between zero and the whole enrollment's benchmark.
    • ACA MAGI matches an independent income-removal calculation, including dependent additions and signed Social Security.
    • Used credit <= coverage-family premium <= selected premium.
    • CSR requires every enrollee to satisfy the substantive PTC conditions even if they pay no marginal premium.
    • On roleful returns where no other taxpayer can claim a filer, the benchmark, MAGI and family size keep their ordinary values.
    • aca_fpg.yaml tests the cases where the current-year family size differs from the old prior-year size. Separate YAML cases test role-less filer corrections and explicit supplied inputs.
  3. Monotonicity: marking another filer as claimed never raises the tax family size, never raises the benchmark for the same enrollees (checked person by person), and never raises the credit. Two intended exceptions, each tested in YAML: income crosses the 100% floor (below it for two, above it for one), or out-of-family dependents' income leaves household income. The test exempts those two.
  4. One poverty line: California's band test, its rate lookup and the federal credit all divide by aca_fpg. policyengine_us/tests/unit/test_ca_premium_subsidy_one_poverty_line_properties.py draws incomes in 2026 and 2027 for a couple with one claimable spouse (tax family of one, tax unit of two) and lets the model compute aca_fpg. It checks eligibility against the Design band and the rate against the Design interpolation over the one-person guideline, in exact arithmetic. YAML witnesses in ca_premium_subsidy.yaml cover $20,000, $25,000 (both labellings) and $27,000 in 2026 and $35,000 in 2027; each lands differently over the tax unit's two-person line.

The seeded test also asserts it reaches the rule: returns with one claimable filer and a positive credit, and in 2026 a positive state wrap.

YAML cases also pin each condition of the supplied-premium rule (enrollment supplied, an enrollee found outside the family, no tax family), a premium supplied by month, the even split of an annual premium with no monthly price pattern, the CSR test of a premium payer's supplied is_aca_ptc_eligible, is_aca_filer's fallback when every member is a supplied dependent, and the minimum premium reform's used_aca_ptc cap. The comments of the last three cases (even split, CSR, filer fallback) say what the changed line would return.

Tests

At e03b7ec97a (main merged at 0315452583), 1,121 tests passed across 88 files, one file per process with numeric threads capped.

Files Count Passed
California Premium Subsidy YAML (tests/policy/baseline/gov/states/ca/hbex/premium_subsidy/) and its three unit files (test_ca_premium_subsidy_applicable_percentage.py, test_ca_premium_subsidy_eligible_properties.py, test_ca_premium_subsidy_one_poverty_line_properties.py) 7 114
Federal ACA YAML (tests/policy/baseline/gov/aca/) 48 463
Massachusetts ConnectorCare 4 49
Connecticut Covered Connecticut 3 43
Colorado Premium Assistance 3 54
Maryland premium assistance 5 101
New Mexico Premium Assistance 5 97
Vermont Premium Assistance 3 38
New Jersey Health Plan Savings 4 70
Washington Cascade Care Savings 5 78
tests/core/test_claimable_filer_ptc_invariants.py 1 14

At 18385c186b, Pavel's runs (Python 3.13, policyengine-core 3.34.10) passed the federal ACA and ACA contrib directories (570), the nine state premium program directories (624), tests/policy/baseline/household/income/ (224), the invariant file with the three California unit files (34) and the partner contract tests (623), and CI passed 36 of 36 checks. 6d336a28dd adds five cases for Pavel's Should address 1-3. d4ec8c5cf8 renames twelve cases that carried review-round names, writes out the six cases that used YAML anchors, and adds three cases. CI runs them.

California now divides by aca_fpg in both its band test and its rate lookup. Its tests supply that denominator as aca_fpg for the test's own period (63 YAML pins and both unit files), and no expected output changes. Five YAML witnesses (2026 at $20,000, $25,000 under both labellings and $27,000; 2027 at $35,000) and the new property file fail if either California read returns to the tax unit's guideline or aca_fpg takes the tax unit's size.

Two fixtures needed new inputs; their assertions did not change. Three New Mexico MIH integration scenarios supply aca_magi without income, so Medicaid treats them as having no income and they don't enroll. They have failed since this PR's MIH gate began requiring a coverage-family member; CI skipped the draft at 09544440a7, so no run showed it. They now supply Marketplace enrollment. The invariant file now supplies its signed Social Security dependent as the social_security total, because #10484 requires reported components to be nonnegative.

This comment holds the review history through r4 and the earlier merge with main.

Microsimulation impact

Pavel Makarchuk ran this PR against its merge base (ac280b06ed) on the default dataset, one run each, at 18385c186b (review of 2026-11-13):

Weighted total 2025 merge base 2025 this PR 2026 merge base 2026 this PR
aca_ptc $170.0219bn $170.0219bn $144.7502bn $144.7502bn
used_aca_ptc $60.2158bn $60.2158bn $47.0997bn $47.0997bn
selected_marketplace_plan_premium_proxy $79.4978bn $79.4978bn $100.7288bn $100.7288bn
marketplace_net_premium $19.2820bn $19.2820bn $53.6291bn $53.6291bn
slcsp $352.3184bn $352.4290bn $444.5247bn $444.6575bn
pays_aca_premium (people) 52.7722m 52.7994m 53.4732m 53.5006m

slcsp rises by $0.11bn in 2025 and $0.13bn in 2026, and about 27,000 more people pay an age-rated premium (27,200 in 2025, 27,400 in 2026). Pavel notes that this agrees with the covered-child ranking, under which an older child who isn't enrolled no longer takes one of the three child-premium slots; he didn't break the difference down by cause. The credit totals (aca_ptc, used_aca_ptc) and the premium totals don't move at this precision.

The default dataset sets the dependency inputs for nobody (follow-up 3) and has no column for pays_aca_premium, selected_marketplace_plan_premium_proxy, monthly_selected_marketplace_plan_premium_proxy or is_aca_marketplace_enrollee, so neither the claimable-filer rules nor the two supplied-input rules move it. The commits after 18385c186b weren't rerun; they add no dataset input and their formula changes compute the same values for it.

Follow-ups (separate work)

  1. Alaska and Hawaii households given a single year get the contiguous-US ACA poverty line, because the guideline lookup reads the prior year's state. Main's tax_unit_fpg(period.last_year) does the same, and this PR keeps that read so it changes nothing else. Use current ACA household with prior-year poverty guidelines #10413 (issue ACA applicable percentage uses the contiguous-states poverty guideline for Alaska and Hawaii #9482) fixes this in aca_magi_fraction; whichever lands second should move the fix into aca_fpg, so California's two direct reads get it too.
  2. Basic Health Program: the payment proxy's reference premium should cover only the hypothetical PTC coverage family, since the payment equals "95 percent of the premium tax credit for which the eligible individual would have qualified" (42 CFR 600.605(a)(1)). BHP eligibility also reads medicaid_income_level where 42 CFR 600.305 uses household income for "the applicable family size".
  3. The default dataset sets the dependency inputs for nobody, so none of the claimable-filer rules move a microsimulation. Setting them belongs in Microcosm.
  4. On ordinary returns, aca_magi (through medicaid_magi) adds dependents' tax-exempt interest and all their Social Security, but 1.36B-1(e)(1)(ii) counts another family member's income only if they "are required to file a return". Main does the same, and this PR removes only out-of-family dependents' amounts.
  5. Generic federal AGI role inference still treats a minor without an explicit spouse role as a tax-unit dependent, excluding their earnings. ACA filer inference here completes family membership and MAGI-addition retention; it does not reconstruct IRS AGI, deductions or loss limits. A separate generic-role correction should compare inferred 18/17 and 17/16 joint returns against explicit-role controls and preserve supplied AGI/MAGI precedence.
  6. Open drafts Treat income exactly at 400% FPL as premium tax credit eligible #10312, Decide Vermont Premium Assistance eligibility on the exact FPL ratio #10313, Decide Washington Cascade Care Savings eligibility on the exact FPL ratio #10314, Decide Covered Connecticut eligibility on the exact FPL ratio #10316, Decide Colorado Premium Assistance's 400% ceiling on the exact FPL ratio #10318, Decide Maryland Premium Assistance's 400% ceiling on the exact FPL ratio #10320 and Decide Marketplace CSR eligibility and tiers on the exact FPL ratio #10326 test the exact ratio over tax_unit_fpg(period.last_year). Whichever lands second should divide by aca_fpg, so each program uses the poverty line its credit uses (invariant 4).

axiom: us:statutes/26/36B/c/1/D queued (TheAxiomFoundation/rulespec-us#1627)

🤖 Generated with Claude Code

MaxGhenis and others added 12 commits October 8, 2026 11:03
The federal standard deduction and 17 state formulas read only whether the
tax-unit head is claimed elsewhere, so a joint return where one spouse can be
claimed was taxed differently depending on which spouse was labelled head.
Each formula now applies its jurisdiction's rule for that case (either spouse,
single filers only, per spouse, or only when every filer is claimed), using
two new label-independent helpers. Adds swap-pair YAML cases and a Hypothesis
property test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… barred

The New Mexico, Maine and Hawaii renters gates counted filers who are not
claimed elsewhere, so a tax unit with neither a head nor a spouse (252 in
the default dataset) looked like one whose every filer was claimed. A new
helper, every_filer_is_dependent_elsewhere, requires a claimed filer and no
unclaimed one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ss EITC

- Hawaii's dependent standard deduction uses earned income net of the
  deductible part of self-employment tax, as the N-11 worksheet does.
- New Mexico's medical care credit needs a filer who is both 65 or older
  and not a dependent when a filer is a dependent elsewhere (NMSA 7-2-18.13).
- The federal EITC without a qualifying child requires that no filer can be
  claimed as a dependent (IRC 32(c)(1)(A)(ii)(III), Publication 596), so
  Missouri's working family credit no longer reaches such a couple.
- Hawaii's food/excise credit keeps minor children receiving public support
  (HRS 235-55.85(c)) on a joint return where one spouse can be claimed.
- Comments label the readings the law does not settle, and the property
  test covers the EITC and the food/excise exemption amount.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… meaning

- The federal and Oregon dependent worksheets use earned income net of the
  deductible part of self-employment tax, as Hawaii's now does.
- Hawaii's food/excise minor-child count excludes children who can be
  claimed by another taxpayer and the filers themselves (Form N-311 line 3).
- claimed_as_dependent_on_another_return documents what it stands for: a
  §151 deduction for the person is allowable to another taxpayer, so a
  person whose would-be claimer files only for a refund is not one
  (Publications 501 and 596); rules on actually being claimed read it too.
- Hawaii's renters comment labels the mixed joint reading as an inference;
  the Hawaii dependent threshold cites HRS 235-2.4(a)(3) on its page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A filer who can be claimed on another return is treated as having no
dependents (IRC 152(b)(1); on a joint return either spouse counts) and has no
personal exemption (IRC 151(d)(2)); one who is claimed gets no education
credits (25A(g)(3)), student loan interest deduction (221(c)) or recovery
rebate (6428(d)(2), 6428A(d)(2), 6428B(c)(2)). The model read none of these.
Now the child tax credit and credit for other dependents, the under-13 child
and dependent care qualifying person, exemptions_count and its RI, DE, OH, OR,
WI, HI and NM readers, the recovery rebates, the education credits and the
student loan interest deduction apply them symmetrically for joint returns.
Georgia keeps its own counts; the HI, WI and Treasury exemption reforms
follow the corrected count.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…it family

IRC 36B(c)(1)(D) excludes anyone another taxpayer can claim from being an
applicable taxpayer, and 26 CFR 1.36B-1(d)(2) leaves such a spouse out of a
joint return's family. Add is_aca_tax_family_member and aca_tax_family_size,
measure household income against the poverty line for that family (aca_fpg,
aca_magi_fraction), gate is_aca_ptc_eligible and the below-FPL immigration
exception on it, and price the credit on the coverage family's benchmark
(aca_ptc_slcsp, which equals slcsp whenever every enrollee is in the family).
The NY/VT family-tier logic becomes shared functions so the benchmark can
apply it to the coverage family. The three ACA reforms that override
is_aca_ptc_eligible keep the gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e tax family

Massachusetts, Connecticut, Colorado, Maryland, California, New Mexico and
Vermont require each enrollee to be eligible for the federal credit, so the
gate flows through is_aca_ptc_eligible and their wraps use the coverage
family's benchmark. New Mexico's Middle Income Household component and New
Jersey Health Plan Savings require every federal criterion except income, so
they now read the tax family too. Washington's Cascade Care Savings pays its
non-federally-subsidized amount (Group 2) to a QHP-eligible enrollee without
a federal subsidy, so a claimable enrollee moves from Group 1 to Group 2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis and others added 12 commits October 10, 2026 09:35
- Child and dependent care: childcare expenses do not count on a return with a
  claimable filer unless a child under 13 still qualifies (IRC 21(b)(2)(A)(ii)).
- Tuition and fees deduction: not allowed to a filer who can be claimed (IRC
  222(c)(3)), so the education credit bar no longer makes such a filer eligible.
- Recovery rebates: the Armed Forces exception waives the identification rule
  only, not the exclusion of a spouse who is another taxpayer's dependent.
- Georgia: the contributed refundable credit and SB 520 reforms count the same
  children as ga_ctc_potential through a new ga_ctc_eligible_child.
- Education credits and student loan interest read the claimed input directly,
  since IRC 25A(g)(3) and 221(c) turn on an actual claim.
- One reference per source document; quote IRC 24(h)(4)(A) exactly.
- Tests: mixed-recipient care, tuition deduction, military rebates, Georgia
  refund cap, and the swapped New Mexico rebate case; the property test now
  covers the state readers of the exemption count.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	policyengine_us/tests/policy/baseline/gov/states/oh/tax/income/exemptions/personal/oh_personal_exemptions_eligible.yaml
#10024 now separates three facts: is claimed, can be claimed, and the would-be
claimant's filing exception.

- IRC 152(b)(1) gates (child tax credit, credit for other dependents, under-13
  care child and its expenses, dependents in exemptions_count, ARPA dependents,
  Ohio dependents, the Hawaii and Wisconsin reforms) read
  head_or_spouse_is_dependent_elsewhere_without_filing_exception, so a filer
  within the Publication 501 exception keeps their dependents.
- Own exemptions, recovery rebates and the tuition deduction read claimability.
- Education credits and student loan interest keep reading the claimed input.
- Tests: the filing exception and a filer who can be claimed but is not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#10024's food/excise credit, Act 115 rebate and renters credit took claimable
filers off exemptions_count themselves. exemptions_count now leaves them out
(and, outside the filing exception, the return's dependents), so those credits
read it as it is; the filing-exception cases were one exemption short.

The renters credit also leaves out a dependent who can be claimed by another
taxpayer (Schedule X counts only people who cannot be), as the food/excise
credit already did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Education credits: a dependent student is not eligible on a return whose
  filer can be claimed outside the filing exception (IRC 25A(f)(1)(A)(iii),
  152(b)(1)); the filer's own eligibility still turns on an actual claim.
- Recovery rebates: no credit when every filer is a dependent of another
  taxpayer (IRC 6428B(a)); the CARES and CAA child prerequisite is a spouse
  with a valid SSN, whether or not that spouse is an eligible individual.
- Child and dependent care: cdcc_qualifying_childcare_expenses holds the
  expense rule, and the single-parent work requirement reform and California's
  expenses read it.
- References: Georgia HB 136 page 3; one entry per recovery rebate statute;
  quote IRC 24(h)(4)(A) exactly in the test comment.
- Tests: dependent students, the two rebate cases, the reform and California
  expenses, and the Hawaii, Wisconsin and Treasury reforms with a claimable
  filer under both labellings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Education credits: is_barred_from_education_credits_by_dependency holds the
  claimed-filer and dependent-student rules; both eligibility formulas and the
  reconciliation SSN reform's Lifetime Learning Credit read it, so the reform
  no longer turns a barred student's tuition into that credit.
- Child and dependent care: childcare counts when any child under 18 is still a
  qualifying individual, so an incapacitated child aged 13 to 17 keeps it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Setting meets_eitc_identification_requirements on one person made it an input
for every person, so the other spouse lost their SSN too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…role-less units

- is_aca_tax_family_member reads claimable_as_dependent_on_another_return
  (#10024's split input: 36B(c)(1)(D) and 1.36B-1(d)(2) turn on being
  claimable, and Form 1040 line 12a, which Form 8962 line 1 keys on, has no
  refund-only carve-out). The return keeps its dependents when the would-be
  claimant meets the refund-only filing exception (Pub 501, Dependent
  Taxpayer Test), a return with no applicable taxpayer has no family, and a
  tax unit with neither a head nor a spouse uses each member's own
  claimability (a lone claimable minor no longer gets the credit).
- aca_magi leaves out the tax-exempt interest and Social Security of the
  return's dependents who are outside the tax family (26 CFR 1.36B-1(e)(1)).
- used_aca_ptc is capped at the coverage family's share of the selected plan
  premium (new aca_ptc_coverage_family_premium; 26 CFR 1.36B-3(d)(1)(i),
  (h)(1)), not the whole policy's premium.
- marketplace_csr_eligible applies 45 CFR 155.305(g)(3): the model prices one
  policy per tax unit, and a policy that also covers an enrollee without
  credit eligibility gets no cost-sharing reductions.
- aca_fpg documents that it sizes the family for the tax year; the NJHPS
  exclusion is labelled an interpretation; one reference per source in
  is_aca_coverage_family_member.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
YAML: refund-only exception (family keeps the child), single claimable filer
with the exception (no family), claimable but not claimed, lone claimable
and unclaimed 17-year-old filers, household income without an out-of-family
child's tax-exempt interest, the coverage-family premium cap (silver and
bronze), CSR under the family-policy rule, Colorado's binding residual
($420), and the tax year's family size against a supplied prior-year size.
Test inputs now use claimable_as_dependent_on_another_return.

Property test: Hypothesis runs every year 2021-2026 and draws claimable-but-
unclaimed spouses and the filing exception; the credit's monotonicity
exemption is limited to crossing the 100% floor or dependents' income leaving
household income; the benchmark check compares enrolled people, not counts;
new identities for household income, the premium cap and CSR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cation, MAGI floor

- A tax unit with neither a head nor a spouse is filed by its oldest member.
  When that member can be claimed elsewhere, nobody is in the tax family.
  Before, a claimable 17-year-old filing with an infant got $12,000.
- The coverage family is priced on its own. Its children are ranked for the
  three-oldest-children rule (45 CFR 147.102(c)(1)), and its family tier is
  built from its own members.
- A shared premium is allocated by each family's benchmark (26 CFR
  1.36B-3(h)(1)). The denominator is the coverage family's benchmark plus the
  benchmark of the enrollees outside it, not the whole policy's tier. An empty
  coverage family gets no share of the premium.
- Out-of-family dependents' tax-exempt interest and Social Security are
  removed before the single zero floor. A negative benefit no longer cuts
  household income.
- is_aca_marketplace_enrollee (enrolled) is split from pays_aca_premium
  (charged an age-rated premium). The family-tier child tests no longer
  depend on payment.
- Tests: YAML for each case under both head/spouse labellings. The property
  test now gives dependents tax-exempt interest and Social Security. It checks
  aca_magi against an expectation built from the inputs, and it exempts only
  that removal from monotonicity. Monotonicity runs under Hypothesis in every
  year 2021-2026. The "unchanged" identities apply only to returns with a
  head or spouse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Base automatically changed from claimable-filer-federal to main October 16, 2026 06:10
Address the round-1 items that Pavel's 2026-11-13 review carried forward.

- New cases pin the even-split fallback for a supplied annual premium, the
  CSR test of a premium payer's supplied PTC eligibility, and is_aca_filer's
  fallback when every member is a supplied dependent.
- aca_ptc_coverage_family_premium returns early when no tax unit has an
  enrollee outside its tax family; the result is unchanged.
- slcsp_age_curve_amount_person_uncapped uses has_input_for_period, and
  is_aca_tax_family_member reads is_dependent_elsewhere_without_filing_exception.
- California references reach PDF page 3 for (d)(7)(B), (d)(10) and (d)(11).
- The Colorado source-conflict candidate gets its URLs, quotes and code paths,
  and a new candidate records the Exchange "tax filer" reading.
- Case names drop review-round prefixes, is_aca_tax_family_member.yaml drops
  its YAML anchors, and the NM and tax-family-size wording is fixed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DTrim99

DTrim99 commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

@PavelMakarchuk, a follow-up to my 16:29 reply. d4ec8c5 takes round-1 Should address 2-7 and suggestions 2-5. Round-1 suggestion 1 isn't done (below). I haven't run tests locally; each new expected value is worked by hand in its case's comment, and CI will run them.

Round-1 Should address

  • 2, axiom issue: Updated the body of Encode IRC 36B(c)(1)(D) and the 36B(d)(1) family size; wire both into the ACA premium tax credit pipeline TheAxiomFoundation/rulespec-us#1627 to this head. It now covers:

    • the refund-only exception;
    • household income, with three new companion cases.

    It lists premium allocation, covered-child rating, shared-policy CSR and the nine state programs as separate issues. The 1.36B-2(b)(5) gate is moot for TY2026, since Pub. L. 119-21 repealed 36B(c)(1)(B).

  • 3, source-conflict register: Fixed.

    • source_conflicts/candidates.yaml:2064 (us-co:premium-assistance-ptc-recipients) now has both URLs: the 2024 C.R.S. Title 10 PDF (p.1002), and Amended Regulation 4-2-78 (p.2), the version the Division of Insurance's adoption notice links. It also has the quoted text, three code paths and a new note.
    • Reading 3 is a new candidate, us:exchange-tax-filer-claimable-spouse (:13984), with state unreviewed: it hasn't been put to the project lead.
    • Readings 1 and 4 get none: each fills a gap where no source gives the alternative, so neither is a source conflict.
  • 4, California pages: Fixed.

    • ca_premium_subsidy_eligible.py:11-20: each Design is one entry opening p.2, with a # PDF pages 2-3 comment; the comments place (c)(2) and (d)(7) on p.2, and (d)(7)(B), (d)(10) and (d)(11) on p.3.
    • ca_premium_subsidy_applicable_percentage.py:12-19: the same, for the (d)(4) table (p.2) and (d)(10) (p.3). ca_premium_subsidy.py:20-23: # PDF pages 1-2, with (d)(5) on p.2.
    • threshold.yaml:30-35: each Design's title now ends #page 2-3 and names (d)(10) and (d)(11).
    • One reference entry per document, as CLAUDE.md asks. I checked each page against the PDF text.
  • 5, helpers: Fixed.

    • slcsp_age_curve_amount_person_uncapped.py:23 uses has_input_for_period; the private call and the fallback are gone.
    • is_aca_tax_family_member.py:53-56 reads is_dependent_elsewhere_without_filing_exception. That is the same claimable & ~exception, and no test supplies it.
    • The PR body's helper sentence now names what the PR reads.
  • 6, unpinned branches: Fixed.

    • marketplace_csr_eligible.py:27-31: marketplace_csr_eligible.yaml:292 has two premium payers supplied with is_aca_ptc_eligible true and false. CSR is false; with the before-premium test only, it would be true.
    • The even-split fallback (aca_ptc_coverage_family_premium.py:78): aca_ptc_coverage_family_premium.yaml:691 has a supplied $7,000 bronze premium with lcbp: 0. The result is 3,500; with a zero fallback it would be 0.
    • is_aca_filer.py:32: is_aca_tax_family_member.yaml:644 has a 17-year-old and an infant, both supplied as dependents. is_aca_filer is true for the 17-year-old and the family size is 2; with ~dependent the family size would be 0.
  • 7, microsimulation: Fixed in the PR body, using your table and crediting your run. It says what moves: slcsp rises by $0.11bn (2025) and $0.13bn (2026), and about 27,000 more people pay an age-rated premium. The credit totals don't move at that precision.

Round-1 suggestions

  • 1, the two tier variables: Not done. No formula or reform reads them, but aca_ptc_slcsp.yaml:743-744 and :817-820 assert both, to show the NY tier the coverage family is priced at, and removing them drops those checks. If you'd rather lose them, I'll remove the variables and those four lines.
  • 2, NM comment: Fixed. nm_premium_assistance_mih_eligible.py:32-35, plus the same name at :16 and :27.
  • 3, names and anchors: Fixed.
  • 4, wording: Fixed.
    • aca_tax_family_size.py:16-20 and is_aca_tax_family_member.py:22-24 say "a filer (is_aca_filer: a head or spouse, including one inferred ...)".
    • is_aca_tax_family_member.py:32-38 adds the Publication 501 joint-return caveat and says the model takes the flag as given.
  • 5, early return: Done. aca_ptc_coverage_family_premium.py:60-64 returns before the monthly benchmarks when no tax unit has an enrollee outside its tax family. That return gives the same value as the full formula, since the share is 1 there.
  • 6, the Count the premium tax credit in household net income as a refundable credit #10773 guard: Still resolved, nothing to change. It's in aca_fpg.py:40-44, and California's two reads (ca_premium_subsidy_eligible.py:58, ca_premium_subsidy_applicable_percentage.py:34) go through aca_fpg.

No formula result changes in this commit outside the new test cases.

@PavelMakarchuk PavelMakarchuk left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE (head d4ec8c5cf8)

The two pushes (6d336a28dd, d4ec8c5cf8) close every open item from my last review and from my first review. I changed each pinned line back and a test now fails each time. I found no new defect in the diff since 18385c186b. No Critical or Should address item is open. Four optional suggestions remain.

Resolved since the last review

Item Status How I checked
Last review, Should 1: the reform's used_aca_ptc read at aca_ptc_minimum_premium.py:76 was not pinned Resolved The new case at ptc_minimum_premium.yaml:303 gives aca_ptc_coverage_family_premium 4,000, aca_ptc 5,940, used_aca_ptc 3,940. With the whole-policy read at line 76: 1 failed, 11 passed (used_aca_ptc 5,940, expected 3,940).
Last review, Should 2: the three conditions of the supplied-premium rule were not pinned Resolved Three new cases in aca_ptc_coverage_family_premium.yaml (from line 569). I removed each condition in turn; each time 1 failed, 16 passed (table below).
Last review, Should 3: monthly premium inputs did not reach the rule Resolved aca_ptc_coverage_family_premium.py:45-52 now also tests each month of monthly_selected_marketplace_plan_premium_proxy. The California witness gives 6,000 / 1,000 / 5,000 (table below). Without the monthly test: 1 failed, 16 passed.
First review, Should 2: axiom issue was stale Resolved TheAxiomFoundation/rulespec-us#1627 is open with the pe-parity label. Its body was updated on 2026-11-13 at 11:46am EST to this head. It now has the refund-only exception (required output 2, case H) and household income (required output 3, cases I and J). It gives a reason for each rule it leaves to separate issues.
First review, Should 3: source-conflict register Resolved us-co:premium-assistance-ptc-recipients has both URLs, quoted text and three code paths. Reading 3 is the new candidate us:exchange-tax-filer-claimable-spouse. I opened both Colorado sources (below).
First review, Should 4: California reference pages Resolved The references open PDF page 2 and name pages 2-3. I read pages 1 to 3 of both Designs (below).
First review, Should 5: helpers and private Core API Resolved slcsp_age_curve_amount_person_uncapped.py:23 calls has_input_for_period; the private call and the fallback for older Core releases are gone. is_aca_tax_family_member.py:53-56 reads is_dependent_elsewhere_without_filing_exception. The PR body names the helpers that the PR reads.
First review, Should 6: three unpinned branches Resolved One new case for each branch. I changed each branch back; a test fails each time (table below).
First review, Should 7: microsimulation impact was "Pending" Resolved The PR body has the table and says which totals move. I ran this head again; the totals did not change (below).
Last review, suggestion 1: changelog Resolved changelog.d/claimable-filer-ptc.fixed.md names both supplied-input rules.
First review, suggestions 2 to 5 Resolved The New Mexico comment, the twelve case names, the YAML anchors, the wording and the early return are done. Suggestion 1 is open (below).

Suggestions

  1. The two tier variables have no reader (first review, suggestion 1). No formula or reform reads aca_ptc_slcsp_family_tier_category or aca_ptc_slcsp_family_tier_multiplier; only aca_ptc_slcsp.yaml asserts them. It is acceptable to keep them as outputs for the tests. If they stay, say in their documentation that they are reporting outputs and that aca_ptc_slcsp does not read them.
  2. Follow-up 1 of the PR body names only #10413. #10860 is also open for the same problem (issue #9482). Name both. The PR that merges second (this one or #10860) must put the coverage-year state lookup and the zero-guideline handling of #10860 into aca_fpg, with aca_tax_family_size as the size, and keep aca_magi_fraction reading aca_fpg, so the federal fraction and California's two direct reads use one poverty line.
  3. The new register candidate is unreviewed. us:exchange-tax-filer-claimable-spouse says the reading was not put to the project lead. Put it to them after the merge; the model result for a joint return with one claimable spouse depends on it.
  4. The microsimulation paragraph of the PR body says that the commits after 18385c186b were not rerun. They can now say that the 2026 totals at d4ec8c5cf8 are the same (below).

What I checked

Mutation checks at this head. I changed one line at a time and ran the test file that holds the new case.

Line changed Change Result Failing value
aca_ptc_minimum_premium.py:76 Read selected_marketplace_plan_premium_proxy 1 failed, 11 passed used_aca_ptc 5,940, expected 3,940
aca_ptc_coverage_family_premium.py:53-55 Remove "enrollment not supplied" 1 failed, 16 passed premium 5,000, expected 0
aca_ptc_coverage_family_premium.py:57 Remove ~tax_unit.any(enrolled) 1 failed, 16 passed premium 5,000, expected 0
aca_ptc_coverage_family_premium.py:57 Remove tax_unit.any(member) 1 failed, 16 passed premium 5,000, expected 0
aca_ptc_coverage_family_premium.py:47-52 Remove the monthly input test 1 failed, 16 passed premium 0, expected 6,000
marketplace_csr_eligible.py:27-31 Use the before-premium test only 1 failed, 7 passed marketplace_csr_eligible true, expected false
aca_ptc_coverage_family_premium.py:78 Zero fallback in place of the even split 1 failed, 16 passed premium 0, expected 3,500
is_aca_filer.py:32 ~dependent in place of the where 1 failed, 21 passed is_aca_filer [false, false], expected [true, false]
aca_ptc_coverage_family_premium.py:60-64 Remove the early return 224 passed (gov/aca/ptc and contrib/aca) none: the early return gives the same values

Monthly premium witness (2026, California, one adult aged 40, aca_ptc: 1_000, no other inputs, so the model finds no enrollee):

Premium input selected_marketplace_plan_premium_proxy aca_ptc_coverage_family_premium used_aca_ptc marketplace_net_premium
Annual, 5,000 5,000 5,000 1,000 4,000
Monthly, 500 in each month 6,000 6,000 1,000 5,000
Monthly, 500 for January to June only 3,000 3,000 1,000 2,000
Monthly, 500 for December only 500 500 500 0
Annual 5,000 and monthly 500 in each month 5,000 5,000 1,000 4,000
Annual 5,000 and monthly 500 for January to June 5,000 5,000 1,000 4,000
Monthly 500 in each month, is_aca_marketplace_enrollee: false 6,000 0 0 6,000
Monthly 500 in each month, adult claimable elsewhere 6,000 0 0 6,000
Monthly 0 in each month 0 0 0 0
Monthly 500 for each month of 2025 only 0 0 0 0
  • The second row was 6,000 / 0 / 0 / 6,000 at the last head.
  • When the annual and the monthly inputs are both supplied, the annual amount is the premium. This agrees with the documentation of selected_marketplace_plan_premium_proxy.
  • A premium supplied for another year does not start the rule.

Since-prior diff, line by line

  • aca_ptc_coverage_family_premium.py:44-55: the input test is a Python boolean for the whole simulation, and it combines correctly with the two arrays. I ran one simulation with four tax units in Texas (2026), each with a supplied premium, once with annual and once with monthly inputs. The results are the same for both input types:

    Tax unit Premium aca_ptc_coverage_family_premium
    Default adult, no enrollee found 5,000 5,000
    Joint; the claimable head is the only enrollee 4,000 0
    Joint; both enrolled, the head claimable (equal benchmarks) 7,000 3,500
    Single adult, no enrollee found 3,000 3,000
  • aca_ptc_coverage_family_premium.py:60-64: when no tax unit has an enrollee outside its tax family, the share is 1 for each unit, so the early return equals the full formula. The mutation check above confirms it.

  • is_aca_tax_family_member.py:53-56: is_dependent_elsewhere_without_filing_exception is claimable & ~exception at the person level (it is from #10024 on main). No ACA test supplies it. The projection through person.tax_unit.any is unchanged.

  • slcsp_age_curve_amount_person_uncapped.py:23: has_input_for_period is the shared helper in policyengine_us/tools/general.py. This PR does not change that file. No variable or reform of this PR calls a private Core method.

  • is_aca_tax_family_member.yaml:503-642: I parsed the file at both heads. The 21 old cases differ only in their names; one case is new.

  • New expected values, by hand: 8,000 x 6,000 / 12,000 = 4,000 and 4,000 - 60 = 3,940; 12 x 500 = 6,000; 12 x (7,000 / 12) x 0.5 = 3,500.

  • No parameter value changed. threshold.yaml changes only two reference titles.

  • Defects found: none.

Axiom line

  • The line axiom: us:statutes/26/36B/c/1/D queued (TheAxiomFoundation/rulespec-us#1627) has the correct form.

  • The issue is open, has the pe-parity label, and names this head.

  • I ran its companion cases B, F and H in the model (2026 joint return, aca_magi: 23_475, benchmark 6,000 for each member). The model agrees with the issue:

    Case aca_tax_family_size aca_fpg aca_ptc
    B: one claimable spouse 1 15,650 5,016.40
    F: as B with one child 1 15,650 5,016.40
    H: as F, the claimant files only for a refund 2 21,150 11,507.03
  • The issue leaves premium allocation, covered-child rating, shared-policy CSR and the nine state programs to separate issues. Its reason holds: the rulespec-us pipeline takes the enrolled premium and the benchmark from the caller, and it has no CSR module and no module for these state programs.

Source-conflict register

  • us-co:premium-assistance-ptc-recipients: PDF page 1002 of the 2024 C.R.S. Title 10 file shows 10-16-1205(1)(b)(II) with the quoted text. PDF page 2 of Amended Regulation 4-2-78 shows Section 4C ("Eligible enrollee") with the quoted text, and page 1 shows the quoted Section 2 text.
  • us:exchange-tax-filer-claimable-spouse: the entry has three sources, two readings, an example (5,016.40, the same as case B above) and two code paths. All code paths in both entries exist.
  • policyengine_us/tests/code_health/test_source_conflicts.py and test_known_dead_reference_urls.py: 143 passed.

California reference pages (2026 Program Design and Final 2027 Program Design)

Provision PDF page, 2026 PDF page, 2027 Value on the page
(a), (b) 1 1 subsidy formula
(c)(2) 2 2 "Meets all eligibility requirements of the federal advance premium tax credit"
(d)(4) table 2 2 2026: 0% to 150%, 3.19% to 3.91% above 150% up to 165%. 2027: 2.8% to 5.28% above 150% up to 200%
(d)(5) 2 2 benchmark has its section 36B meaning
(d)(7) 2 2 "at or below 165 percent" (2026), "at or below 200 percent" (2027)
(d)(7)(B), (d)(10), (d)(11) 3 3 dependent rule, family size, poverty level
  • ca_premium_subsidy_eligible.py:11-20, ca_premium_subsidy_applicable_percentage.py:12-19, ca_premium_subsidy.py:20-25 and threshold.yaml:30-35 agree with this table.
  • The thresholds 1.5, 1.65 (2026) and 2.0 (2027) are on page 2 of each Design.

Microsimulation (default dataset, weighted 2026 totals, one run for each commit)

Total 18385c186b d4ec8c5cf8
aca_ptc $144.7502bn $144.7502bn
used_aca_ptc $47.0997bn $47.0997bn
aca_ptc_coverage_family_premium $100.7288bn $100.7288bn
Marketplace enrollees 54.0744m 54.0744m
  • The totals did not change. They are the same as in my last review.
  • has_input_for_period is false for pays_aca_premium, selected_marketplace_plan_premium_proxy, monthly_selected_marketplace_plan_premium_proxy and is_aca_marketplace_enrollee on the default dataset, so the supplied-input rules stay inactive for population results.

Tests run at this head (Python 3.13, policyengine-core 3.34.10)

Tests Result
policyengine_us/tests/policy/baseline/household/income/ 224 passed
policyengine_us/tests/policy/baseline/gov/aca/ and policyengine_us/tests/policy/contrib/aca/ 578 passed
The nine state premium program directories (CA, CO, CT, MA, MD, NJ, NM, VT, WA) 624 passed
tests/core/test_claimable_filer_ptc_invariants.py and the three tests/unit/test_ca_premium_subsidy_*.py files 34 passed
policyengine_us/tests/policy/baseline/partners/ 623 passed
The two register test files in tests/code_health/ 143 passed
  • The ACA count is 570 at the last head plus the 8 new cases.
  • Partner contract tests: the PR edits none of them.

Merge with main

  • The PR merges into main at 5cc0d58afa with no conflict. On that merge, gov/aca, contrib/aca and household/income give 802 passed.
  • Main moved by six commits after 5cc0d58afa. One of them changes source_conflicts/candidates.yaml, which this PR also changes. GitHub reports the PR as mergeable.

CI and repository rules

  • CI at this head: 36 of 36 checks passed; the last one completed on 2026-11-13 at 1:00pm EST.
  • The changelog fragment is at the top level of changelog.d/.
  • The PR adds no program, so policyengine_us/programs.yaml needs no change.

Not verified

  • I ran the tests on Python 3.13; CI uses 3.14. CI is green at this head.
  • The microsimulation comparison is one local run for each commit on the default dataset, for 2026 only. I did not run the microsimulation test suite locally (the CI check passed), and I did not run another dataset or 2025 at this head.
  • For each mutation I ran the test file (or the two directories) named in the table, not the full suite.
  • I did not run the tests on a merge with the newest main, only with 5cc0d58afa. I did not run the register tests on the merge.
  • In TheAxiomFoundation/rulespec-us#1627, I ran cases B, F and H. I did not run cases A, C, D, E, G, I and J, and I did not check the corpus rows that the issue names.
  • For the register entry us:exchange-tax-filer-claimable-spouse, I did not open the three federal sources again; I read 26 CFR 1.36B-1(d) in my first review.
  • The sources that I could not open in the first review (956 CMR 12.00, Connecticut Public Act 21-2, the New Mexico MIH Addendum, Publication 501, the Form 1040 instructions).

@DTrim99
DTrim99 merged commit 383192a into main Nov 13, 2026
36 checks passed
@DTrim99
DTrim99 deleted the claimable-filer-ptc branch November 13, 2026 20:53
DTrim99 added a commit that referenced this pull request Nov 13, 2026
#10041 moved the guideline lookup into aca_fpg and the enrollment conditions
of pays_aca_premium into is_aca_marketplace_enrollee. Resolve by carrying
this PR's changes to where they now live, as Pavel's review laid out:
- aca_fpg reads the state group for the coverage year and lags only the
  guideline (1.36B-1(h); Form 8962 line 4).
- aca_magi_fraction reads aca_fpg and keeps the zero-guideline guard and the
  multiply-first truncation.
- is_aca_marketplace_enrollee carries the no-Exchange test for Guam, Puerto
  Rico and the Virgin Islands; pays_aca_premium is main's.
- The coverage-year family-size case now supplies aca_tax_family_size, which
  aca_fpg reads since #10041.
- Both sides' test cases are kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis added a commit that referenced this pull request Nov 13, 2026
Main's 19 new commits include the premium tax credit rules for a filer
who can be claimed as a dependent (#10041). They add four items to
source_conflicts/candidates.yaml and edit three others, none of which
this branch changes, and Git merged the file without a conflict.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 13, 2026
…age-year state

Per Pavel's re-review at d590964:
- S1: since #10041, aca_magi_fraction divides by the stored aca_fpg, and in
  32-bit arithmetic 35,369 / 15,650 x 100 rounds to exactly 226, so that case
  no longer caught a divide-first formula. Use 36,621 (234% of 15,650), which
  divide-first floors to 233.
- The claimable-filer invariant compares aca_fpg with the prior year's
  guideline for the coverage year's tax family size and state group, not
  with tax_unit_fpg for the prior year, which reads the prior year's state.
- The territory cases assert is_aca_marketplace_enrollee, and their comments
  name where the comparisons now live.
- is_aca_marketplace_enrollee documents that a supplied pays_aca_premium still
  marks an enrollee in the territories, with no credit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis added a commit that referenced this pull request Nov 14, 2026
Main's #10041 rewrote the note on Colorado's premium-assistance item,
directly above the District of Columbia childless EITC item this branch
adds. Keep main's note and the branch's item.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 16, 2026
…t's income fraction (#10860)

* Use the Alaska and Hawaii poverty guidelines in the premium tax credit's income fraction

aca_magi_fraction read the household's state for the guideline year, so a
state supplied only for the coverage year fell back to the default state
there. It now reads the state for the coverage year and lags only the
guideline (26 CFR 1.36B-1(h)). Fixes #9482.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Use the coverage year's family size, handle territories, and fix references

- Read tax_unit_size for the coverage year (26 CFR 1.36B-1(d)(1)); only the
  guideline lags.
- Backdate the Guam, Puerto Rico and Virgin Islands guideline placeholders to
  1992, so coverage before 2025 no longer raises ParameterNotFoundError for a
  territory household. Their fraction is infinite, and is_aca_ptc_eligible now
  requires a finite fraction, since the 2021-2025 eligibility rows have no
  upper limit and no Exchange operates in the territories (36B(c)(2)(A)).
- Replace the titled Form 8962 references with a bare URL pinned to the 2025
  instructions (Line 4 and Worksheet 2, file pages 8-9) and drop the
  documentation that counted reference entries.
- Tests: a mover from Alaska to Texas, coverage-year family size, 2025
  coverage in Alaska, Alaska and Texas in one simulation, Alaska's 100% and
  400% edges, and a 2024 Puerto Rico household.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep the 2024 territory guideline placeholder as the last value

Moving the placeholders' only value to 1992 made uprating start in 1992,
where gov.hhs.fpg_uprating is undefined, so the parameter tree failed to
load. Keep 2024-01-01: 0 as the last value and add 1992-01-01: 0 before it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Charge no Marketplace premium in the territories; pin the zero-guideline guard

- pays_aca_premium is false where aca_magi_fraction is infinite, which is
  where HHS publishes no guideline: Puerto Rico, Guam and the Virgin Islands
  have no Exchange (26 U.S.C. 36B(c)(2)(A); 42 U.S.C. 18024(d)). An infinite
  fraction was outside the coverage gap, so a territory household below the
  floor, $0 included, was treated as paying a Marketplace premium.
- Drop the finite-fraction check in is_aca_ptc_eligible: core's single-amount
  scale already maps an infinite fraction to its false out-of-range cell, so
  the check changed nothing, and its comment said otherwise.
- New 2026 Puerto Rico case at $0 of MAGI pins the zero-guideline guard: the
  required contribution is 0, where plain division gives NaN and a fraction
  of 0 gives 0.021. The 2024 case now asserts pays_aca_premium false.
- Cite 1.36B-1(d) rather than (d)(1), and 42 U.S.C. 18024(d).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Multiply before dividing in the fraction; drop the fpg.yaml edit; test territories by state group

Per Pavel's review:
- C1: compute 100 * MAGI / guideline before flooring. Dividing first floored
  income exactly on a whole percentage one point low in every state (Texas,
  $35,369 in 2026: 2.25 instead of 2.26). New case pins it.
- S1: restore fpg.yaml. Core backdates each parameter's first value to 2015,
  so the 2024 territory placeholder already answers every guideline year the
  credit reads; the 1992 entries only changed 2015 results outside the ACA.
  Correct the changelog and the 2024 Puerto Rico case's comment.
- Suggestion 1: pays_aca_premium tests the state group for Guam, Puerto Rico
  and the Virgin Islands instead of reading an infinite fraction.
- Add PR 10413's negative-income case.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Drop the changelog line about whole-percentage truncation

main already multiplies before dividing, so the truncation order changes
nothing against main; only this PR's earlier commit had regressed it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Test the Guam and Virgin Islands exclusions from Marketplace premiums

Per Pavel's re-review: the territory test is three state-group comparisons,
and only Puerto Rico's had a case. Each new case fails without its
comparison.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Re-pin the multiply-first truncation; check aca_fpg against the coverage-year state

Per Pavel's re-review at d590964:
- S1: since #10041, aca_magi_fraction divides by the stored aca_fpg, and in
  32-bit arithmetic 35,369 / 15,650 x 100 rounds to exactly 226, so that case
  no longer caught a divide-first formula. Use 36,621 (234% of 15,650), which
  divide-first floors to 233.
- The claimable-filer invariant compares aca_fpg with the prior year's
  guideline for the coverage year's tax family size and state group, not
  with tax_unit_fpg for the prior year, which reads the prior year's state.
- The territory cases assert is_aca_marketplace_enrollee, and their comments
  name where the comparisons now live.
- is_aca_marketplace_enrollee documents that a supplied pays_aca_premium still
  marks an enrollee in the territories, with no credit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
Read the exact ratio from aca_fpg, the poverty line the credit's fraction
has divided by since #10041, and point is_aca_ptc_eligible_before_premium
at aca_ptc_income_eligible. Keep territories without a guideline out of the
right-closed lookup.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
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>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. Pin the test fixtures to aca_fpg and add
a joint return with a claimable spouse, whose ceiling follows the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. Pin the test fixtures to aca_fpg and add
a joint return with a claimable spouse, whose ceiling follows the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. COMAR 14.35.21.02B(3) and MHBE's income
thresholds support the guideline year; Maryland's rules don't define the
family counted, so the comment calls that part a modeling choice. Pin the
test fixtures to aca_fpg and add a joint return with a claimable spouse,
whose ceiling follows the one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above a limit
can't round down onto it. 956 CMR 12.03 and the Health Connector's subsidy
guides support the guideline year. The regulation's Household doesn't say
whether a filer who can be claimed on another return counts, so the comment
calls that point a modeling choice. Pin the test fixtures to aca_fpg and add
joint returns with a claimable spouse, whose limits and Plan Type follow the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
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 175%
can't round down onto the limit. Pin aca_fpg in the test fixtures for the
coverage year, and add joint-return cases where a claimable spouse leaves a tax
family of one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 18, 2026
…line

Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
ceiling can't round down onto it. DOBI's and Get Covered NJ's dollar limits
imply the guideline year. Get Covered NJ's "tax households" isn't defined,
so the comment calls leaving out a filer who can be claimed elsewhere a
modeling choice. Pin the test fixtures to aca_fpg, add joint returns with a
claimable spouse, and move main's two such cases at exactly 150% FPL to
DOBI's $40 band. The household pipeline cases now supply income, because
the gates no longer read a supplied aca_magi_fraction. Cite DOBI's table as
Section 2, item 7 of the filing requirements.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
…10313)

* Decide Vermont Premium Assistance eligibility on the exact FPL ratio

33 V.S.A. 1812(a)(1) covers income "less than or equal to 300 percent of
federal poverty level". The gate compared the truncated aca_magi_fraction
with 3.0, so every income from 300.00% to 300.99% passed. Test the exact
ratio of nonnegative ACA MAGI to the prior-year guideline instead.

Integration Scenario 2 expected a $47,000 single filer (300.32%) to stay
eligible because the fraction truncates to 3.00; it now tests exactly
300% ($46,950), and Scenario 2b keeps $47,000 as an ineligible case. Two
three-person cases supplied a 3.00 fraction with $100,000 of MAGI (375%
of $26,650); they now use $79,950.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Read Vermont's 300% limit from the credit's poverty line

Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. Pin the test fixtures to aca_fpg and add
a joint return with a claimable spouse, whose ceiling follows the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
…tio (#10318)

* Decide Colorado Premium Assistance's ceiling on the exact FPL ratio

Amended Regulation 4-2-78 Section 4.C defines an eligible enrollee by
household income "no greater than 400% of the Federal Poverty Level". The
gate compared the truncated aca_magi_fraction with 4.0, so every income
from 400.00% to 400.99% passed. The federal PTC gate ends at 400% under
current law, so the error showed only when a reform extends the federal
credit; test the exact ratio of nonnegative ACA MAGI to the prior-year
guideline anyway, so the state ceiling holds on its own.

Tests that supplied aca_magi_fraction now supply aca_magi against a
prior-year guideline of $10,000; new cases use the real 2025 guideline
at the edge and a reform that extends the federal credit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Read Colorado's 400% limit from the credit's poverty line

Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. Pin the test fixtures to aca_fpg and add
a joint return with a claimable spouse, whose ceiling follows the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
…atio (#10321)

* Decide ConnectorCare's ceiling and Plan Type bands on the exact FPL ratio

956 CMR 12.04(3)(b) assigns Plan Types by household income: "at or below
150%" (2A), "over 150% and not over 200%" (2B), "above 300% ... and not
over 400%" (3C). ConnectorCare compared the truncated aca_magi_fraction
with these edges, so incomes from 150.00% to 150.99% landed in 2A (and the
same slivers above 200%, 250% and 300% in the band below), and the 400%
gate admitted up to 400.99%. Use the exact ratio of nonnegative ACA MAGI
to the prior-year guideline for both, and evaluate the enrollee-premium
scale right-closed with thresholds at the band edges, so income exactly at
an edge stays in the lower band.

Tests that supplied aca_magi_fraction now supply aca_magi against a
prior-year guideline of $10,000; new cases use the real 2025 guideline at
each band edge and at 400%.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Read ConnectorCare's income limits from the credit's poverty line

Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above a limit
can't round down onto it. 956 CMR 12.03 and the Health Connector's subsidy
guides support the guideline year. The regulation's Household doesn't say
whether a filer who can be claimed on another return counts, so the comment
calls that point a modeling choice. Pin the test fixtures to aca_fpg and add
joint returns with a claimable spouse, whose limits and Plan Type follow the
one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
…atio (#10314)

* Decide Cascade Care Savings eligibility on the exact FPL ratio

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>

* Measure Cascade Care Savings income against the credit's poverty line

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>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
* Decide Covered Connecticut eligibility on the exact FPL ratio

C.G.S. 19a-754c(b)(1)(C)(iv) covers "household income up to one hundred
seventy-five per cent of the federal poverty level", which DSS applies
"up to an[d] including 175%". The gate compared the truncated
aca_magi_fraction with 1.75, so every income from 175.00% to 175.99%
passed. Test the exact ratio of nonnegative ACA MAGI to the prior-year
guideline instead.

Tests that supplied aca_magi_fraction now supply aca_magi against a
prior-year guideline of $10,000; new cases use the real 2025 guideline
at the edge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Measure Covered Connecticut income against the credit's poverty line

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 175%
can't round down onto the limit. Pin aca_fpg in the test fixtures for the
coverage year, and add joint-return cases where a claimable spouse leaves a tax
family of one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
DTrim99 added a commit that referenced this pull request Nov 19, 2026
…tio (#10320)

* Decide Maryland Premium Assistance's ceiling on the exact FPL ratio

MHBE's adopted PY2026 design provides "No state subsidy above 400% FPL"
and the PY2027 design "Eligibility: 400% FPL or below". The gate compared
the truncated aca_magi_fraction with 4.0, so every income from 400.00% to
400.99% passed. The federal PTC gate ends at 400% under current law, so
the error showed only when a reform extends the federal credit; test the
exact ratio of nonnegative ACA MAGI to the prior-year guideline anyway.

Seven amount cases supplied a fraction that disagreed with their own
aca_magi (for example "225% FPL" with $35,000, which is 223.6% of
$15,650). With the gate now reading MAGI, each case would have judged
eligibility and the target percentage on different incomes; their
incomes and expected amounts are recomputed so both agree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Read Maryland's 400% limit from the credit's poverty line

Divide ACA MAGI by aca_fpg, the prior-year guideline for the section 36B
tax family that the federal credit has used since #10041, instead of the
whole tax unit's guideline. Divide in float64 so a ratio just above the
limit can't round down onto it. COMAR 14.35.21.02B(3) and MHBE's income
thresholds support the guideline year; Maryland's rules don't define the
family counted, so the comment calls that part a modeling choice. Pin the
test fixtures to aca_fpg and add a joint return with a claimable spouse,
whose ceiling follows the one-person tax family.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: David Trimmer <david@policyengine.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants