PolicyEngine / PolicyEngine/microcosm

SNAP OBBBA work requirements: restore data inputs needed for household exposure analysis

Open
#248 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
94

Description

Problem

Populace's SNAP spending baseline is strong nationally, but the dataset is not yet ready for precise household-level OBBBA SNAP work-requirement exposure analysis.

The biggest issue is not only target calibration. It is input parity: PolicyEngine-US has work-requirement rules, but Populace must carry the data inputs those rules read. When the inputs are absent, PolicyEngine defaults can make the rules look operational while masking the actual exposure channel.

Current status

Core child issues:

  • #242: carry hours-worked inputs through Populace US outputs.
  • #243: carry SNAP reported amounts and take-up inputs through Populace US outputs.
  • #244: carry SNAP eligibility and exemption inputs through Populace US outputs.
  • #249: carry SNAP work-program participation inputs or assumptions through Populace US outputs.
  • #250: carry local geography needed for SNAP ABAWD waiver modeling.

Related broader parity/data issues:

  • #225: broader citizenship / SSN / immigration-status gap.
  • #32: SPM input gaps that overlap SNAP deductions/resources.
  • #49: wealth/property/asset backlog relevant to SNAP resources.

Acceptance criteria

  • The linked issues cover all currently known Populace data blockers for OBBBA SNAP work-requirement analysis.
  • Each child issue is small enough to map to a reasonably scoped PR.
  • The final Populace H5 can support SNAP work-requirement diagnostics without silently relying on the 40-hours/week default or all-eligible take-up defaults.
  • Remaining unsupported inputs are explicitly documented in release diagnostics or issue bodies.

Related rules work

PolicyEngine-US state/local rules gaps are tracked separately in PolicyEngine/policyengine-us#8820.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading child issues #242, #243, #244, #249, and #250, then review PolicyEngine/policyengine-us#8820 for the separate rules gaps. Done means the child issues cover the known input blockers, the Populace H5 supports work-requirement diagnostics without silent defaults, and unsupported inputs are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.