PolicyEngine / PolicyEngine/microcosm
Track SPM-specific input gaps: housing, WIC, school meals, child support, workers comp, and expense deductions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
Problem
SPM-specific poverty resource and deduction components need explicit Populace handling so the resource definition is complete and release diagnostics show unsupported families rather than silently omitting them.
Relevant families:
- HUD housing assistance / capped housing subsidy resources.
- USDA WIC resources.
- USDA school lunch/breakfast resources.
- HHS OCSE child support received and paid.
- Workers' compensation benefits.
- MOOP, work expenses, and childcare expense validation/imputation benchmarks.
Scope
For each family:
- Identify the relevant PolicyEngine-US input/output variables and whether Populace should store an input, impute an upstream input, or let the engine compute a formula-owned variable.
- Identify source status and whether an Arch source package exists.
- If source data are missing, make release diagnostics report the family as unsupported/source-gap.
- Once source-backed inputs exist, add Populace imputation/target mapping and tests.
Acceptance criteria
- A Populace US SPM component inventory exists with model variables, formula/store decision, source status, and release behavior.
- Missing source families are surfaced in release diagnostics/manifest as source gaps.
- Populace does not hard-target CPS SPM values to fill these gaps.
- Where source-backed inputs are available, tests confirm inputs or upstream formula inputs are populated.
Contributor 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.
Research direction
Start by inventorying the listed PolicyEngine-US SPM variables, their formula/store decisions, and whether an Arch source package exists. Then inspect the release diagnostics/manifest and existing Populace mappings; done means every family is classified, source gaps are surfaced, CPS SPM values are not hard-targeted, and source-backed inputs have coverage tests.
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
- Needs clarification
- Newbie friendliness
- 30/100