Scenario refresh: state SSA disability status and dependent relationships explicitly
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Locate the scenario definitions for scenario_064, scenario_067, and the scenario_121 family referenced from #92. Review how disability status and dependent relationships are represented, then update the scenarios so SSI eligibility and MAGI household membership are explicit. Done means the listed scenarios no longer leave those interpretations to convention.
Written by the indexing model from the issue text.
Description
From the #107 adjudication: two scenario-design ambiguities cause defensible-either-way cells. (1) Scenarios setting is_disabled leave is_ssi_disabled unset (false per convention), so SSI = $0 while a careful reader assumes SSI eligibility — scenario_064, scenario_067, and the #92 scenario_121 family. (2) Adult dependents never state their relationship to the filers, which determines the MAGI household under 42 CFR 435.603(f)(2) — scenario_064 dependent1 (27), scenario_067 dependent1 (23). Both belong in the next scenario/reference refresh alongside #92.
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policybench
-
v2 prompt and data: program-specific disability facts, integer inputs, and the take-up boundaryOpen
Difficulty 5/5 Over a week Newbie friendliness 38/100
PolicyEngine/policybench#165 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/policybench#145 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
PolicyEngine/policybench#140 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/policybench#139 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PolicyEngine/policybench#129 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/policybench
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
uniswap-python/uniswap-python#487 ·
-
[Bug]: agent_final_response still returns the abandoned branch's answer after navigate moves HEAD backPossibly taken @enyst claimed this today. Openbug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/software-agent-sdk#5822 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
area: server enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
scs0209/laya-guard#52 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days