PolicyEngine / PolicyEngine/microcosm
Verify US wealth, property, and asset imputation backlog
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 94
Description
Source backlog
Copied from policyengine-us-data issues/PRs that still matter to Populace's US input surface:
- PolicyEngine/policyengine-us-data#1079, #1080, #1081 / PR #1085: ACS primary residence value imputation and publication.
- #230: home equity from SCF.
- #267, #281: vehicle ownership / auto-loan eligibility inputs.
- #835: net-worth aggregate decomposition.
- #734: replace SCF net-worth target with Fed Financial Accounts net worth.
- Related SPM/source-gap items may overlap with #32.
Populace direction
Populace already declares SCF wealth stages and scf_primary_residence_value; this issue is to verify the PE-US-facing variable surface and target/diagnostic coverage are complete.
Acceptance criteria
- Inventory each wealth/property/asset variable as populated, upstream-populated, formula-computed, diagnostic-only, or reviewed-excluded.
- Confirm whether
primary_residence_valueitself, home equity, vehicles, auto-loan variables, and net-worth components are present in the published PE-US input surface when needed. - Add source-stage specs and tests for any missing source-backed inputs.
- Use Fed Financial Accounts / other external benchmarks as diagnostics or hard targets only after source role is explicitly classified.
Part of #46.
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 declared SCF wealth stages and scf_primary_residence_value, then compare them with the published PE-US input surface and the upstream issues listed here. Add source-stage specs and tests for missing source-backed inputs. Done means every variable has an explicit population status and external benchmarks are clearly classified as diagnostics or hard targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100