Skip to content

Add Pennsylvania state supplementation for 2026 - #10167

Open
hua7450 wants to merge 3 commits into
mainfrom
pa-ssp-2026
Open

Add Pennsylvania state supplementation for 2026#10167
hua7450 wants to merge 3 commits into
mainfrom
pa-ssp-2026

Conversation

@hua7450

@hua7450 hua7450 commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

What and why

Implements Pennsylvania State Supplementary Payment for researched 2026 coverage, with state-specific eligibility, payment rules, and integration into benefit totals and SNAP/HUD income.

Models optional living-arrangement supplements and institutional personal-needs payments. Care certification and separate individual SSI claims require explicit inputs. Mandatory grandfathered payments and ancillary facility subsidies are outside this component.

Parameter backfilling does not establish verified historical coverage.

Related: #8568; historical backdating remains separate.

References

Additional section and page citations are included alongside the parameters and formulas.

Test plan

  • 17 source-based YAML cases passed on this separate state branch.
  • Synthetic national simulation: 153 households, 204 people, all 50 states and DC; finite nonnegative benefit and income aggregates.
  • make format, reference/registry checks, and git diff --check.
  • State changelog fragment.

axiom: needed

hua7450 and others added 3 commits October 12, 2026 14:28
@hua7450
Add Pennsylvania state supplementation for 2026
d515ab5
@hua7450
Normalize Pennsylvania SSP parameter and test formatting
6555a8d
@hua7450 @claude
Fix issues from review: Pennsylvania SSP SPN gate, couple notes and t…
5b27ace 
…ests

- Accept reported SSI receipt for the $22.10 Supplement for Personal Needs
- Document that the personal care home couple rate applies only in the move month
- Clarify the unused Medicaid-institution couple value; cite Ch. 299 sections and LTC Handbook 450.243
- Registry placement and comments, SNAP reference title, programs.yaml note
- Federal-minimum, care-couple, SPN and separate-claim cases; whole-dollar boundary incomes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hua7450
hua7450 marked this pull request as ready for review October 13, 2026 08:14
@hua7450
hua7450 requested a review from DTrim99 October 13, 2026 20:37
@DTrim99

DTrim99 commented Oct 13, 2026

Copy link
Copy Markdown
Collaborator

PR Review: Add Pennsylvania state supplementation for 2026

PR #10167 (author: hua7450, head 5b27aceb40, merge-base 2e9eea7e6e). 15 files (+665/−4), 3 commits.

Summary

The PR adds Pennsylvania's State Supplementary Payment (SSP):

  • Parameters, all dated 2026-01-01:

    • gov.states.pa.dhs.ssp.amount.individual and .couple, broken down by pa_ssp_living_arrangement:

      Arrangement Individual Couple
      Independent living 22.10 33.30
      Household of another 25.53 38.44
      Domiciliary care 634.30 1,347.40
      Personal care home 639.30 1,357.40
      Medicaid institution 22.10 0 (unused)

    • care_age_threshold of 18.

    • A new federal gov.ssa.ssi.state_supplement.minimum_payment of $1.

  • Variables:
    • pa_ssp_living_arrangement (Person, MONTH). Its formula maps the federal living arrangement; domiciliary and personal care homes are input-only.
    • pa_ssp (Person, MONTH).
    • A shared helper, variables/gov/ssa/ssi/_ssi_state_supplement.py. It handles the income reduction, couple and spouse-deeming rules. For the SSA-administered care-home rows it also applies SSA rounding and the $1 minimum.
  • Aggregates and registry:
    • household_state_benefits (all four year blocks), spm_unit_benefits, SNAP unearned income and HUD unearned income.
    • A programs.yaml entry (partial, verified_years: "2026").
  • Tests: 24 YAML cases, 17 in pa_ssp.yaml and 7 in integration.yaml.

The 2026 policy content is right:

  • Amounts. All eight living-arrangement rates match 55 Pa. Code § 299.37 (state-administered rows) and POMS SI 01415.058 K.2 (SSA-administered rows). They also match PA's MA Eligibility Handbook 387 Appendix A 2026 totals. The $22.10 Supplement for Personal Needs (SPN) matches LTC Handbook 450.243.
  • Who administers what. Pennsylvania administers the independent and household-of-another rows; SSA administers the care-home rows (§ 299.1(c)). The code follows that split.
  • Rules the code follows correctly:
    • The SSP-only dollar-for-dollar reduction (§ 299.21(b)(1), § 299.36(a)(2)(iv)).
    • The age-18 floor for care homes (POMS K.1).
    • The $1 minimum (20 CFR 416.2020(c)).
    • The deeming computation (SI 01320.430 D).
  • Tests and CI. All 24 expectations check by hand and pass at the head. CI is green and the branch merges cleanly with main.

Four should-fix items remain:

  1. The axiom: needed line isn't valid for a staff PR.
  2. Three parameter descriptions don't follow the house template.
  3. Pennsylvania's own Property Tax/Rent Rebate counts half of the SSP, but pa_ssp isn't wired into that income definition.
  4. The first reference on both rate files (§ 299.37) prints the pre-increase care-home amounts.

Critical (must fix)

None.

Should address

1. axiom: needed isn't valid here, and this PR adds a program.

  • Where: the last line of the PR body, axiom: needed.
  • The rule. main's CLAUDE.md, "Axiom Parity (required for policy changes)", lists the accepted forms: encoded-correct, encoded, queued or n/a: <reason>. needed is reserved for external contributors who can't complete the Axiom work, and the author is PolicyEngine staff.
    • CONTRIBUTING.md#axiom-parity: "That covers a new program, a parameter or threshold update, an eligibility rule and a bug fix." This PR adds a new program, and none of the n/a grounds applies.
  • Nothing to point to yet.
    • rulespec-us main has no Pennsylvania SSP module. us-pa/ holds only policies/cms/ (CHIP and Medicaid levels) and policies/income_tax/.
    • Issue searches for "Pennsylvania supplementary", "Pennsylvania SSP", "299.37" and "Chapter 299" find nothing. The only open Pennsylvania pe-parity issue is Increase default age from 30 to 40 #1737 (CCW).
  • Precedent:
  • Fix: file a dispatch-ready pe-parity issue on the Add AMT parameters for 2020-2023 #1467 / DC CDCC #1708 model, then add a line such as axiom: 55 Pa. Code §§ 299.21, 299.36, 299.37; POMS SI 01415.058 K TheAxiomFoundation/rulespec-us#NNNN queued. The issue needs:

    • Module paths, for example:

      • us-pa/regulations/pa-code/title-55/chapter-299/299-37-optional-ssp-levels.yaml, plus the § 299.21 and § 299.36 rules
      • us-pa/policies/ssa/poms/si-01415-058/2026/pa-ssp-individual-state-supplement-levels.yaml and the couple counterpart, mirroring the existing DC and DE modules
      • us-pa/policies/dhs/ltc-handbook/450-243-supplement-for-personal-needs.yaml

    • Verbatim law, quoted under Verified correct:

      • § 299.21(a), (b)(1) and (b)(3)
      • § 299.36(a)(2)(iv)(A)–(B)
      • the § 299.37 independent and household-of-another rows
      • POMS K.1 codes G and H, the K.2.a/K.2.b G and H rows, and the K.2 NOTE
      • the LTC 450.243 SPN sentence

    • Required outputs (Person, monthly):

      • the rate table by arrangement
      • a Judgment: SSI-eligible except for income, AND countable income below FBR + SSP, AND not in a Title XIX facility for the optional SSP, AND age 18 or older for the care rows
      • Money: max(0, rate − max(0, countable − FBR))
      • the $22.10 SPN for SSI recipients in a Medicaid facility
      • the $1 floor for SSA-administered rows

    • Companion tests from the same sources (MA Handbook 387 Appendix A 2026 totals and POMS K.2):

      Case SSP Total payment
      Independent individual, no income 22.10 1,016.10
      Household-of-another individual 25.53 688.20
      Domiciliary-care individual 634.30 1,628.30
      Personal-care-home couple in the move month 1,357.40 2,848.40
      SSI recipient in a Medicaid institution 22.10 52.10
      SSP-only with $1,010 countable income 6.10 —

2. Three parameter descriptions don't follow the house template.

  • Where:
    • parameters/gov/states/pa/dhs/ssp/amount/individual.yaml:1: "Pennsylvania provides these monthly state supplementary payment rates for an eligible individual."
    • .../amount/couple.yaml:1: the same, "for an eligible couple".
    • .../care_age_threshold.yaml:1: "Pennsylvania requires this minimum age for federally administered domiciliary or personal care supplementation."
  • The template: "one sentence, spell the program out fully (no acronyms), [State] [verb] ... under the [Full Program Name] program."
    • None of the three has the "under the ... program" clause.
    • The sibling SSP parameters on main all do. For example, ga/dhs/ssp/amount.yaml: "Georgia provides this amount as the monthly supplement under the State Supplementary Payment program." And in/fssa/ssp (age): "Indiana sets this threshold as the minimum age for eligibility under the State Supplementary Payment program."
  • Fix:
    • individual.yaml: "Pennsylvania provides these amounts as the monthly individual payment under the State Supplementary Payment program."
    • couple.yaml: the same with "couple".
    • care_age_threshold.yaml: "Pennsylvania sets this age as the minimum for the domiciliary care and personal care home supplements under the State Supplementary Payment program."

3. Pennsylvania's Property Tax/Rent Rebate counts half of the SSP, but pa_ssp isn't in its income definition.

  • Where: variables/gov/states/pa/tax/property/property_tax_or_rent_rebate/pa_property_tax_or_rent_rebate_income.py:30-40. half_counted_benefits halves social_security, ssi and railroad_benefits only.
  • The source. 2025 PA-1000 instructions:
    • Line 4 (PDF p. 7): "Include one-half of your 2025 Social Security Benefits as shown in Box 5 of your benefit statement SSA-1099, one-half of your 2025 SSI, one-half of your 2025 Social Security Disability Income, and one-half of your 2025 State Supplementary Payment."
    • "State Supplementary Payment recipients" (PDF p. 3): "SSP is still considered reportable income. As with other Social Security income, only half of the SSP income needs to be included on Line 4 of the Property Tax/Rent Rebate claim form."
  • Why it is a finding now. Before this PR the SSP wasn't modeled, so nothing could be counted. Now that pa_ssp exists, the program that most directly targets PA's SSP population leaves it out. The checklist treats this as missing wiring, not double counting.
  • Probe at the head (2026): an aged single renter with $6,000 of rent and $4,900 of taxable pension.
    • SSI is 7,268 (12,168 − 4,900) and pa_ssp is 265.20.
    • PTRR income is 8,534 (4,900 + 7,268 / 2), so the rebate is $1,000.
    • Counting half the SSP gives 8,534 + 132.60 = 8,666.60. That is above the $8,551 bracket edge, so the rebate is $770 (pinned-income probe). The model overstates this household's rebate by $230.
  • Fix:
    • Add "pa_ssp" to the half_counted_benefits list.
    • Update benefit_income_rate.yaml's description to name the State Supplementary Payment.
    • Add the case above to the PTRR tests: income 8,666.60, rebate 770.

4. The first reference on both rate files prints the old care-home amounts.

  • Where: amount/individual.yaml:10-11 and amount/couple.yaml:10-11 list "55 Pa. Code § 299.37, Optional SSP levels" first.
  • What the code says. § 299.37 reads:
    • "Residing in a Domiciliary Care Home $434.30 $947.40"
    • "Residing in a Personal Care Home $439.30 $957.40"
    • "Source: amended April 13, 2012, effective July 1, 2011"
  • The conflict. The PR's DOMICILIARY_CARE / PERSONAL_CARE values are 634.30 / 1,347.40 and 639.30 / 1,357.40. They are right for 2026, per POMS SI 01415.058 K.2.a: "G | All | 994.00 | 634.30 | 1628.30" and "H | All | 994.00 | 639.30 | 1633.30"; and K.2.b, "1347.40" and "1357.40".
    • So a reader who opens the first reference sees amounts $200 (individual) and $400 (couple) lower, with nothing explaining the gap.
    • The rows are still corroborated by the second reference, so this is not a missing reference.
  • A better source. PA's own MA Eligibility Handbook 387 Appendix A, "Effective January 1, 2026", shows every 2026 row:
    • Independent: $1,016.10 / $1,524.30 = FBR + 22.10 / 33.30
    • Another individual's home: $688.20 / $1,032.44 = 662.67 + 25.53 / 994 + 38.44
    • Domiciliary care: $1,628.30 / $2,838.40
    • Personal care boarding home: $1,633.30 / $2,848.40
    • MA institution: $52.10 / $104.20 = $30 + $22.10 per person
  • Fix:
    • Add the Handbook 387 Appendix A reference and point the POMS hrefs at #k2a (individual) and #k2b (couple).
    • Add a one-line YAML comment by the care rows: § 299.37 still prints the pre-increase $434.30 / $439.30.
    • Alternatively, close Suggestion 1 by dating the older amounts. § 299.37 then corroborates the values it actually shows.

Suggestions

  1. Care-home and SPN amounts before 2023 (deferral documented in the PR body and Pennsylvania SSP 2017, 2018, 2019 #8568).
    • The leak. All values are dated only 2026-01-01, so they carry back to 2015. The probe at the head gives pa_ssp of 634.30 (domiciliary care) and 639.30 (personal care) for 2018-01, 2021-01 and 2022-01.
    • What SSA paid. The POMS January charts show:
      • SI 01415.050 (Jan 2018) through SI 01415.054 (Jan 2022): G $434.30 / $947.40 and H $439.30 / $957.40
      • SI 01415.055 (Jan 2023) onward: $634.30 / $1,347.40 and $639.30 / $1,357.40
    • The Handbook totals agree. The 2022 domiciliary total is $1,275.30 (841 + 434.30); the 2023 total is $1,548.30 (914 + 634.30).
    • Size of the error. The model overstates 2015–2022 care-home payments by $200 per individual and $400 per couple each month. The exact 2022 effective date isn't in the January charts; it needs the Pennsylvania authority, likely the 2022–23 budget.
    • The SPN. Appendix A's MA-institution totals are $45 for 2020–2024, which implies $30 + $15. The LTC Handbook's $22.10 text is "Updated December 23, 2024". The 2025 total of $60 is internally inconsistent, so confirm the SPN history before backdating it.
    • Unchanged rows. The independent and household-of-another rows haven't changed since the July 1, 2011 amendment.
    • Fix: widen Pennsylvania SSP 2017, 2018, 2019 #8568 (titled "Pennsylvania SSP 2017, 2018, 2019") to 2015–2025, including the care-home step and the SPN history.
  2. The Texas rebate reform's copy of spm_unit_benefits now omits pa_ssp.
    • Where: reforms/states/tx/rebate/tx_rebate.py:45-127 redefines spm_unit_benefits nationwide with a hard-coded list. It lacks pa_ssp, and it already lacks ca_state_supplement.
    • Probe at the head: a PA aged SSI-only single in 2027 has spm_unit_benefits of 14,823.46 at baseline and 14,558.26 under the reform, a drop of exactly the $265.20 pa_ssp. spm_unit_net_income falls by the same amount; household_net_income is unchanged.
    • Fix: insert "pa_ssp", # Pennsylvania benefits after "fl_oss", at line 65, as spm_unit_benefits.py does. Add ca_state_supplement while there, consistent with Add Wyoming state supplementation for 2026 #10174.
  3. Mixed-arrangement couple in the move month (integration Case 6, integration.yaml:128-159).
    • The PR pins [347.675, 347.68], the average of the two half couple rates. That follows SSA's national rule in SI 02005.030 G.1: "For multi-category or multi-living arrangement couples living together, average their individual OSS payment (unless the State provides specific couples multi-category levels)."
    • Pennsylvania's regional instruction says otherwise. SI PHI01415.010, Appendix I Chart 35, note 2: "The state supplement amount to the member(s) who move(s) into the PCBH is 1/2 of the couple's rate for OS-H for the month of move. The state supplement amount for the member who remains in a household situation is 1/2 of the couple's rate for OS-A or OS-B for the month of move."
      • So the split should be 16.65 (state-paid) and 678.70 (SSA-paid).
      • The couple total agrees to within half a cent (695.355 against 695.35), so household aggregates are right. The PR documents this as a limitation.
    • Fix (optional): give the helper a per-member split option, standard = couple_rate / 2 for joint couples, and pin [16.65, 678.70].
    • Default for personal-care couples. SSA treats a personal-care couple as individuals from the month after the move, so the usual month needs ssi_claim_is_joint: false. Consider saying so in pa_ssp.py's documentation as well as in the Enum's.
  4. Pin the remaining readings with tests. The default branch of pa_ssp_living_arrangement covers more than independent living.
    • Children and private-pay facilities. SSA's State Assistance Programs for SSI Recipients, January 2011, Pennsylvania defines "Living alone" to include "all recipients in private medical facilities ... where Medicaid is not paying more than 50 percent of the cost of care ... and all other individuals and couples residing in a federal Code A or C living arrangement". It also says "Blind and disabled children are eligible for optional supplementation."
    • Probes at the head:
      • A disabled 10-year-old living with a parent gets pa_ssp 22.10.
      • A household-of-another SSP-only person with $700 of Social Security gets 25.53 − (680 − 662.67) = 8.1967. That is an unrounded state-administered amount.
    • Fix: add these two cases. Assert pa_ssp_living_arrangement directly for the medical, household-of-another, child and private-pay paths.
  5. Polish.
    • Blank lines. The PR adds a stray blank line before metadata: in household_state_benefits.yaml (line 412) and in hud/annual_income/sources/unearned.yaml (line 33). Neither relates to Pennsylvania.
    • Case count. The PR body says "17 source-based YAML cases"; the PR has 24 (17 + 7).
    • Missing citation. pa_ssp.py:14-19 cites § 299.1 and § 299.36 but not § 299.21. That section holds the excess-income exception and the Title XIX exclusion, the two rules the formula leans on most.

Verified correct

  • Administration split. 55 Pa. Code § 299.1(c):

    • "(2) The SSA administers SSPs for an individual or couple that is ... (ii) Living in a DCH. (iii) Living in a licensed PCH."
    • "(3) The Commonwealth administers SSPs for an eligible individual or couple that does not qualify for an SSP under paragraph (2) and is ... (i) Living independently. (ii) Living in the household of another and receiving in-kind support and maintenance."
    • The code passes federal_payment_rules=care, so SSA rounding and the $1 floor apply only to the care rows. POMS K.1 code Z ("recipients in FLA A or FLA B who receive a State-administered supplement") matches.

  • Eligibility and the income reduction. § 299.21:

    • "(a) ... to be eligible for an optional SSP, the individual or couple shall be eligible for SSI."
    • "(b)(1) ... If the individual or couple meets all SSI requirements other than income, and if countable income does not exceed the combined FBR and applicable SSP, the individual or couple is eligible."
    • "(b)(3) ... living in a medical care facility where ... more than 50% of the cost of care is paid under Title XIX ... is ineligible for an optional SSP."
    • § 299.36(a)(2)(iv)(B): "Countable income is adjusted dollar for dollar against the appropriate SSP amount in § 299.37, plus the FBR."
    • SSA 2011: "Countable income is deducted first from the federal payment. Any income that remains to be counted after the federal payment has been reduced to zero is then deducted from the state supplementary payment."
    • The helper's rate − max(countable − FBR, 0) and the non-income is_ssi_eligible gate (categories, resources, immigration) match all three.

  • The household-of-another payment level uses the reduced FBR. POMS K.2.a row "B | Z | 662.67", and Handbook 2026 "$688.20" = 662.67 + 25.53. That supports using ssi_amount_if_eligible (one-third reduction) as the FBR.

  • Care homes:

    • Age floor. POMS K.1: code G and code H "Apply OS code ... to adult persons (age 18 and over) certified by the State".
    • Domiciliary couples keep the couple rate. Chart 35 note 2: "Couples can reside in a noninstitutional care arrangement such as DOMCARE. The couple is considered to be living in their own household."
    • Personal-care couples. The K.2 NOTE: "Apply the payment level for couples in Pennsylvania's PCBHs only in the month they move into the PCBH. You must regard them as individual recipients in the month following the month of move." That supports integration Cases 4 and 5.

  • Medicaid institutions. LTC Handbook 450.243 ("Updated December 23, 2024"): "If the SSI recipient has no other income or has countable income less than the current SSI personal needs allowance, the individual can get the SSI payment of $30.00 plus a state-issued Supplement for Personal Needs (SPN) of $22.10".

    • Gating on ssi > 0 | receives_ssi, per person and without SSA rounding, matches that text. It also matches Appendix A's 2026 couple total of $104.20 ($60 + 2 × 22.10).
    • Appendix A's "includes" note still prints "$15.00", but the 2026 totals ($52.10 / $104.20) and LTC 450.243 both give $22.10.
    • Probe: a couple both in a Medicaid facility gets SSI 30 each and pa_ssp 22.10 each.

  • Federal minimum and rounding.

    • 20 CFR 416.2020(c): "The Federal Government will not administer optional State supplementary payments in amounts less than $1 per month. Hence, optional supplementary payment amounts of less than $1 will be raised to a dollar."
    • SI 02001.005 A.2 applies the floor to the federal + SSP total. In Pennsylvania the SSP is reduced only after SSI reaches zero, so a sub-$1 SSP always stands alone and the two rules give the same result.
    • SI 02001.010: "Rounding applies only if there is a third digit ... Do not round up the fourth digit" and "Round Federal and State benefits separately". That matches ceil(floor(x × 1000) / 10) / 100.

  • Spouse deeming. SI 01320.430 D works in three steps:

    • 1: individual computation
    • 2.c–d: the couple OSS ("or the individual State supplement, if greater") minus excess over the couple FBR
    • 3.b: "The State supplement amount is the lesser of" the two

    The helper's own_payment, deemed_payment and min_ mirror those steps. Integration Case 7 pins them: min(22.10, 33.30) = 22.10.

  • Kept out of SSI income. § 299.1(c)(1): "The SSP is not considered income by the SSA in determining eligibility for SSI." pa_ssp isn't in the SSI income sources, so there is no circularity.

  • Code:

  • Wiring:

    • pa_ssp is in all four household_state_benefits year blocks (2023–2026), spm_unit_benefits, SNAP unearned (7 CFR 273.9(b)(2) "other assistance programs based on need") and HUD unearned, which is the batch convention.
    • The SNAP reference consolidation matches main's one-entry-per-document rule.

  • Hand checks: all 24 expectations. The 2026 FBR is $994 for an individual and $1,491 for a couple.

    • Unit Case 1: 22.10.
    • Case 2: 25.53.
    • Cases 3 and 4: 634.30 and 639.30.
    • Case 5: age 17 in a personal care home gives 0.
    • Case 6: SPN 22.10.
    • Case 7: 12,360 / 12 = 1,030; 1,030 − 20 = 1,010; 1,010 − 994 = 16; so 22.10 − 16 = 6.10.
    • Case 8: 1,036 − 20 = 1,016; the excess is 22, so 0.10 (state-administered, no floor).
    • Case 9: 1,037 − 20 = 1,017; the excess of 23 exceeds 22.10, so 0.
    • Case 10: resources of 2,001 give 0 (§ 299.36(a)(2)(iii)).
    • Cases 11 and 12: age 30 gives 0; Ohio gives 0.
    • Case 13: no take-up gives 0 (§ 299.36(b)(2)(iii)).
    • Case 14: 600 / 12 = 50, so 30 countable; SSI is 0 and the SPN is 0.
    • Case 15: 1,653 − 20 = 1,633; 639.30 − 639 = 0.30, raised to 1.
    • Case 16: 15,080 / 12 = 1,256.67; (1,256.67 − 85) / 2 = 585.83; SSI is 408.17 and pa_ssp is 22.10.
    • Case 17: reported receipt gives 22.10.
    • Integration Cases 1 and 2: 33.30 / 2 = 16.65 and 38.44 / 2 = 19.22.
    • Integration Case 3: 12 × 22.10 = 265.20; SNAP and HUD unearned income are 11,928 + 265.20 = 12,193.20.
    • Integration Case 4: 1,347.40 / 2 = 673.70.
    • Integration Case 5: 994 and 639.30 each.
    • Integration Case 6: documented averaging (Suggestion 3).
    • Integration Case 7:
      • own countable is 700 − 20 = 680
      • the spouse's 1,256.67 exceeds 497, so deeming applies
      • deemed income is (1,256.67 − 65) / 2 = 595.83
      • SSI is 1,491 − 1,275.83 = 215.17, and pa_ssp is 22.10

  • Changelog: changelog.d/pa-ssp-2026.added.md is top-level, typed added, and accurate.

  • Registry:

    • The programs.yaml entry sits under ssi_state_supplement.state_implementations with the WA/MO fields.
    • partial fits the unmodeled mandatory and essential-person supplements. parameter_prefix resolves.

Batch checks

  1. Axiom line: invalid (needed). No rulespec-us module or issue exists for PA SSP (Should 1).
  2. Parameter descriptions: three PA files are off-template (Should 2). The federal minimum_payment.yaml is acceptable.
  3. Backdating: the care-home rows leak $634.30 / $639.30 (and $1,347.40 / $1,357.40) back to 2015–2022, where POMS shows $434.30 / $439.30 ($947.40 / $957.40). The SPN was likely $15 before 2025. It is a documented deferral (Pennsylvania SSP 2017, 2018, 2019 #8568), so Suggestion 1.
  4. tx_rebate.py copy: it omits pa_ssp; the probe shows spm_unit_benefits down $265.20 (Suggestion 2).
  5. Aggregate wiring:
    • spm_unit_benefits, all four household_state_benefits blocks, HUD, SNAP and programs.yaml are present.
    • There is no double count with ssi.
    • Pennsylvania's own PTRR income omits the SSP the PA-1000 counts (Should 3).
  6. Income attribution:
    • It uses SSA countable income: couples combined and halved, SSP-only reduction, and SI 01320.430 deeming pinned by integration Case 7.
    • The private-pay facility and child (FLA C) paths follow SSA's 2011 definitions but aren't pinned (Suggestion 4).
    • The mixed-couple split follows SI 02005.030 G.1, not PA's PHI note (Suggestion 3).
  7. Sibling conflicts:
  8. CI: all 26 checks pass on head 5b27aceb40, with no failing job.
  9. State law first:
    • All 2026 rows match § 299.37, POMS SI 01415.058 K.2, MA Handbook 387 Appendix A and LTC 450.243.
    • The administration split, the effective date of January 2026 and the SSP-only rule match § 299.1, § 299.21 and § 299.36.
    • All 24 expectations check by hand.

Axiom line assessment

Invalid (Should 1).

CI status

All 26 checks pass (gh pr checks 10167). Three "skipping" entries belong to the superseded run 38358609883.

  • The run. Run 38367925733 (pull_request, 2026-10-13 08:14 UTC) on head 5b27aceb40, conclusion success.
  • Main since then. main has since changed only unemployment_compensation → total_unemployment_compensation in the shared income lists and tx_rebate.py, plus three programs.yaml lines. None of that affects this PR's logic.
  • Local run. The two new test files at the head with policyengine-core 3.33.2: 24 passed.
  • Partner tests. The PR touches no partner test files, and the Household API Partners job passes.

Branch status

Verdict: REQUEST_CHANGES

DTrim99
DTrim99 requested changes Oct 13, 2026
View reviewed 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.

All 2026 amounts check out against 55 Pa. Code § 299.37, POMS SI 01415.058 K.2 and MA Handbook 387 App. A, and so do the administration split, SSP-only reduction, deeming and all 24 YAML expectations. Four should items (see the comment above): (1) 'axiom: needed' isn't valid for staff and rulespec-us has no PA SSP module, so file a pe-parity issue and add a queued line; (2) three parameter descriptions are off the template; (3) PA property tax/rent rebate income omits half of pa_ssp, which PA-1000 Line 4 requires (an aged renter with a $4,900 pension gets $1,000 instead of $770); (4) the § 299.37 reference prints the old care-home rates, so cite MA Handbook 387 App. A and the POMS anchors.

This was referenced Oct 13, 2026
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
@hua7450 hua7450 mentioned this pull request Oct 14, 2026
Open

This branch has not been deployed

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

Reviewers

@DTrim99 DTrim99 DTrim99 requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@hua7450 @DTrim99