Skip to content

Apply each state's rule for a Medicaid applicant whose spouse is not aged, blind or disabled - #10640

Merged
hua7450 merged 10 commits into
PolicyEngine:mainfrom
hua7450:medicaid-couple-limit-ineligible-spouse
Nov 12, 2026
Merged

hua7450 merged 10 commits into
PolicyEngine:mainfrom
hua7450:medicaid-couple-limit-ineligible-spouse

Conversation

@hua7450

@hua7450 hua7450 commented Nov 2, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes #10459
Fixes #10507

Changes since review, round 2 (2026-11-12)

  • The pathway's income test totals only the couple. is_optional_senior_or_disabled_income_eligible now uses spouses_sum, as the 209(b) and medically needy budgets do. When a household gives no marital units, an unrelated adult in the default marital unit no longer adds income to a couple's test. Two cases pin the default-unit code:
    • West Virginia, uses-couple-standard Case 18, pins the couple-standard helper. An unrelated 67-year-old doesn't count as the applicant's spouse, so the applicant is tested alone against $11,928.
    • Arizona, the new last case in is_optional_senior_or_disabled_income_eligible.yaml, pins the income test. The applicant's $9,760 is within the couple limit of $21,640. Adding the 67-year-old's $19,760 would give $29,520 and fail the applicant.
  • One main case is re-expected for that fix. In "California leaves another couple's dependent's premiums out of a couple budget" (medicaid_optional_senior_or_disabled_countable_income.yaml), the second couple has no income and now passes the pathway: $0 is within the couple limit of $29,863.20. The case's old comment put their failure down to the whole-unit sum. Its inputs are unchanged, and its first-couple comment now names the couple limit.
  • Minnesota is recorded as an open candidate, us-mn:abd-spouse-income-statute-vs-manual. The setting follows the state manual, which deems a spouse's income whenever the spouses live together. Minn. Stat. 256B.056, subd. 1a(a)(1) adopts SSI's methodologies instead. "Minnesota" under Limits gives an example, and a new "North Dakota" limit covers that state's pathway setting.
  • The stricter-than-SSI ruling is linked and pinned. us:medicaid-abd-budgeting-together-stricter-than-ssi now links the ruling comment. Uses-couple-standard Case 19 runs the candidate's example. The spouse's $5,964 of interest equals SSI's threshold, so SSI deems nothing. Arizona budgets the couple together and denies the applicant ($21,924 against $21,640). Pennsylvania follows SSI's rule and finds the applicant eligible ($15,960 against $15,960).
  • Medically needy Case 45 names SSI pools a married couple's income by December's facility status, so a part-year facility stay gives wrong SSI in the other months #10818. Its ssi_countable_income assertion stays out until Combine an SSI couple's income by each month's facility status #10820 merges. Until then SSI gives each spouse $31,320, where $20,880 is right.
  • Oklahoma's own-income difference has a size, under "Own-income test" in Limits.
  • Merged with main at 24939d2701. Main now holds Let Missouri aged, blind and disabled people who don't receive SSI spend down #10629, so the two PRs no longer conflict. In is_209b_ssi_recipient_income_eligible_for_medicaid, the parental medical expense share comes off inside the couple total, as in is_medically_needy_for_medicaid. In is_medically_needy_for_medicaid.yaml, main's Illinois Case 40 keeps its number, and this PR's cases move from 40-53 to 41-54. Every case number in this description is the new one.

Changes since review, 2026-11-11

  • Oklahoma follows SSI's rule, not budget together. OAC 317:35-7-40(1) tests the applicant's own income against the individual standard and both spouses' income against the couple standard. The model's version of SSI's rule differs from that test in two places: it has no own-income test once a spouse's income is deemed (see "Own-income test" under Limits), and it leaves out the couple test when the spouse's income is $497 a month or less, which changes a result only above about $473. Both stay in Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641. medicaid_optional_senior_or_disabled_uses_couple_standard.yaml Case 16.
  • Budget-together states keep SSI's allocation for ineligible children, except Missouri, whose manual bars it. Arizona's and Arkansas's own texts subtract one. Four of this PR's Massachusetts and Kansas cases become eligible (is_medically_needy_for_medicaid.yaml Cases 46 to 49), and two cases are new (deemed-income Case 7, medically needy Case 54).
  • Budgeting together outside the 209(b) states is ruled, 2026-11-10 (us:medicaid-abd-budgeting-together-stricter-than-ssi). The seven earlier candidates now carry readings, prs, the deciding parameter files and years.from: 2015.
  • The state settings and the 209(b) facility split are pinned: pathway Case 17 (15 states, with Montana tested alone), medically needy couple-standard Case 6 (13 states) and 209(b) Case 14.
  • Merged with main at 23a7c9a8f4. Main now totals a couple's spend-down budget through the SSI spouse test (Apply 416.1163(e)(2) to deemed SSI and identify SSI couples by marriage, not tax roles #10141), and this PR's formulas use those totals. The couple-standard helper also reads a couple that the spouse test finds inside a default marital unit of more than two people, which main's new cases need; two-person units are read as before. This PR's medically needy cases moved after main's new Cases 37 to 39. Case 45 drops its ssi_countable_income assertion, because main computes that figure month by month.
  • Description corrected after a law check, 2026-11-11, with no code change. The Oklahoma line above, and "Own-income test" and "Child allocations" under Limits. Later the same day, "Child allocations" moved Wisconsin to the states with no allocation found and added Hawaii to the states that count children in the unit size.

What and why

The model gave every married Medicaid applicant the couple limit, including someone whose spouse is not aged, blind or disabled and whose income SSI wouldn't deem. #10459 and #10507 proposed SSI's rule for these applicants. Research across 42 states found most states don't follow it, so this PR applies each state's own rule. The model uses a method other than SSI's rule in 19 of the 38 states in the aged, blind and disabled column below, and in 17 of the 32 states in the medically needy column.

Method Aged, blind and disabled pathway Medically needy
SSI's rule (default): tested alone unless the spouse's income is deemed (20 CFR 416.1163(d)) AR DC FL IA ID LA MT NC NJ NY OH OK OR PA UT VA WA WV, plus CA DC FL GA IA KY LA ME MT NC NY PA UT VA WA WV
Budget together: combined income against the couple limit, with no deeming threshold AK AZ CO CT HI IL IN MA MI MN MO ND NE NH SC VT WI AR CA CT HI IL KS MA MD MI MN ND NE NH VT WI
Couple limit without deeming: the couple limit always, with SSI's deeming of income ME RI NJ RI

North Dakota's 209(b) SSI recipients read the pathway's setting even though the state has no group for people not on SSI.

Changes:

  • New state settings, for each program: budgets_couple_together and couple_limit_without_deeming.
  • New variables: medicaid_optional_senior_or_disabled_uses_couple_standard, medicaid_medically_needy_uses_couple_standard and medicaid_medically_needy_income_from_spouse.
  • The income limits, the income tests, the 209(b) route and medically needy all read these settings.
  • medicaid_optional_senior_or_disabled_income_deemed_from_ineligible_spouse now reads budgets_couple_together. A budget-together state counts the spouse's income with no deeming threshold, after SSI's allocations for ineligible children (20 CFR 416.1163(b)). Missouri alone counts the spouse's gross income, because MHABD 0805.015.05 says "Do not consider the income and expenses of minor children".
  • medicaid_medically_needy_income_from_spouse adjusts ssi_countable_income. In a budget-together state it replaces SSI's deemed amount with the spouse's income after SSI's allocations for ineligible children, counted with no threshold, so one method applies at every income.
  • A facility splits a couple when exactly one member of any married couple is in a Medicaid-paid facility. Each spouse is then tested alone on their own income, and no spouse income counts under deeming or budgeting together (20 CFR 416.414(b)(3); 42 USC 1396r-5(a)(1), (b)(1), (h)(1)). In medically needy, the adjustment removes SSI's deemed amount, so it can be negative.
  • The model reads the facility status at December. A stay that changes within the year is tested on December's status for the whole year. On main, SSI's countable income is now computed month by month (Fix Missouri TANF grants, territory SNAP limits, Hawaii CCAP income and SSI food timing #10332), so for a part-year stay the year's income mixes the two (SSI pools a married couple's income by December's facility status, so a part-year facility stay gives wrong SSI in the other months #10818).
  • A spouse's medical expenses still reduce income when their income isn't counted (42 CFR 435.831(d)). After a facility split, each spouse deducts only their own.

A 70-year-old with $1,400 a month of countable income, and a 50-year-old spouse with no income, in 2026:

State Method Limit before Limit after Eligible before Eligible after
WV SSI's rule $1,491 $994 Yes No
AZ Budget together $1,803 $1,803 Yes Yes
RI Couple limit without deeming $1,803 $1,803 Yes Yes

Sources: each state's citation is in the parameter files. The quotes and what wasn't checked are in the research behind this PR. State plans weren't read, so this rests on state regulations and manuals.

Rulings: Ruled by the project lead, 2026-11-02. When a state's own rule differs from SSI's deeming rule, the model follows the state's rule. SSI's rule applies where the state follows it or is silent. On 2026-11-10 the project lead confirmed that this holds outside the 209(b) states too, where 42 CFR 435.601(d)(2) lets a state's methods be "less restrictive, but no more restrictive" than SSI's. Budgeting together is stricter than SSI's rule only in a narrow band, for example a spouse's income between $473 and $497 a month against poverty-level standards. Candidate us:medicaid-abd-budgeting-together-stricter-than-ssi. The six earlier rulings cover every state below except Hawaii.

State What the sources say The model follows Candidate
CO 10 CCR 2505-10 8.100.7.C.2 counts both spouses' income. 8.100.6.C.1.b defines the group by SSI eligibility. The express income rule: budget together. us-co:abd-spouse-income-ssi-defined-group
CT UPM 5020.75 and 5515.05 count the spouse. A 2023 DSS hearing decision on a Medicare Savings Program case (Request 203652) called that more restrictive than SSI. The manual: budget together. Connecticut is a 209(b) state. us-ct:abd-spouse-income-hearing-decision
HI HAR 17-1724.1-16(1): "The income of spouses living in the same residence shall be considered available to each other." HAR 17-1719-11.1(a)(2) and (a)(3) set the standards "for a household of applicable size", and nothing read defines that size. Under 20 CFR 416.1163(d)(1), the default, nothing is deemed at or below SSI's threshold. Chapter 17-1714.1 and the income chart couldn't be read. HAR 17-1724.1-16(1): budget together, in both settings. us-hi:abd-spouse-income-household-size
MA 130 CMR 520.002(A)(1) says "an income standard". Only 520.003(A)(2) names the couple limit, for assets. The couple standard for income: budget together. us-ma:abd-couple-income-standard
MD The Medical Assistance Manual, Section 600, uses a two-person unit. COMAR 10.09.24.06 counts the income but names only an aged, blind or disabled spouse as a unit member. Budget together. us-md:medically-needy-non-abd-spouse-unit
MT ARM 37.82.903(2) and 37.82.1107(1)(b) adopt SSI's rules. Manual CMA 603-1 considers both spouses' income with no threshold. The regulation: SSI's rule. us-mt:abd-spouse-deeming-threshold
NE 477 NAC 24 sizes the unit with both spouses. 477 NAC 25-002.03(B) says the program follows SSI methodology. The specific rule: budget together. us-ne:medically-needy-unit-size

Limits:

  • Own-rule states. AK, NY, OK and CA's aged, blind and disabled groups, and GA, KY, NC, NY and WA medically needy, have rules of their own. This PR gives them the closest method, and Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 tracks the differences. For Oklahoma the closest method is SSI's rule; its two-part test is not modeled. WA keeps its one-person medically needy limit.

  • Own-income test. SSI's rule has a first step that the model doesn't apply. POMS SI 01320.400 A says "For spouse-to-spouse deeming to apply, the SSI applicant or recipient must be eligible based on their own income", and 20 CFR 416.1163(e)(2) says the result under deeming "cannot be higher than it would be if deeming did not apply". N.J.A.C. 10:72-4.4(d)1 states it for this pathway: "If the countable income (before income deeming) of the aged, blind, or disabled individual exceeds the poverty income guideline for one person he or she is ineligible for benefits and income deeming does not apply." In the states on SSI's rule, once a spouse's income is deemed the model tests only the couple's combined income against the couple limit. A New Jersey 70-year-old with $1,500 a month of Social Security, whose 50-year-old spouse earns $700, has $1,480 of own countable income, above the one-person $1,330, so that rule gives not eligible. The model counts $1,480 + ($700 - $65) / 2 = $1,797.50 against the two-person $1,803.33 and passes the income test (by code trace, not run). main gives the same result, so this PR doesn't change it; Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 tracks the test. In Oklahoma, whose standards are $1,330 and $1,803.33 a month, a working spouse adds only (wages - $65) / 2. At spouse wages just over $497 a month, the model passes own countable income up to about $1,587 a month, about $257 above the individual standard. The gap closes at spouse wages of about $1,012.

  • Iowa, Maine and Idaho. Ruled by the project lead, 2026-11-02: Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 tracks these, and this PR doesn't change them.

    • Iowa: Employees' Manual Title 8, Chapter J says a spouse with no income to deem "is not a responsible relative", while the model deducts that spouse's bills in every state under 42 CFR 435.831(d). The ruling follows Iowa's manual, and a state setting waits for a survey of other states.
    • Maine: the medically needy setting is SSI's rule by default because 10-144 C.M.R. ch. 332, 10-3 doesn't state the family size. The aged, blind and disabled setting reads section 7-4 as a couple limit.
    • Idaho: IDAPA 16.03.05 sections 761-766 allow a community property method in some cases. The model has no input for separate or community income.
  • Minnesota. The setting follows Minnesota's eligibility manual in both programs: "Except in the situations noted below, the income of a spouse is deemed to a person if the spouses live together" (EPM 2.3.3.3.2.1.1). Minn. Stat. 256B.056, subd. 1a(a)(1) adopts SSI's methodologies for these groups. The open candidate us-mn:abd-spouse-income-statute-vs-manual records the conflict, and the model follows the manual pending a ruling. A 70-year-old with $16,800 of Social Security and a spouse with no income has $16,800 of countable income, because Minnesota deducts no $20 disregard (subd. 1b). That is within the two-person $21,640 budgeted together, and above the one-person $15,960 tested alone.

  • North Dakota. No North Dakota text read gives a couple standard for the pathway setting. The setting reaches only SSI recipients on the 209(b) route, and at SSI's own standard both methods pass them, so no household result is expected to turn on it (arithmetic, not run). Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 tracks it.

  • Child allocations. The model applies SSI's allocation for ineligible children (20 CFR 416.1163(b)) in every budget-together state except Missouri, whose manual bars it. The states' own texts, re-read on 2026-11-11, are not all silent on children:

    • An allocation off the spouse's income: Alaska (APA Manual 460-5), Arkansas (MS O-531 step 3, read directly on 2026-11-11), Colorado (10 CCR 2505-10 8.100.5.H), Indiana (405 IAC 2-3-20) and Michigan (BEM 541). The amounts weren't compared with SSI's, and Arkansas's "living allowance" is in an appendix that wasn't read.
    • An allocation off the couple's total: Arizona (AHCCCS MA611 A step 4) subtracts it from the couple's total net income, not from the spouse's income, so it can exceed SSI's when the spouse has little income.
    • Children counted in the unit size instead: California (22 CCR 50603(a)(3)), Illinois (PM 15-06-02-c: "use the standard for the total number of persons in the home for whom they are responsible") and Nebraska (its appendix 477-000-009 tests a disabled father "at 100% FPL for five"). Hawaii probably belongs here too: its standards are "for a household of applicable size" (HAR 17-1719-11.1), and HAR 17-1724.1-16(6) leaves out a child's "income and needs" only "if a child is not included as part of the household". No definition of the household was found, so this reading is uncertain.
    • No allocation: Connecticut's method (UPM 5020.70 C.3) deems the spouse's gross unearned income and applied earned income. None was found in the sections read for Kansas, Maryland, Massachusetts, Minnesota, North Dakota or Wisconsin, whose fiscal test groups "are groups of one or two" (MEH 15.1.1). New Hampshire allocates only on request, at another standard (He-W 654.21).

    So SSI's allocation is the state's own rule only in the first group, and none of the other treatments is modeled. The Massachusetts and Kansas cases rest on 130 CMR 520.002(A)(1) and MKEESM 4312, which count the spouses' total income and don't mention allocations.

  • Facility splits.

    • The 30-consecutive-day test in 42 USC 1396r-5(h)(1) isn't modeled.
    • The facility input covers Medicaid-paid stays only.
    • A spouse who isn't aged, blind or disabled and is in a facility also splits the couple, so the applicant at home is tested alone. 1396r-5(b)(1) protects the institutionalized spouse, and no source was checked for this direction.
    • HAR 17-1724.1-16(2) counts income one spouse actually contributes to the other after a split, and the model doesn't.
    • Spouses both in a facility stay a couple, while 130 CMR 520.002(B)(1) says their income and assets "are not mutually available". Other states weren't checked.
    • A year's result can differ from a month-by-month rule. A New Jersey facility resident with $7,760 of countable income passes alone against $15,960 in January through June, and the model gives not eligible for the year because the couple is home in December. This example was measured at the earlier head and not remeasured after the merge with main.
    • SSI's own deeming still applies to a facility resident whose spouse isn't aged, blind or disabled (ssi_countable_income, so ssi and the SSI_RECIPIENT route). Split couples still pool assets. ms_hmw_income_eligible tests a split couple's countable income against its own two-person limit.
  • Dates. The settings start in 2015 because the sources don't date each state's rule.

  • Population effect. It hasn't been estimated.

Test plan

  • For policy changes: 49 new cases, with expected values worked by hand from each state's rule and the 2026 poverty guideline: 19 in medicaid_optional_senior_or_disabled_uses_couple_standard.yaml, 6 in medicaid_medically_needy_uses_couple_standard.yaml, 14 in is_medically_needy_for_medicaid.yaml (Cases 41 to 54), 4 in is_209b_ssi_recipient_income_eligible_for_medicaid.yaml, 3 in medicaid_category.yaml, 2 in medicaid_optional_senior_or_disabled_income_deemed_from_ineligible_spouse.yaml and 1 in is_optional_senior_or_disabled_income_eligible.yaml. They cover part-year facility stays, couples with an ineligible child on both sides of SSI's threshold, Arizona's and Arkansas's child allocations, Oklahoma, every state setting, facility residents with a spouse who isn't aged, blind or disabled, the 209(b) route and its facility split, both Hawaii settings, the final category for the WV, AZ and RI example, an unrelated aged adult in a default marital unit, and the stricter outcome of budgeting together. One existing case's expected value changes: in main's "California leaves another couple's dependent's premiums out of a couple budget", the second couple now passes the pathway. Four comments in cases main added on 2026-11-10 now name the couple limit, which this PR applies to a couple found inside a default marital unit.
  • If this PR takes a reading where sources disagree: eight state: ruled candidates are in source_conflicts/candidates.yaml (CO, CT, HI, MA, MD, MT and NE, and the general one on budgeting together outside the 209(b) states), and one state: open candidate, us-mn:abd-spouse-income-statute-vs-manual. The rulings above state each ruled one, and "Minnesota" under Limits states the open one. There are no register entries or markers yet.
  • make format (ruff format on the changed variables)
  • Changelog fragment in changelog.d/

Before the merge with main at 24939d2701, the tests for the round-2 fixes passed locally (145 passed). On that merge, the PR's nine changed test files and three of #10629's test files were run one process at a time: 321 passed. Other suites were not run locally; CI validates.

axiom: TheAxiomFoundation/rulespec-us#2012 queued

🤖 Generated with Claude Code

hua7450 and others added 2 commits November 2, 2026 18:30
…aged, blind or disabled

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

hua7450 commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator Author

Rulings by the project lead on the source conflicts in this PR, 2026-11-02.

General rule: when a state's own rule differs from SSI's deeming rule, the model follows the state's rule. SSI's rule applies where the state follows it or is silent.

State Conflict Ruling
MT ARM 37.82.903(2) and 37.82.1107(1)(b) adopt SSI's rules. Manual CMA 603-1 considers both spouses' income with no threshold. Follow the regulation: SSI's rule.
CO 10 CCR 2505-10 8.100.7.C.2 counts both spouses' income. 8.100.6.C.1.b defines the group by SSI eligibility. Follow the express income rule: budget together.
CT UPM 5020.75 and 5515.05 count the spouse. A 2023 DSS hearing decision on a Medicare Savings Program case (Request 203652) called that more restrictive than SSI. Follow the manual: budget together. Connecticut is a 209(b) state.
MD The Medical Assistance Manual, Section 600, uses a two-person unit. COMAR 10.09.24.06 counts the income but names only an aged, blind or disabled spouse as a unit member. Budget together.
NE 477 NAC 24 sizes the unit with both spouses. 477 NAC 25-002.03(B) says the program follows SSI methodology. Follow the specific rule: budget together.
MA 130 CMR 520.002(A)(1) says "an income standard". Only 520.003(A)(2) names the couple limit, for assets. Use the couple standard for income: budget together.

Scope: this PR covers SSI's rule, budgeting together and the couple limit without deeming. A follow-up issue tracks the states with rules of their own.

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

hua7450 commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator Author

The follow-up for the states with rules of their own is #10641.

hua7450 and others added 2 commits November 2, 2026 22:18
Give CO, MA and NE candidates a second source, which clears the failing CI
check. A couple split by a facility counts no spouse income (42 USC 1396r-5),
read at the same instant as the income it gates. Medically needy budget-together
uses one method at every income. Hawaii budgets a couple together.

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

DTrim99 commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

PR Review: Apply each state's rule for a Medicaid applicant whose spouse is not aged, blind or disabled

PR #10640 (author: hua7450), head 37d23c83c6. The branch is 6 commits ahead of main and 95 behind. The diff covers 22 files: four new state-keyed boolean parameters, three new variables, a helper module (_couple_standard.py), 40 new YAML cases and seven source-conflict candidates. No partner test file is touched.

Path prefixes used below:

  • P/ = policyengine_us/parameters/gov/hhs/medicaid/eligibility/categories/
  • V/ = policyengine_us/variables/gov/hhs/medicaid/
  • T/ = policyengine_us/tests/policy/baseline/gov/hhs/medicaid/

Summary

What works. The federal default is right, and the facility split rests on the right federal law:

  • Federal default. 20 CFR 416.1163(d)(1) and (d)(2) are encoded correctly. If the spouse's income after allocations is "not more than" the couple-minus-individual FBR difference, nothing is deemed and the applicant is tested alone. Above that amount, the couple is tested together.
  • Facility split. It cites 20 CFR 416.414(b)(3) and 42 USC 1396r-5(b)(1).
  • Code. The code is vectorized. The new parameters are keyed by state_code_str and list all 51 jurisdictions, so the NH Add New Hampshire state supplementation for 2026 #10156 pattern doesn't arise.
  • Tests. All 40 new cases hand-check, and CI is green (34/34).

What needs to change. Two state settings give wrong results against the sources the PR itself cites, and I reproduced both on the head:

  • Oklahoma. OAC 317:35-7-40(1) adds an own-income test. The model drops that test, so the PR's own headline household comes out eligible in Oklahoma, while the regulation makes it ineligible.
  • Child allocations. Arizona's MA611 A (aged, blind and disabled pathway) and Arkansas's MS O-531 (medically needy) budget the couple together but subtract an allocation for each ineligible child. The model drops that allocation in every budget-together state. In Arizona this is a regression: a household the old code passed now fails.

Should address. There are three items:

  • In the non-209(b) states, budgeting together is sometimes more restrictive than SSI's rule (42 CFR 435.601(d)(2)-(3)), and that regulation-versus-manual choice isn't recorded.
  • The seven candidates lack readings and prs, and most point at the wrong file.
  • The ruled readings for CO, CT, MD, MT and NE, and many of the per-state flags, are pinned by no test.

The axiom line is valid for this head.

Critical (must fix)

C1. Oklahoma is marked "budget together", but its cited rule adds an own-income test.

  • Where. P/senior_or_disabled/income/budgets_couple_together.yaml:131 (OK: true). The file's own reference at line 49 is OAC 317:35-7-40.
  • What the rule says. OAC 317:35-7-40(1) (revised 09-14-20): "For an individual whose spouse is not eligible for Medicare, total countable income of the eligible individual must be equal to or less than the QMBP standards for an individual, and the income of both must be equal to or less than the QMBP standards for a couple." The test is two-part. Budgeting together keeps only the second part.
  • Reproduced on the head. Take the PR's own example household in Oklahoma, 2026: an applicant aged 70 with Social Security of $16,800 ($1,400 a month) and a spouse aged 50 with no income.
    • Model. uses_couple_standard is true, countable income is 16,800 - 240 = 16,560, the limit is 21,640, so is_optional_senior_or_disabled_income_eligible is true.
    • Under the rule. Own income of 16,560 is above the individual standard of 15,960 ($1,330 a month), so the applicant is ineligible.
  • Why SSI's rule is closer. Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 says Oklahoma was given "the closest method", but SSI's rule is the closer one. With spouse income s a month after allocations:
    • At or below $497. SSI's rule tests own income against $1,330, which is the rule's first part. The two differ only for s between $473 and $497 ($1,803 - $1,330 = $473).
    • Above $497. Under SSI's rule, combined income at or under $1,803 already forces own income below $1,306, so the rule's first part always holds.
    • Budgeting together. This passes anyone whose own income falls between $1,330 and $1,803 - s.
  • Fix. Set OK: false, which gives SSI's rule and matches the regulation except in that $24 band. Or encode the own-income pretest now. Add an Oklahoma case such as the one above (expected: not eligible), and update the Oklahoma row in Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 and in rulespec-us#2012.

C2. Budgeting together drops the ineligible-child allocation, even in states whose sources subtract it.

  • Where.
    • V/income/deemed/from_ineligible_spouse/medicaid_optional_senior_or_disabled_income_deemed_from_ineligible_spouse.py:55-65 replaces SSI's post-allocation spouse income with the spouse's gross income in every budget-together state.
    • V/eligibility/categories/medically_needy/medicaid_medically_needy_income_from_spouse.py:43-58 does the same for medically needy.
    • Before this PR, gross income replaced the post-allocation amount only in Missouri, whose manual (0805.015.05) bars allocations.
  • What the sources say.
    • Arizona. AHCCCS MA611 A, "Calculation for Customer and Spouse", step 4: "Calculate a child allocation amount for each of the customer's children and the customer's spouse's children living in the home ... subtract from the total net income". Step 7 repeats the allocation before the FPL test.
    • Arkansas. MS O-531 (file page 424), step 3: "From the ineligible spouse's income, deduct a living allowance for each ineligible child in the home". Step 4 then totals the result with the applicant's income "as for an eligible couple", and step 6 compares it to the two-person MNIL. I opened the manual and confirmed this text and the page anchors.
    • Federal rule. SSI's own methodology also subtracts the allocation (20 CFR 416.1163(b)). Arizona is not a 209(b) state, so 42 CFR 435.601(d)(2)-(3) bars a method more restrictive than SSI's.
  • Reproduced on the head. Arizona, 2026: an applicant aged 70 with Social Security of $16,000, a spouse aged 50 with interest of $6,000, and one child aged 10.
    • Model. It deems 6,000, countable income is 16,000 + 6,000 - 240 = 21,760, above 21,640, so the applicant is not income eligible.
    • Under MA611 A. 21,760 - 5,964 (12 x $497 for the child) = 15,796. That is within the couple FBR of 17,892 at step 5, so the applicant is eligible.
    • Under the previous code (and under SSI). 6,000 - 5,964 = 36 is at or under 5,964, so nothing is deemed: own income of 15,760 passed.
    • So for this household the PR turns a correct "eligible" into a wrong "not eligible".
  • Fix. The post-allocation amounts already exist: ssi_earned_income_deemed_from_ineligible_spouse and ssi_unearned_income_deemed_from_ineligible_spouse. In a budget-together state, use them and drop only the threshold. Swap in gross income only where the state bars allocations, for example through a state parameter that is true for MO and for any state shown to bar them. Massachusetts and Kansas currently rest on texts that "don't mention allocations", and the PR body says the rest of those manuals wasn't checked. Add an Arizona case like the one above and an Arkansas medically needy case with a child, and update the "Child allocations" limit and rulespec-us#2012's "Out of scope" line.

Should address

S1. In non-209(b) states, budgeting together is sometimes more restrictive than SSI's rule, and that choice isn't recorded.

  • Federal rule. 42 CFR 435.601(d)(2)(i) lets a state's methodology for aged, blind and disabled groups be "less restrictive, but no more restrictive (except in States using more restrictive requirements than SSI), than ... the SSI methodologies". Paragraph (d)(3) adds: "no individuals who are otherwise eligible are by use of that methodology made ineligible". 42 CFR 435.602(b) permits wider relative responsibility only in 209(b) states.
  • Reproduced on the head. Take an applicant aged 70 with Social Security of $16,200 and a spouse aged 50 with interest of $5,964 (at SSI's threshold).
    • Arizona (budget together). Countable income is 21,924 against a limit of 21,640: not eligible.
    • Pennsylvania (SSI's rule). The applicant is tested alone, at 15,960 against a limit of 15,960: eligible.
  • Which states.
    • In the pathway, every non-209(b) budget-together state: AK, AZ, CO, IN, MA, MI, NE, OK, SC, VT and WI.
    • In medically needy: AR, CA, KS, MA, MD, MI, NE, VT and WI.
  • The gap. The 2026-11-02 ruling ("When a state's own rule differs from SSI's deeming rule, the model follows the state's rule") decides this. Still, it is a regulation-versus-manual choice under CONTRIBUTING.md#source-conflicts, and no candidate records it. The seven candidates cover only conflicts within a state.
  • Fix. Add one candidate, or one per state, that records 435.601(d)(2)-(3) against the state rules and links the ruling. Or have the project lead confirm that the ruling covers it.

S2. The seven candidates are incomplete under CONTRIBUTING.md step 1.

  • Missing fields. Step 1 lists readings and pe_us.prs. None of the seven has readings or prs; all 381 candidates on main have readings. The guard doesn't check either field, which is why CI passes.
  • Wrong code path. CO, CT, MA, MD, MT and NE list pe_us.code: _couple_standard.py. That file holds no state's deciding line: the decision is the state's entry in the budgets_couple_together.yaml files. Step 3 will mark the deciding line in each listed file. Hawaii's candidate already lists the two parameter files, and the others should do the same.
  • Years. Each candidate covers only 2026, but the settings start on 2015-01-01 and apply in every year.

S3. Ruled readings and most per-state flags are unpinned (mutation rule).

  • Ruled readings. CONTRIBUTING.md step 1 says the ruling PR adds "the YAML test cases for its reading". CO (pathway), CT (both), MD (medically needy), MT (both, SSI's rule) and NE (medically needy) have no case. Flipping any of those values fails no test. HI and MA are pinned.
  • Other flags.
    • ME: true in the pathway's couple_limit_without_deeming has no case.
    • In the pathway's budgets_couple_together, only AZ, HI, MO and ND (209(b)) are exercised. Michigan Case 11 is a facility split, which overrides the flag.
    • In the medically needy file, only MA, KS and HI are exercised.
    • One two-person household per remaining true state, asserting *_uses_couple_standard and the limit, would pin them cheaply.
  • 209(b) split branch. V/eligibility/categories/is_209b_ssi_recipient_income_eligible_for_medicaid.py:41-45 (where(split, own expenses, couple expenses)) is unpinned, because the only split case in that file, Case 13 (T/.../is_209b_ssi_recipient_income_eligible_for_medicaid.yaml:263), has no medical expenses. Add an expense for the community spouse there.

Suggestions

Verified correct

  • Federal default.
    • uses_couple_standard tests an applicant alone exactly when the applicant is aged, blind or disabled, married, has a spouse who is not, and is_ssi_spousal_deeming_applies is false. That variable compares post-allocation spouse income to 12 x (1,491 - 994) = 5,964 with >, matching 416.1163(d)(1)'s "not more than".
    • The facility split is checked first.
    • The non-aged spouse "stays with the couple" but has no countable income in the pathway, and is_medically_needy_for_medicaid requires aged, blind or disabled status, so that has no effect.
  • Downstream readers.
    • Income limits. medicaid_optional_senior_or_disabled_income_limit and medicaid_medically_needy_income_limit both read the new flags.
    • Income eligibility. The income test sums the marital unit only under the couple standard. Under the couple computation, medicaid_optional_senior_or_disabled_countable_income already halves combined income, so the sum is the couple's total.
    • Medically needy adjustment. In a budget-together state, medicaid_medically_needy_income_from_spouse replaces SSI's deemed amount with SSI-exclusion combined-minus-alone. The result doesn't jump at the threshold: in Case 43, 42,438 + 2,982 = 39,760 + 5,660.
    • No reinvented variables. The new variables reuse ssi_countable_income, ssi_income_deemed_from_ineligible_spouse, is_ssi_spousal_deeming_applies, is_ssi_ineligible_spouse and _apply_ssi_exclusions.
  • Facility law.
    • 42 USC 1396r-5(b)(1): "no income of the community spouse shall be deemed available to the institutionalized spouse". Paragraph (a)(1) supersedes inconsistent provisions.
    • 20 CFR 416.414(b)(3) computes each spouse separately.
    • 42 CFR 435.831(d) deducts "medical expenses incurred by the individual or family or financially responsible relatives". The model does this for a spouse whose income isn't counted, and only for each spouse's own expenses after a split.
    • The December read of ssi_federal_living_arrangement matches ssi_couple_computation_applies, and part-year Cases 12 and 41 pin it.
  • Federal text checked.
    • 42 CFR 435.602(a)(2)(i)-(iv) and (b)-(c), and 435.601(b)-(d), from eCFR.
    • 42 CFR 435.723 and 435.724 don't exist in the current CFR, so the governing federal text is 435.601-602 with 20 CFR 416.1160-1163.
    • 42 CFR 435.121(a)(2) lets 209(b) states use their 1972 plan rules, and 435.602(b)(2) allows wider relative responsibility there, so budgeting together is permissible in the 209(b) states CT, HI, IL, MN, MO, ND and NH. Virginia, also a 209(b) state, follows SSI's rule here.
  • State spot-checks (14 states, prioritizing departures from SSI):
State Setting Source checked Result
AZ Pathway: budget together MA611 A: customer and spouse totaled, couple FBR and couple FPL Method correct; child allocation missing (C2)
OK Pathway: budget together OAC 317:35-7-40(1): own and combined tests Contradicted (C1)
MI Both: budget together BEM 211 p. 8: "the fiscal and asset group is the adult applicant and the spouse" Correct; the anchor shows the text
WI Both: budget together MEH 15.1: "Spouses who live together are in each other's FTG ... The FTG size ... is two" Correct
IN Pathway: budget together 405 IAC 2-3-4: "his or her income includes the income of his or her spouse" Correct
MN Both: budget together EPM 2.3.3.3.2.1.1: "the income of a spouse is deemed to a person if the spouses live together" Correct
SC Pathway: budget together MPPM 303.06.01: "a couple case if both spouses reside together, even if only one is applying" Correct
NH Both: budget together He-W 854.02(c): "The countable gross earned incomes of the applicant and nonapplicant spouse shall be combined" Correct
IL Both: budget together PM 15-06-02-c: "always use the 2-person standard ... regardless" Correct (see G2)
KS Medically needy: budget together KEESM 4312: "The total income and resources of both spouses shall be considered" Correct
ND Budget together (209(b)) 75-02-02.1-34(2), file page 70: spouse income "considered available ... even if ... not actually contributed" Correct; anchor right
RI Both: couple limit without deeming 210-RICR-40-05-1 1.11.2(A)(2): "a 'couple' or group of two ... whether or not the applicant's spouse is also requesting Medicaid"; 1.11.5(C) deems above the FBR-difference standard Correct
NJ Medically needy: couple limit without deeming N.J.A.C. 10:70-3.5(c)2: "a budget unit of two" "whether or not the spouse is program eligible" Correct
AR Medically needy: budget together MS O-531, pages 424-425: no threshold, two-person MNIL Method correct; child allocation missing (C2)
  • Hand-checks (2026: FPL 15,960/21,640, Hawaii 18,360/24,890; FBR 994/1,491; annual exclusion 240; earned exclusion 780 before halving):
    1. Couple file Case 2 (WV). 14,640 - 240 = 14,400 > 11,928 (12 x 994) → [false, true]; limits [11,928, 17,892] ✓.
    2. Cases 3-4 (WV threshold). 5,964 is not more than 5,964, so no deeming; 5,965 deems, giving a couple limit of 17,892 ✓.
    3. Case 6 (MO). ceil(0.85 x 21,640 / 12) = ceil(1,532.83) = 1,533 → 18,396 ✓.
    4. Case 12 (NJ, December status). (8,000 + 22,000 - 240) / 2 = 14,880 each; 29,760 > 21,640 → not eligible ✓.
    5. Case 13 (AZ facility). 15,000 - 240 = 14,760 ≤ 15,960; deemed 0 although SSI deems ✓.
    6. Case 15 (HI). 12,000 + 5,000 - 240 = 16,760 ≤ 24,890; SSI: 11,760 < 11,928 → SSI_RECIPIENT ✓.
    7. 209(b) Case 11 (VA). 0.8 x 15,960 = 12,768 and 0.8 x 21,640 = 17,312; 9,360 ≤ 12,768 ✓.
    8. 209(b) Case 12 (ND). 10,000 + 5,000 - 240 = 14,760 ≤ 17,892 ✓.
    9. Medically needy Case 38 (NY). 27,760 - 5,000 - 1,000 = 21,760 ≤ 22,032 (12 x 1,836) ✓.
    10. Medically needy Case 39 (MA). 19,760 + (4,800 - 780) / 2 = 21,770; minus 14,000 = 7,770 ≤ 7,800 (12 x 650); adjustment 2,010 ✓.
    11. Medically needy Case 43 (MA, child). 12,100 - 5,964 = 6,136 > 5,964; SSI deems (6,136 - 780) / 2 = 2,678; budgeting together gives (12,100 - 780) / 2 = 5,660; adjustment 2,982; 42,438 + 2,982 - 35,000 = 10,420 > 7,800 ✓.
    12. Medically needy Case 45 (KS, two children). 18,000 - 11,928 = 6,072 → deemed 2,646; budgeting together gives 8,610; adjustment 5,964; 22,406 + 5,964 - 6,000 = 22,370 > 17,892 ✓.
    13. Medically needy Case 47 (MA facility). Deemed (20,000 - 780) / 2 = 9,610, adjustment -9,610; 19,760 - 14,000 = 5,760 ≤ 6,264 ✓.
    14. Medically needy Case 48 (NY split). 23,000 - 240 - 100 = 22,660 > 22,032 and 30,000 - 240 - 8,000 = 21,760 ≤ 22,032 ✓.
    15. Category Cases 15-17. 16,800 against 11,928 (WV), 21,640 (AZ) and 21,640 (RI) → NONE, SENIOR_OR_DISABLED, SENIOR_OR_DISABLED ✓.
  • References. Both PDF ranges follow the house rules: "#page 424-425" is the Arkansas range, and Vermont's "#page 14,52" lists two nonconsecutive pages. Each href opens the first page. There is one entry per source document, and the parameter descriptions follow the boolean template.
  • Housekeeping.
    • The changelog fragment changelog.d/medicaid-couple-limit-ineligible-spouse.fixed.md is top-level, with a sensible type.
    • Tests are in variable-named files, and no Python tests were added.
    • No existing expected value changes; every hunk only adds.
  • Source-conflict guard. No added comment matches CONFLICT_COMMENT_RE. All seven candidate ids are well-formed and unique in the merged tree. Every field the guard checks is valid.

Axiom line assessment

axiom: TheAxiomFoundation/rulespec-us#2012 queued is valid for this head:

  • Issue state. rulespec-us#2012 is OPEN, labelled pe-parity, created 2026-11-02 and updated 2026-11-03.
  • Matches the head. It names head 37d23c83c6 and its 40 cases. It lists the module paths and corpus citations, quotes the law verbatim (416.1163(d), 1396r-5, 416.414(b)(3), and the state texts), and gives the required outputs.
  • Dispatch-ready. Its companion tests are derived by hand from the same state and federal sources as the YAML tests. It records the blockers: sources missing from the bundles, unapproved billed runs, and no merged revision.
  • After the fixes. C1 changes Oklahoma's method and C2 adds child allocations, so the issue's state table, the AZ/AR companion rows and the "Out of scope: child allocations" line will need updating.

CI status

All 34 checks pass at head 37d23c83c6 (re-checked just now; none pending).

I ran one probe of four households on the head, using policyengine-core 3.33. It confirmed the C1, C2 and S1 figures above, with no unexpected values for any applicant.

Branch status

The branch is 95 commits behind main. git merge-tree --write-tree PolicyEngine/main 37d23c83c6 merges cleanly (tree 238c1129dd).

  • Main-side changes to Medicaid files since the merge base. Only Add 2015-2023 Medicare IRMAA brackets and 2015-2020 Part B premiums #10112 changed one: it removed a two-line NOTE comment from medicaid_optional_senior_or_disabled_countable_income.py, which this PR doesn't touch.
  • Code-health guards. Main changed test_source_conflicts.py (KNOWN_UNMARKED wording and lines) and candidates.yaml (+1,591 lines). Neither affects this PR: it adds no conflict-sounding comments, and its candidate ids stay unique.
  • Main-side tests. No test added on main since the merge base reads Medicaid eligibility for a couple with one aged, blind or disabled spouse.

Sibling notes (not findings):

Verdict: REQUEST_CHANGES

@DTrim99 DTrim99 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.

Requesting changes per the review above: 2 critical (OK own-income test; budget-together drops the ineligible-child allocation in AZ/AR), 3 should, 6 suggestions.

hua7450 and others added 2 commits November 11, 2026 19:36
…geting together

OAC 317:35-7-40(1) tests the applicant's own income against the individual
standard as well as the couple's against the couple standard, so Oklahoma
follows SSI's rule, the closer method, not budgeting together.

A state that budgets a couple together now keeps SSI's allocations for
ineligible children (20 CFR 416.1163(b)) and drops only the deeming threshold,
as Arizona's MA611 A and Arkansas's MS O-531 do. Missouri alone counts the
couple's gross income (MHABD 0805.015.05).

Tests: Oklahoma, Arizona and Arkansas cases; Massachusetts and Kansas Cases 42
to 45 re-expected; one household per state pins every couple-rule flag; a
209(b) case pins the facility split in the expense deduction.

source_conflicts/candidates.yaml: the seven candidates gain readings, prs and
the deciding parameter files, and a new ruled candidate records 42 CFR
435.601(d)(2)-(3) against the state rules outside 209(b) states.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…into medicaid-couple-limit-ineligible-spouse

Main now totals a couple's spend-down budget through the SSI spouse test
(PR 10141). In the 209(b) and medically needy formulas, keep this branch's
couple-standard switch, facility rule and spouse-income adjustment, and
total a couple with main's helpers through couple_budget_total. In the
spouse-deeming formula, use main's couple totals for the spouse's gross
income and keep this branch's budget-together and facility rules.

Main's new cases put a couple and an unrelated adult in one default marital
unit. The couple-standard helper read a couple only from a two-person
marital unit, so those spouses were each tested alone. It now also reads a
pair that the SSI spouse test finds inside a larger unit. Two-person units
are read as before.

Tests: keep main's medically needy Cases 37 to 39 and renumber this branch's
cases 40 to 53. Three comments in main's cases now name the couple limit,
which this branch applies to those couples. Case 44 drops its
ssi_countable_income assertion: main computes it month by month, so the
year no longer equals the December-status figure.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@hua7450

hua7450 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator Author

Ruling by the project lead, 2026-11-10. The general rule of 2026-11-02 applies outside the 209(b) states too: where a state's own rule differs from SSI's deeming rule, the model follows the state's rule, including where that is stricter than SSI's rule in a narrow band (42 CFR 435.601(d)(2)-(3)).

@hua7450

hua7450 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator Author

Ready for another look. Your change requests of 5 November are covered under "Changes since review, 2026-11-11" at the top of the description:

  • Oklahoma follows SSI's rule, not budgeting together.
  • Budget-together states keep SSI's allocation for ineligible children, except Missouri.
  • Budgeting together outside the 209(b) states is ruled, in the comment above, and the seven earlier candidates carry their readings, PR links, deciding parameter files and years.
  • The state settings and the 209(b) facility split are pinned.
  • The branch is merged with main at 23a7c9a8f4, and all 36 checks pass.

A law check on 11 November corrected the description with no code change. It adds the missing own-income test as a limit and groups the budget-together states by how their own texts treat children. #10641 tracks both. This PR and #10629 still conflict with each other, so whichever merges second takes main again.

@hua7450
hua7450 requested a review from DTrim99 November 12, 2026 16:15
@DTrim99

DTrim99 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

PR Review (round 2): Apply each state's rule for a Medicaid applicant whose spouse is not aged, blind or disabled

PR #10640 (author: hua7450), head 27ca507758, re-review requested on 2026-11-12. Round 1 was at 37d23c83c6 (request changes: 2 critical, 3 should, 6 suggestions). Since then the branch has one fix commit (cbefa07bd1) and one merge of main at 23a7c9a8f4. The diff is 23 files, +2,924/-34. No partner test file is touched.

Path prefixes used below:

  • P/ = policyengine_us/parameters/gov/hhs/medicaid/eligibility/categories/
  • V/ = policyengine_us/variables/gov/hhs/medicaid/
  • T/ = policyengine_us/tests/policy/baseline/gov/hhs/medicaid/

How each claim below was checked is stated with it: run (executed on the head with policyengine-core 3.33), hand trace (arithmetic or code read by hand) or reading (the tests or the source text).

Summary

Both criticals and all three should items from round 1 are fixed, and each fix is pinned.

  • Oklahoma now follows SSI's rule, and Case 16 pins it.
  • Child allocations are kept in budget-together states, with Missouri the one exception. Arizona and Arkansas cases pin this.
  • The ruling of 2026-11-10 is recorded as a candidate, and the code follows it.
  • The seven earlier candidates are complete.
  • Every state setting is pinned. I flipped each one in memory and reran the cases for that state: all 36 true settings fail a test when flipped.

Two new should items remain, both small.

  • Minnesota. The author's own law check found that Minnesota's setting follows the manual against a statute. Issue Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 says so and says it "has no candidate entry". The PR records nothing.
  • Default marital units. The merge commit added code that finds a couple inside a default marital unit of three or more people. One branch of it is pinned by no test, and the pathway's income test still sums the whole unit.

The merge is sound. All seven hand-resolved files combine both parents correctly. Dropping Case 44's ssi_countable_income assertion does hide a wrong value (31,320 each, where 20,880 is right), but the cause is on main (#10818) and this PR doesn't touch it.

Prior findings

Finding Status Evidence
C1. Oklahoma marked "budget together" against OAC 317:35-7-40(1) Fixed P/senior_or_disabled/income/budgets_couple_together.yaml:134 is now OK: false. I re-read the rule: the two-part test is as quoted. Case 16 hand-checks (16,800 - 240 = 16,560 > 15,960). Run: flipping OK to true in either pathway setting fails Case 16 on three outputs. The two remaining differences are assessed below.
C2. Budgeting together dropped the ineligible-child allocation Fixed Both variables now read SSI's post-allocation amounts and drop only the threshold; Missouri alone keeps gross income. Deemed-income Case 7 (Arizona) and medically needy Case 53 (Arkansas) hand-check. Hand trace: the round-1 code would give 6,000 and 3,110 where they expect 36 and 128, so both fail without the fix.
S1. Budgeting together stricter than SSI outside 209(b) states, unrecorded Fixed (ruled) Candidate us:medicaid-abd-budgeting-together-stricter-than-ssi has every field step 1 lists, state: ruled and the date 2026-11-10. Run: its own example gives not eligible in Arizona (21,924 > 21,640) and eligible in Pennsylvania (15,960 against 15,960).
S2. Seven candidates incomplete Fixed Parsed the file at the head: all seven carry readings, pe_us.prs, the deciding parameter files and years.from: 2015 with no to.
S3. Ruled readings and most flags unpinned; 209(b) split branch unpinned Fixed Run: see "State settings" under Verified. Run: with the facility split removed from the 209(b) expense deduction, Case 14 returns [true, true] against its expected [false, true]; Case 13 still passes, as round 1 said.
G1. Alaska's third standard Addressed Named under "Own-rule states" and tracked in #10641.
G2. Illinois sizes the standard by household Addressed In "Child allocations" and in #10641.
G3. Arizona drops the half-of-earnings deduction in the FPL test Open Not in the body or in #10641.
G4. Own-income pretest under SSI's rule Addressed Now a limit of its own, with a New Jersey example.
G5. Missing Case 49; Case 50 asserts no eligibility Partly Cases now run 40 to 53 with no gap. The Hawaii case (now Case 52) still asserts no is_medically_needy_for_medicaid.
G6. Duplicated facility test Open Unchanged.

Oklahoma's two remaining differences

Both are disclosed accurately, in "Changes since review", under "Own-rule states" and "Own-income test", and in the Oklahoma row of #10641. Neither is new (hand trace): main gives the same result in the second and is more generous in the first, where it tests the applicant's own income against the couple limit.

  • No couple test when the spouse's income is $497 a month or less.
    • Size. This is a narrow band, as the body says. It needs spouse unearned income between $473.33 and $497 and own income near the individual standard.
    • Run. An applicant with Social Security of $16,200 and a spouse with $5,880 of interest is tested alone and passes (15,960 against 15,960). The rule's second part fails them: 16,200 + 5,880 - 240 = 21,840 > 21,640.
  • No own-income test once the spouse's income is deemed.
    • Size. This one is not narrow, and the body gives it no size. With a working spouse, only (wages - $65) / 2 is added, so own income well above $1,330 can pass the couple test. At wages just over $497 the model passes own countable income up to about $1,587 a month, $257 above the individual standard. The gap closes at wages of about $1,012.
    • Run. Social Security of $19,000 and spouse wages of $6,000 gives 18,760 + 2,610 = 21,370, within 21,640, so the model says eligible. Own income of 18,760 is above 15,960, so the rule says not eligible.
    • Same on main. Hand trace: main also tests a deemed couple only against the couple limit.

See suggestion G10 for the wording.

New findings

Critical (must fix)

None.

Should address

S4. Minnesota's setting follows the manual against a statute, and no candidate records it.

  • Where. P/senior_or_disabled/income/budgets_couple_together.yaml:105 and P/medically_needy/limit/income/budgets_couple_together.yaml:87 (MN: true). The only Minnesota source either file cites is the manual.
  • What the sources say.
    • Minn. Stat. 256B.056, subd. 1a(a)(1): "Unless specifically required by state law or rule or federal law or regulation, the methodologies used in counting income and assets to determine eligibility for medical assistance for persons whose eligibility category is based on blindness, disability, or age of 65 or more years, the methodologies for the Supplemental Security Income program shall be used".
    • EPM 2.3.3.3.2.1.1: "Except in the situations noted below, the income of a spouse is deemed to a person if the spouses live together." The page says whose income is deemed. It gives no amount and no threshold.
    • I read both on 2026-11-12.
  • Who found it. The author's law check of 2026-11-11. Issue Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 lists it under "not yet ruled" and says: "This is the same shape as Nebraska's ruled conflict (us-ne:medically-needy-unit-size), and it has no candidate entry."
  • Why it matters. The two readings differ widely, not in a narrow band. Hand arithmetic, as in Oklahoma's Case 16: a Minnesota 70-year-old with $16,800 of Social Security and a spouse with no income has 16,560 of countable income. Budgeted together that is within 21,640. Under SSI's methodology the applicant is tested alone, and 16,560 is above 15,960.
  • The gap. CONTRIBUTING.md#source-conflicts step 1 has the PR that takes a reading record it in source_conflicts/candidates.yaml. The test plan says the PR's readings are recorded as "eight state: ruled candidates", which leaves this one out. The rulings of 2026-11-02 and 2026-11-10 don't settle it: Montana's went to the regulation over the manual, Nebraska's to the specific rule over the general SSI clause.
  • Fix. Add a candidate for Minnesota. The guard accepts state: open, so this needn't wait for a ruling. Name it under Limits. If the project lead rules for the statute, set MN: false in both files and re-expect Minnesota in pathway Case 17 and medically needy Case 6.
  • Also from Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641, missing from the body. North Dakota's pathway setting rests on no text that gives a couple standard. Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 expects no household result to turn on it. One sentence under Limits would cover it.

S5. The default-marital-unit code added in the merge is half pinned and half applied.

  • Where. V/income/_couple_standard.py:21-29 (spouses_sum) and V/eligibility/categories/is_optional_senior_or_disabled_income_eligible.py:33-37.
  • What is pinned. Run: without the spouse-test branch of in_married_couple, Case 19 of is_209b_ssi_recipient_for_medicaid.yaml fails.
  • What is not. spouses_sum reads only the two spouses when a marital unit holds more than two people. Run: with that branch replaced by the plain marital-unit sum, no asserted output changed in any of the 58 cases under T/ that have a marital unit of three or more people. Other test folders were not run.
  • A case that pins it. West Virginia, 2026, no marital units given: a 70-year-old tax-unit head with $10,000 of Social Security, a 50-year-old tax-unit spouse, and a 67-year-old in their own tax unit with a $20,000 pension.
    • At the head (run). medicaid_optional_senior_or_disabled_uses_couple_standard is [false, true, false] and the limit is [11,928, 17,892, 11,928].
    • With the plain sum (run). [true, true, false] and 17,892 for the applicant, because the third adult counts as a second aged person in the couple.
  • The half not applied. The pathway's income test still sums the whole marital unit under the couple standard, while the 209(b) and medically needy budgets now total only the couple.
    • Run. The same household in Arizona: the applicant's 9,760 is within the couple limit of 21,640, but the test adds the third adult's 19,760, and 29,520 gives not eligible. With a third adult aged 50, who has no countable income here, the applicant is eligible.
    • Not a regression. Reading main's formula (not run on main): it sums the whole unit against the one-person limit and gives the same result.
  • Fix. Use spouses_sum(person, period, personal_income) in is_optional_senior_or_disabled_income_eligible, and add the two cases above.

Suggestions

  • G7. Missouri's exception is pinned by no test.
    • The text. MHABD 0805.015.05 supports the exception. I read it on 2026-11-12: "Consider the gross income of the couple in determining the adjusted income" and "Do not consider the income and expenses of minor children".
    • The gap. Run: no Missouri case under T/ has both an ineligible-child allocation and a non-zero deemed amount. Hand trace: so replacing where(is_mo, gross, ...) with the post-allocation amount would fail none of them. I did not run that mutation.
    • Context. The lines are unchanged from main. A Missouri copy of deemed-income Case 7, expecting the gross 6,000, would pin them.
  • G8. Case 44 should name SSI pools a married couple's income by December's facility status, so a part-year facility stay gives wrong SSI in the other months #10818.
  • G9. The new candidate's note and case.
    • Its note links the PR, not the ruling comment of 2026-11-12 (#issuecomment-6812820779), as six of the earlier seven link theirs. The comment was posted after the commit.
    • No case shows the stricter outcome the ruling is about. Arizona's Case 9 is denied under both rules, since 16,560 is above 15,960. The candidate's own example (16,200 and 5,964) would do.
  • G10. Give Oklahoma's own-income difference a size. The body sizes only the couple-test difference ("only above about $473"). The own-income difference reaches own income about $257 a month above the individual standard (see above).
  • G11. Connecticut is the clearest state to join Missouri.
    • The text. I read both sections on 2026-11-12. UPM 5020.75 C says MAABD deemed income "is calculated from parents and from spouses in the same way as in AABD". UPM 5020.70 C.3 deems "the combined total of the deemor's gross unearned income and applied earned income after the appropriate deductions are made". No child allocation appears in either.
    • Status. The body discloses this and Medicaid couple rules: encode the states whose rule is neither SSI's nor budgeting together #10641 holds it for a ruling, which is reasonable. If the ruling follows each state's text, a state parameter should replace the state == "MO" test.
  • Carried from round 1. G3 (Arizona's FPL test and the half-of-earnings deduction), G5 (Case 52 asserts no eligibility) and G6 (duplicated facility test).

Verified

  • Hand-checks of the six named cases (2026: FPL 15,960 / 21,640; child allocation 12 x 497 = 5,964; exclusions 240 and 780). CI also runs all six green.
    1. Case 45 (MA). 11,900 - 5,964 = 5,936, within 5,964, so SSI deems nothing. (5,936 - 780) / 2 = 2,578. 39,760 + 2,578 - 35,000 = 7,338, within 7,800: eligible.
    2. Case 46 (MA). 12,100 - 5,964 = 6,136, above 5,964. (6,136 - 780) / 2 = 2,678 is already in 42,438, so the adjustment is 0. 42,438 - 35,000 = 7,438, within 7,800: eligible.
    3. Case 47 (KS). 17,000 - 11,928 = 5,072. (5,072 - 780) / 2 = 2,146. 19,760 + 2,146 - 6,000 = 15,906, within 17,892: eligible.
    4. Case 48 (KS). 18,000 - 11,928 = 6,072. (6,072 - 780) / 2 = 2,646. 22,406 - 6,000 = 16,406, within 17,892: eligible.
    5. Deemed-income Case 7 (AZ). 6,000 - 5,964 = 36. 16,000 + 36 - 240 = 15,796, within 21,640. MA611 A's own order (allocation off the couple's total) gives the same 15,796.
    6. Medically needy Case 53 (AR). 7,000 - 5,964 = 1,036. (1,036 - 780) / 2 = 128. 19,760 + 128 - 17,500 = 2,388, within 2,599.92: eligible.
    • Also. 209(b) Case 14: 24,000 - 240 = 23,760 > 18,360 with own expenses only, and 17,760 with the spouse's 6,000, so [false, true].
  • Massachusetts and Kansas. Cases 45 to 48 turn eligible because SSI's allocation now applies where the state text is silent. That matches the ruling of 2026-11-02 ("SSI's rule applies where the state follows it or is silent"), and the body says these states' texts don't mention allocations.
  • State settings (run). I flipped each setting in memory and reran the cases for that state.
Setting States pinned when flipped By
Pathway budgets_couple_together, true AK CO CT IL IN MA MI MN NE NH SC VT WI Case 17
AZ Cases 8 and 9, deemed-income Case 7
HI Cases 14 and 15
MO Case 6, deemed-income Case 2
ND 209(b) Case 12
Pathway couple_limit_without_deeming, true ME, RI Case 17, Case 10
Pathway, false MT, OK, PA, VA, WV Cases 17, 16, 5, 209(b) Case 11, Case 2
Medically needy budgets_couple_together, true AR CA CT IL MD MI MN ND NE NH VT WI Couple-standard Case 6
MA Couple-standard Case 2; medically needy Cases 42 and 45
KS, HI Medically needy Case 47; Case 52
Medically needy couple_limit_without_deeming, true NJ, RI Couple-standard Cases 4 and 3
Medically needy, false MT, NY Couple-standard Case 6; Case 1 and medically needy Case 40
  • No true setting is unpinned. The other false settings are the default and have no case of their own.
  • Merge with main at 23a7c9a8f4: all seven hand-changed files.
    1. is_209b_ssi_recipient_for_medicaid.yaml. Comment only. 0.80 x 21,640 = 17,312 is right, and the expectation is unchanged.
    2. is_medically_needy_for_medicaid.yaml. main's Cases 37 to 39 keep their expectations. The comments in Cases 37 and 39 now name 434 x 12 = 5,208, the New Jersey couple limit in the parameter file. The PR's cases are 40 to 53, and their cross-references follow.
    3. is_209b_ssi_recipient_income_eligible_for_medicaid.py. Under the couple standard with no split, the couple's income total less the couple's expense total equals main's total of income less expenses.
    4. is_medically_needy_for_medicaid.py. The same, with the parental expense share totalled the same way. main's asset lines are untouched.
    5. _couple_standard.py. Not a conflict: new code written in the merge (see S5).
    6. Deemed-income variable. It keeps main's spouse-test totals for Missouri's gross income and the PR's budget-together and facility guards. The unused marital_unit is gone.
    7. candidates.yaml. Both sides kept. Parsed at the head: 436 unique ids; main's 428 entries at the merge parent are unchanged; 8 belong to the PR.
  • Can the widened helper pair the wrong two people? Yes, but only where main's SSI spouse test already does.
    • Run. Arizona, no marital units and no tax roles: a 70-year-old, her 45-year-old son and a 10-year-old. The tax-role inference makes the son the spouse. SSI deems his wages (ssi_countable_income is 23,388 for the mother), and the helper gives both the couple limit.
    • Why this is not a finding. The helper adds no pairing rule of its own, and an ambiguous unit resolves to no spouse. A two-person default unit (the mother and son alone) is paired the same way (run), as it was before the merge (reading). With marital units or tax roles given, the pairing is right. Without the widening, the limit would be for one person while the income already includes the deemed amount.
    • Inherited from main (reading, not run). A two-person marital unit that the spouse test rejects, for example one spouse being the other's tax dependent, gets the couple limit against one person's budget.
  • Law check of 2026-11-11: no code changed for it.
    • Commits. The head has two commits since round 1. The fix commit touches 10 files and the merge hand-changes the 7 above. Neither adds an own-income test. In the four setting files only Oklahoma's line changed, so Wisconsin and Hawaii are as they were.
    • Limits sampled against the texts (read 2026-11-12, all as quoted):
      • N.J.A.C. 10:72-4.4(d)1.
      • POMS SI 01320.400 A.
      • 20 CFR 416.1163(e)(2).
      • 405 IAC 2-3-20: an allocation off the spouse's income.
      • Wisconsin MEH 15.1.1: "EBD fiscal test groups are groups of one or two".
      • Connecticut UPM 5020.70 C.3, and 5020.75 C applying it to MAABD.
      • Missouri MHABD 0805.015.05.
    • Run. The New Jersey example gives 21,570 against 21,640 and passes, as the body's code trace says.
    • Not re-read. The Alaska, Colorado, Michigan, California, Illinois, Nebraska, Hawaii and New Hampshire texts.
  • Ruling record. The new candidate has id, program, question, years (from 2015, program type with a note), five sources, readings, an example, pe_us (follows: conflicting-source, two parameter files, prs) and state: ruled, dated 2026-11-10 in the note. Its list of non-209(b) states drops Oklahoma, matching the settings.
  • Counts. 46 new cases (17 + 6 + 14 + 4 + 3 + 2), and the state table's 19 of 38 and 17 of 32 match the parameter files.
  • Housekeeping. The changelog fragment is updated. No Python tests were added. The one new reference is a plain URL.

Axiom

axiom: TheAxiomFoundation/rulespec-us#2012 queued is valid for this head.

  • Issue state. OPEN, labelled pe-parity, updated 2026-11-12.
  • Matches the head. It names 27ca507758 and main at 23a7c9a8f4. It covers Oklahoma, the child allocations, the ruling of 2026-11-10, the 46 cases with Cases 40 to 53, and the helper added in the merge. Its out-of-scope list carries the own-income test and Arizona's own allocation method.
  • After S4 and S5. A changed Minnesota setting or new cases would need the issue updated again.

CI

All 36 checks pass at 27ca507758 (re-checked at the end; none pending).

Local runs on the head, with policyengine-core 3.33: one probe of 15 households, one in-memory mutation pass over the four setting files, and one pass for the 209(b) split, the Missouri cases and the default-unit helper. Nothing was run on main.

Branch

The branch contains main at 23a7c9a8f4 and is 5 commits behind main (1ca3d5a55c). git merge-tree --write-tree PolicyEngine/main 27ca507758 merges cleanly (tree 746cef66af).

Sibling notes (not findings):

Verdict: REQUEST_CHANGES

@DTrim99 DTrim99 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.

Requesting two small changes. Both round-1 criticals and all three should-address items are fixed and pinned: Oklahoma follows SSI's rule (Case 16), child allocations are kept in budget-together states except Missouri, the 2026-11-10 ruling is recorded and followed, the seven earlier candidates are complete, and every true state setting fails a test when flipped.

  1. Minnesota's setting follows the manual against a statute, with no candidate. Minn. Stat. 256B.056, subd. 1a(a)(1) requires SSI's methodologies unless state law or rule says otherwise; the budget-together rule is in the manual only. #10641 already says this "has no candidate entry". Please add one; state: open is accepted, so it needn't wait for a ruling (Should Address S4).
  2. The default-marital-unit code added in the merge is half pinned and half applied. spouses_sum's branch for a marital unit of three or more people changes no asserted output when replaced by the plain sum, and the pathway's income test still sums the whole unit while the 209(b) and medically needy budgets total only the couple. Two cases and a one-line change are in the report above (S5).

All seven hand-resolved merge files combine both parents correctly. Dropping Case 44's ssi_countable_income assertion is right for now, since the wrong value comes from main (#10818, fixed by #10820). CI is green at 27ca507758; the branch still conflicts with #10629 in two files.

hua7450 and others added 2 commits November 12, 2026 13:34
The aged, blind and disabled pathway's income test summed the whole
marital unit under the couple standard, so a default unit of more than
two people added another adult's income. Use spouses_sum, as the 209(b)
and medically needy budgets do, and pin it with a West Virginia household
(the third adult is not the applicant's spouse) and an Arizona one (the
applicant passes on the couple's own income). One of main's California
cases now finds the second couple eligible on its own income.

Add the open candidate us-mn:abd-spouse-income-statute-vs-manual: Minn.
Stat. 256B.056, subd. 1a(a)(1) requires SSI's methodologies, while the
manual the model follows deems a co-resident spouse's income. Link the
2026-11-10 ruling comment from the budgeting-together candidate, and add
a case showing the stricter outcome that ruling covers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Main now holds PR 10629. In is_209b_ssi_recipient_income_eligible_for_medicaid,
the parental medical expense share comes off inside the same couple total as
the couple's own expenses, as is_medically_needy_for_medicaid already does. In
is_medically_needy_for_medicaid.yaml, main's Illinois Case 40 keeps its number
and this branch's cases move to 41-54, with their cross-references; Case 45
now names issue 10818 and PR 10820 for the omitted ssi_countable_income.

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

hua7450 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator Author

Ready for another look at 25c45f3214:

On the merged code, the nine changed test files and three of 10629's pass locally (321 cases).

@hua7450
hua7450 requested a review from DTrim99 November 12, 2026 19:33
@DTrim99

DTrim99 commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

PR Review (round 3): Apply each state's rule for a Medicaid applicant whose spouse is not aged, blind or disabled

PR #10640 (author: hua7450), head 25c45f3214, re-review requested on 2026-11-12. Round 2 was at 27ca507758 (request changes: 0 critical, 2 should, 8 suggestions). Since then the branch has one fix commit (47c6fc309c, 5 files, +182/-7) and one merge of main at 24939d2701, which now holds #10629. The merge hand-resolves two files. The diff is 25 files, +3,118/-39. No partner test file is touched.

Path prefixes used below:

  • V/ = policyengine_us/variables/gov/hhs/medicaid/
  • T/ = policyengine_us/tests/policy/baseline/gov/hhs/medicaid/

Nothing was run locally this round. Each claim below says what it rests on: hand trace (arithmetic or code read by hand), reading (the code, tests or source text) or CI log (the run at this head). Where I say what a changed line would do to a test, that is by my reading, not a run.

Summary

Both should items from round 2 are fixed, and each fix is pinned.

  • Default marital units (S5). The pathway's income test now totals only the couple, and three cases turn on it: West Virginia Case 18, the new Arizona case and main's California case.
  • Minnesota (S4). The open candidate us-mn:abd-spouse-income-statute-vs-manual has every field step 1 lists, and Limits covers Minnesota and North Dakota.

The California re-expectation is the correct result of the fix, not a regression. The second couple has no income. main failed them only because it added the first couple's 36,000 to their test.

The merge is sound. Both hand-resolved blocks combine their parents correctly. No expectation from #10629 changed, and a child alone in a marital unit still gets their own budget.

Nothing new blocks. Three new suggestions, one of which corrects a figure from my round-2 report: after #10820 (merged into main after this head), Case 45's ssi_countable_income is 14,320 and 27,320 by my reading, not 20,880 each.

Prior findings

Finding Status Evidence
S4. Minnesota's setting follows the manual against a statute, with no candidate Fixed source_conflicts/candidates.yaml:5724 adds us-mn:abd-spouse-income-statute-vs-manual with id, program, years (from 2015, program type with a note), question, two sources (statute and manual), readings, an example, pe_us (follows: conflicting-source, both budgets_couple_together.yaml files, prs) and state: open. Reading: both quotes match the pages, re-read on 2026-11-12. Both code paths exist at the head. The id is unique at the head (441 ids) and on the tree merged with main (447 ids). The guard job is green (CI log). Limits now has "Minnesota" and "North Dakota".
S5. Default-marital-unit code half pinned and half applied Fixed V/eligibility/categories/is_optional_senior_or_disabled_income_eligible.py:39 now calls spouses_sum. Hand trace: West Virginia Case 18 and the Arizona case give the expected values. By my reading, each case fails if spouses_sum's branch for three or more people, or its use in the income test, goes back to the plain marital-unit sum (see Verified).
G7. Missouri's exception pinned by no test Open No Missouri case with an allocation was added. The lines are unchanged from main.
G8. Case 44 should name #10818 Addressed The case, now Case 45, names #10818 and #10820. See G12 for the figure.
G9. The new candidate's note and case Addressed The note links #issuecomment-6812820779, which exists and states the ruling of 2026-11-10. Uses-couple-standard Case 19 runs the candidate's example and hand-checks.
G10. Size for Oklahoma's own-income difference Addressed "Own-income test" gives it. Hand arithmetic: 1,803.33 - (497 - 65) / 2 = 1,587.33, which is 257.33 above 1,330, and (w - 65) / 2 = 473.33 gives w = 1,011.67.
G11. Connecticut is the clearest state to join Missouri Open (tracked) Held in #10641 for a ruling, as before.
G3, G5, G6. Carried from round 1 Open Unchanged. The Hawaii case, now Case 53, still asserts no is_medically_needy_for_medicaid.

New findings

Critical (must fix)

None.

Should address

None.

Suggestions

  • G12. Case 45's restored assertion should be 14,320 and 27,320, not 20,880 each.
    • What changed. Combine an SSI couple's income by each month's facility status #10820 merged into main at 20:13 UTC on 2026-11-12, after this head. Case 45's comment and the body say to restore ssi_countable_income: [20_880, 20_880] once it merges.
    • The figure (reading of main's formula, not run). In the six months of the stay each spouse counts their own income less their own $20: 646.67 and 2,813.33 a month, or 3,880 and 16,880. In the six months at home each has half of 3,500 - 20 = 3,480, or 10,440. That gives 14,320 and 27,320.
    • My error in round 2. I wrote that 20,880 "is right". That is the figure with no stay, and the comment follows my wording.
    • Effect. The couple's total becomes 41,640, not 41,760. It is still above 29,868, so no asserted output changes.
    • Ask. At the next merge of main, restore the assertion with the value the model gives, and reword the comment and the body's "where $20,880 is right".
  • G13. Two tracking texts are behind the head.
  • G14. The couple branch of the parental-share term has no case.
    • Where. V/eligibility/categories/is_209b_ssi_recipient_income_eligible_for_medicaid.py:65 and V/eligibility/categories/medically_needy/is_medically_needy_for_medicaid.py:75.
    • Reading. Every case with a share has the child alone in a marital unit, so the couple total and the child's own share are equal. By my reading, replacing the where with either branch changes no asserted output.
    • Why it's only a suggestion. The term equals main's total wherever the couple standard applies (see Verified), and a share reaches a couple's total only when an eligible couple has an eligible child with an ineligible parent in the same default unit.
  • Carried. G3 (Arizona's FPL test and the half-of-earnings deduction), G5 (Case 53 asserts no eligibility), G6 (duplicated facility test), G7 (Missouri's exception) and G11 (Connecticut).

Verified

  • Hand-checks of the new and changed expectations (2026: FPL 15,960 / 21,640; SSI rates 994 / 1,491 a month; exclusion 240). CI also runs all of them green.
    1. West Virginia, uses-couple-standard Case 18. Three adults, no marital units, so one default unit of three.
      • The spouse test pairs the head and spouse of the first tax unit. The 67-year-old heads another tax unit and has no spouse.
      • The applicant is aged and the spouse is not, so the couple holds one aged person. The spouse has no income, so nothing is deemed, and the applicant is tested alone: [false, true, false].
      • Limits: 12 x 994 = 11,928, 12 x 1,491 = 17,892 and 11,928.
    2. Arizona, the new last case in is_optional_senior_or_disabled_income_eligible.yaml. The same household. Arizona budgets together, so the pair uses the couple standard: [true, true, false] and limits 21,640, 21,640 and 15,960.
      • Countable income: 10,000 - 240 = 9,760, 0, and 20,000 - 240 = 19,760.
      • The couple's 9,760 + 0 is within 21,640. The 67-year-old's 19,760 is above 15,960: [true, true, false].
    3. Uses-couple-standard Case 19. The spouse's 5,964 of interest equals 12 x (1,491 - 994) = 5,964, so SSI deems nothing (20 CFR 416.1163(d)(1): "not more than").
      • Arizona: 16,200 + 5,964 - 240 = 21,924, above 21,640. Neither is eligible.
      • Pennsylvania: the applicant alone has 16,200 - 240 = 15,960, within 15,960. The spouse's couple total is 15,960, within 21,640. Both pass.
    4. California, "leaves another couple's dependent's premiums out of a couple budget". Five people in one default unit: two aged couples and a child.
      • Both couples use the couple limit, 1.38 x 21,640 = 29,863.20.
      • First couple: (24,120 + 12,120 - 240) / 2 = 18,000 each, and 36,000 is above the limit.
      • Second couple: 0 + 0 is within it. The child is not aged, blind or disabled: [false, false, true, true, false].
  • S5 mutations (by my reading; not run).
    • spouses_sum's branch for three or more people replaced by the plain sum. In Case 18 the unit then holds two aged people, the applicant no longer has an ineligible spouse, and the first output is true against the expected false. In the Arizona case the income is 9,760 + 0 + 19,760 = 29,520, above 21,640, against the expected true.
    • The income test's spouses_sum replaced by person.marital_unit.sum. The Arizona case fails the same way, and California's second couple gets 36,000 against the expected true. Case 18 asserts no income test, so the Arizona case is the one that covers this half.
  • The California case.
    • Origin. Apply 416.1163(e)(2) to deemed SSI and identify SSI couples by marriage, not tax roles #10141 added it on main (2026-11-10).
    • Inputs. Unchanged. Against main, only the two comment blocks and the one expectation line differ.
    • Why the new value is right. Two aged spouses with no income are within any limit. main's own comment put their failure down to the whole-unit sum ("because the income reader sums the whole default unit").
    • Comment. The first-couple comment now gives the couple limit, 29,863.20. It read 22,024.80 (1.38 x 15,960) at round 2, when the limit was already the couple's.
  • Minnesota.
    • Statute, read 2026-11-12. Subd. 1a(a)(1) is as quoted. Subd. 1b: "The $20 general income disregard allowed under the Supplemental Security Income program is included in the standard and shall not be allowed as a deduction from income".
    • Example. So countable income is 16,800, as the candidate says, not the 16,560 in my round-2 example. It is within 21,640 budgeted together and above 15,960 alone.
    • Manual, read 2026-11-12. As quoted. The page lists when a spouse's income is not deemed and gives no amount or threshold.
    • Still to rule. The statute-first principle points to the statute here, so the setting may change. The candidate's note names the two cases to re-expect.
  • North Dakota (hand arithmetic). An SSI recipient's own countable income is at most 11,928. With nothing deemed, the spouse has at most 5,964. The total is at most 17,892, the couple rate, so both methods pass, as Limits says.
  • Merge with main at 24939d2701: both hand-resolved blocks.
    1. is_medically_needy_for_medicaid.yaml.
      • 55 cases: main's 41 and this PR's 14, with none dropped or doubled.
      • The first 1,093 lines equal main's file except the two comments changed in round 2. Illinois Case 40 is identical.
      • This PR's cases equal their pre-merge text apart from the case numbers (now 41 to 54) and Case 45's comment.
      • The two in-file cross-references follow (Case 46 and Case 50). So do the body and rulespec-us#2012.
    2. is_209b_ssi_recipient_income_eligible_for_medicaid.py.
      • Against main. main totals income less expenses less the parental share over the couple. Under the couple standard the head totals each of the three over the couple, which is the same sum.
      • Against the PR. The income and expense lines are the PR's. The parental share is added the way is_medically_needy_for_medicaid already had it.
      • A child alone in a marital unit. The child has no spouse, so each total is the child's own: income less own expenses less own share, as on main.
      • Hand trace, Missouri Case 28 of is_optional_senior_or_disabled_for_medicaid.yaml. 22,320 - 0 - 10,000 = 12,320, within 13,572. Without the share term, 22,320 is above it, so Let Missouri aged, blind and disabled people who don't receive SSI spend down #10629's cases pin the term.
  • No Let Missouri aged, blind and disabled people who don't receive SSI spend down #10629 expectation changed. Against main, Let Missouri aged, blind and disabled people who don't receive SSI spend down #10629's test files differ only in five comment lines of is_209b_ssi_recipient_for_medicaid.yaml (from round 2) and the renumbering above.
  • Files merged without conflict.
  • Source-conflict ratchet. The fix commit and the merge add comments in two variable files, and neither reads like a conflict between sources. The ratchet reads variables, parameters and reforms, not tests. The guard is unchanged on main since the merge.
  • Counts. 49 new cases (19 + 6 + 14 + 4 + 3 + 2 + 1), matching the test plan.
  • Housekeeping. No Python tests were added. The fix adds no reference.

Axiom

axiom: TheAxiomFoundation/rulespec-us#2012 queued is valid for this head.

  • Issue state. OPEN, labelled pe-parity, updated 2026-11-12.
  • Matches the head. It names 25c45f3214 and main at 24939d2701. It covers the couple-only income test, Cases 18 and 19, the California re-expectation, the open Minnesota candidate, the 49 cases and medically needy Cases 41 to 54.
  • One stale line. See G13.

CI

All 36 checks pass at 25c45f3214 (re-checked at the end; none pending). The four that were pending earlier have finished.

From the log of the Baseline (contrib-hhs) job, every changed test file ran with no failure:

  • medicaid_optional_senior_or_disabled_uses_couple_standard.yaml: 19.
  • is_optional_senior_or_disabled_income_eligible.yaml: 40.
  • medicaid_optional_senior_or_disabled_countable_income.yaml: 49.
  • is_medically_needy_for_medicaid.yaml: 55.
  • is_209b_ssi_recipient_income_eligible_for_medicaid.yaml: 14, and is_209b_ssi_recipient_for_medicaid.yaml: 22.
  • medicaid_category.yaml: 17, medicaid_medically_needy_uses_couple_standard.yaml: 6, and the deemed-income file: 9.
  • Let Missouri aged, blind and disabled people who don't receive SSI spend down #10629's other files: is_optional_senior_or_disabled_for_medicaid.yaml 37, is_optional_senior_or_disabled_asset_eligible.yaml 72, medicaid_parental_medical_expense_share.yaml 4.

I couldn't reconcile the body's local count of 321 with these (the nine changed files alone hold 231). CI is the record.

Branch

The branch contains main at 24939d2701 and is 20 commits behind main (cc486336d7). git merge-tree --write-tree PolicyEngine/main 25c45f3214 merges cleanly (tree 1a303f82ff).

Sibling notes (not findings):

Verdict: APPROVE

@DTrim99 DTrim99 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.

Approving. Both round-2 items are fixed and pinned: the pathway's income test now totals only the couple (West Virginia Case 18, the new Arizona case and main's California case all turn on it), and Minnesota is recorded as the open candidate us-mn:abd-spouse-income-statute-vs-manual. The California re-expectation is the right consequence of the fix, both hand-resolved merge blocks combine their parents correctly, and no #10629 expectation changed.

One correction to my round-2 report, in G12: the value to restore in Case 45 once main is merged again is 14,320 and 27,320 (by my reading of main's formula after #10820), not 20,880 each. No asserted output changes. The other suggestions are optional. CI is green at 25c45f3214.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants