Skip to content

Align Washington property tax exemption age with the collection year - #10839

Merged
MaxGhenis merged 4 commits into
mainfrom
wa-pte-collection-year-age
Nov 14, 2026
Merged

MaxGhenis merged 4 commits into
mainfrom
wa-pte-collection-year-age

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

From collection year 2020, Washington claimants aged 61 previously qualified through the senior property tax exemption pathway. We now require age 62 at collection-year end, matching age 61 at the preceding filing-year deadline.

We previously cited E2SHB 1105 (2019 c 332), which our reference named ESHB 1105, for a cut from 62 to 61 in 2020. In that act, the Legislature amended RCW 84.56.020, 84.64.225, 36.35.110 and 84.64.050 and added sections to chapters 84.56, 36.29 and 36.21. It left RCW 84.36.381 unchanged.

Senior claimants must reach 61 by December 31 of the filing year and receive relief on taxes due the following year. The Legislature kept that timing in 2008 c 6 §706, 2015 3rd sp.s. c 30 §2, 2019 c 453 §1, 2025 c 200 §1 and 2026 c 163 §101. The Department of Revenue describes the same assessment-year and following-tax-year cycle in PT0017, page 1.

We retain the veteran policy dates: VA compensation and a total rating from collection year 2016, the 80% combined-rating route from 2020, and 40% from 2027. See the application provisions in 2015 §4, 2019 §9 and 2025 §3.

Historical calculations also need a combined-rating parameter before 2016 because the formula reads it before selecting the applicable pathway. We provide infinity from 2008; the existing gate continues to select the pre-2016 veteran pathway through 2015.

We clarify why the existing pre-2016 proxy does not require SSDI receipt: claimants need insured status and an application for SSDI under 42 U.S.C. 423(a). Under the ruling recorded in source-conflict candidate us-wa:pte-veteran-pathway-pre-2016, Washington incorporates only the disability definition. We also restore the space in 423 (d)(1)(A) in that candidate's question.

This addresses the age follow-up in #10330.

Invariants and tests

Pull request run 43626652995 at 7f324be43d passed all 37 jobs on GitHub's merge with main 8b2fba3884.

  • Eligibility cannot fall when age increases with other inputs fixed. Disability retirement still qualifies Washington claimants, and claimants outside Washington remain ineligible. test_wa_pte_collection_year_age_invariants checks these properties and the veteran boundaries.
  • For collection years 2008, 2015, 2016, 2019, 2020, 2026 and 2027, the same test requires categorical eligibility to equal the modeled pathways. A Washington claimant qualifies at 62 or older in the collection year, through disability retirement, or through that year's veteran pathway.
  • Against main, we remove categorical eligibility from 2020 only for claimants aged at least 61 and under 62 who have no other qualifying pathway. We also make categorical eligibility computable for 2008–2014, where main raises a missing-parameter error.
  • wa_pte_categorical_eligible.yaml checks ages 61 and 62 in those seven years, plus mixed pathways. integration.yaml checks the $0 and $3,600 household outcomes; comments show the arithmetic.
  • YAML validation: categorical eligibility 37 passed, eligibility 9 passed, integration 16 passed, exemption amounts 18 passed and tiers 14 passed.
  • test_wa_pte_collection_year_age_invariants: 1 passed with 10 generated populations and an explicit boundary example. A local macOS run on a loaded host, separate from Linux CI, took 44.90 seconds in pytest and peaked at 1,072 MiB. CI runs the test in the core Python group. CI run 38141803955 measured that group's peak memory at 13.3 GB and its wall time at 11:51, before the SSI resource-deeming test moved to core-heavy (Makefile, lines 38–50 and line 69). The test reuses the shared tax-benefit system and builds one simulation of at most 60 people per example.
  • Both mutants failed their targeted tests. Restoring age 61 from 2020 failed Cases 1, 21, 34, 35 and 36 in wa_pte_categorical_eligible.yaml, Case 15 in integration.yaml and the Python test. Removing the 2008 rating value failed Case 30 and the Python test with a missing parameter.
  • Changed Python files pass Ruff formatting and lint checks. test_source_conflicts.py: 103 passed.

Methodology choices

  • Treat the period as the collection year and annual age as age attained by December 31. Keep the existing parameter name and date the veteran policy by collection year.
  • Use an inert historical rating threshold to permit eager evaluation; retain the 2016 gate and later rating thresholds.
  • Retain current-period income and disability inputs as existing proxies for filing-year facts. The pre-2016 disability proxy still cannot establish service connection.
  • Add no age source-conflict candidate: the statutes and Department guidance agree. Clarify the existing veteran candidate without changing its ruling.
  • Leave the age-57 pathway for a surviving spouse or domestic partner in RCW 84.36.381(3)(b) unmodeled, as on main. PolicyEngine has no input for the deceased claimant's exemption.

Microsimulation impact

n/a: no variable, parameter list or adds/subtracts entry outside the exemption's own files reads wa_senior_disabled_property_tax_exemption, wa_pte_eligible or wa_pte_categorical_eligible, so household net income, taxes and benefits match main.

axiom: TheAxiomFoundation/rulespec-us#1863 queued (RCW 84.36.381(3)(a); no signed corpus scope holds RCW 84.36.381, WAC 458-16A-130 or the session laws that date it, so the signed encoder can't run yet)

🤖 Generated with Claude Code

MaxGhenis and others added 4 commits November 12, 2026 01:03
Use age 62 at collection-year end to apply the statutory age-61 filing-year deadline. Keep the veteran transition dates and add boundary and invariant coverage.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Provide an inert combined-rating threshold before the VA-rating pathway begins. This lets the categorical formula evaluate the statutory age and historical disability pathways from 2008.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Distinguish SSDI payment requirements from the incorporated disability definition. Preserve the historical citation spacing in the existing source-conflict question.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The property test compared each result with the age values this branch
removes: 62 before 2020 and 61 from 2020. The collection-year check
already requires eligibility to equal a qualifying pathway or age 62, so
the test still fails if someone restores 61 from 2020.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis marked this pull request as ready for review November 14, 2026 16:40
@codecov

codecov Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (aae7f98) to head (7f324be).
⚠️ Report is 272 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main    #10839   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         2    +1     
  Lines           37        32    -5     
=========================================
- Hits            37        32    -5     
Flag Coverage Δ
unittests 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@MaxGhenis

Copy link
Copy Markdown
Contributor Author

US + core hub merge audit, us#10839 at 7f324be43d96510ce922c2f80321e1447e966452 (squash): Align Washington property tax exemption age with the collection year.

  • Reviews:
    • The PR has no GitHub reviews. Two independent review rounds ran outside GitHub, with a fix round between them.
    • The first round, at 57f286d633, read the 2008, 2015, 2019 and 2025 session laws, 2019 c 332, DOR's PT0017, current RCW 84.36.381, WAC 458-16A-130 and the 2004 edition of 42 U.S.C. 423. It found the age change right in law: each act keeps 61 on December 31 of the filing year, and 2019 c 332 never amends RCW 84.36.381. It computed King County households by hand and ran 16 on the head and on the merge base 935b24ff4f, and every computed result matched its hand figure.
    • In those runs, a claimant aged 61 with no other pathway fell from $3,600 to $0 in 2020 and 2024 and from $4,450 to $0 in 2027. Every other computed result stayed the same. Its full household calculations for 2008, 2012 and 2014 raised errors at both commits: on combined_rating_threshold at the merge base, and on federal parameters at the head.
    • It also ran the head's YAML files on the merge base's code. Cases 1, 21, 34, 35 and 36 of wa_pte_categorical_eligible.yaml and Case 15 of integration.yaml failed on age, and Case 30 failed on the missing 2008 parameter.
    • It asked for a microsimulation estimate or a reason for none, and for the description to say why main held 61 and to drop local-run detail. It also noted that the property test compared results with main's superseded ages.
    • The fix round, at 7f324be43d, changed one test file. It dropped the two assertions that compared results with main's ages, after a mutant that restored 61 from 2020 still failed the assertion it kept. By git grep, it found that outside the exemption's own files and the source-conflict register, only this PR's test names the exemption's amount and eligibility variables. In the description, it added the reason for no estimate and the paragraph on 2019 c 332. It removed the other local-run detail and kept the property test's local time and peak memory, as the repository's CLAUDE.md asks.
    • The second round approved 7f324be43d with no blocking finding. It showed that both dropped assertions follow from the kept one. With 61 restored from 2020, the property test failed at line 191, and Cases 1, 21, 34, 35 and 36 and integration Case 15 failed again.
    • It also ran a grid of nine ages, four pathways and collection years 2008 to 2027. The head matched the rule, a pathway or age 62 or older, in all 720 cells. The merge base raised a missing-parameter error for 2008 to 2014 and, from 2020, differed from the head only for ages from 61 to under 62 with no other pathway. Seven King County households kept the same net income, tax and benefits at both commits.
    • At 7f324be43d, the fix round's runs passed 37, 16 and 9 cases in the three YAML files this PR changes and 18 and 14 in the exemption-amount and tier files. They also passed the property test and the 103 tests of test_source_conflicts.py. The second round reran the categorical and integration files, the property test and test_source_conflicts.py, with the same counts.
    • The second round listed three minor findings. The description called the 2019 act ESHB 1105, where its cover reads "ENGROSSED SECOND SUBSTITUTE HOUSE BILL 1105", and the description could cite the core test group's CI figure. Commit 7f324be43d's message says the branch removes 62 before 2020, where the branch keeps 62 from 2008 and removes only the 2020 value of 61.
    • I made both description changes before merge, and the squash message leaves that sentence out. I also made six changes the reviews didn't list. The description now names 2026 c 163 s 101 among the acts that keep the age wording, and names the Legislature as the body that kept the filing-year timing. It calls the pre-2016 pathway a veteran pathway, and it names the source-conflict candidate whose ruling it cites, us-wa:pte-veteran-pathway-pre-2016. It says the property test checks the modeled pathways, and it discloses that the model has no age-57 pathway for a surviving spouse or domestic partner.
  • Methodology choices for maintainers:
    • The period stands for the collection year, and annual age for the age a claimant reaches by December 31 of that year. The statute's 61 applies a year earlier, at the filing-year deadline, so the senior pathway compares age with 62. A maintainer who reads the period as the filing year would set 61 and move the veteran thresholds, which follow collection years, a year earlier.
    • Only age moves to the filing-year basis. Income, disability retirement and veteran facts still come from the collection year's inputs, while DOR says an applicant must "meet all qualifications in the assessment year" (PT0017, page 1). The description lists those inputs as existing proxies.
    • combined_rating_threshold holds infinity from 2008 because the formula reads it in every year. The value opens no rating route, and rating_requirement_in_effect, false before 2016, still selects the pre-2016 veteran pathway. A formula that read the threshold only from 2016 would need no placeholder.
    • The PR adds no source-conflict candidate for age, since RCW 84.36.381, WAC 458-16A-130 and PT0017 agree. It edits the ruled candidate us-wa:pte-veteran-pathway-pre-2016: a 2004-edition source for 42 U.S.C. 423, a note on 423(a) and the space in the quoted 423 (d)(1)(A). The ruling stays.
    • Beyond its title, the PR adds the 2008 rating value, cites the 2015 session law in two veteran parameters, and adds the 423(a) note and the candidate edit. The first review checked each piece and accepted them in one PR.
  • Gates checked live at merge:
    • gh pr checks exits 0;
    • the latest Pull request run at the head, 43626652995, passed and tested this head merged into main at 8b2fba3884;
    • MERGEABLE;
    • not a draft;
    • no reviewer's latest review requests changes;
    • the semantic-overlap guard: since 8b2fba3884, main has changed no area this PR touches. Between the PR's merge base 935b24ff4f and main at 99d740496b, main changed one file this PR touches, source_conflicts/candidates.yaml, where it added and edited other candidates and left us-wa:pte-veteran-pathway-pre-2016 alone. Main also added one KNOWN_UNMARKED entry, for an IRS indexing parameter, to test_source_conflicts.py, which checks that file. Main changed nothing under states/wa/dor. On the merged tree, only this PR's test names the three variables outside the exemption's own files and the source-conflict register. Fix WA property tax exemption crash for households outside Washington #10113, which fixes a crash in the exemption for households outside Washington, hasn't landed. It touches none of this PR's files and merges with this branch without conflict. The branch merges into main at 99d740496b without conflict;
    • the merge pins the head.
  • Impact: n/a for household net income, taxes and benefits. No variable, parameter list or adds/subtracts entry outside the exemption's own files reads wa_senior_disabled_property_tax_exemption, wa_pte_eligible or wa_pte_categorical_eligible. The household tests show the change: the exemption falls to $0 for a claimant aged 61 in a collection year from 2020 who has no disability or veteran pathway.
  • Next:
    • Full household calculations of the exemption still fail before 2015: gov.irs.gross_income.sources starts in 2010, and the 401(k) contribution limit starts in 2018 and reaches back to 2015 only. This PR makes person-level categorical eligibility computable for 2008 to 2014, and an issue can cover the rest.
    • The description gives a local macOS time and peak for the new property test. A maintainer can add the Linux figure once a core shard reports it.
    • At the head, the 2019 act's PDF address appears only in the dead-link register, known_dead_reference_urls/west.toml, so the E2SHB designation needs no code change. The squash replaces commit 7f324be43d's message, so its sentence needs none either.
    • age_threshold.yaml's references stop at 2025 c 200. In 2026 c 163 s 101, the Legislature amended RCW 84.36.381 again for collection years from 2027 and kept the age wording, and a follow-up can cite it.
    • The model has no pathway for a surviving spouse or domestic partner aged 57 or older (RCW 84.36.381(3)(b)), on main or on this branch. An issue can add an input for the deceased person's exemption.
    • wa_pte_va_total_disability_rating.py, from main, cites 38 CFR 3.340 at law.cornell.edu. A follow-up can point it at a government copy.
  • Axiom: Washington senior and disabled property tax exemption: disability retirement and dated veteran ratings (RCW 84.36.381(3)(a)) (PE-US #10330) TheAxiomFoundation/rulespec-us#1863 queued, the open pe-parity issue for RCW 84.36.381(3)(a). A comment corrects its Case 21 row and adds companion rows from this PR's YAML: the age cases, the 80% veteran in 2019 and 2020, and the two King County owners. The signed encoder can't run yet: no signed corpus scope holds RCW 84.36.381, WAC 458-16A-130 or the session laws that date it, and rulespec-us's pinned release carries no Washington title 84 scope.

🤖 Generated with Claude Code

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant