PolicyEngine / PolicyEngine/ccdf-calculator

Clarify population comparison years and validate sensitivity of headline estimates

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Population impact currently shows:

  • 16,853,856 qualifying children (31.4% of under-13s).
  • Approximately $151.5 billion potential annual subsidy.
  • 1,606,000 children served and 9.5 served per 100 who would qualify.
  • Qualifying shares of 73.5% in Vermont and 60.6% in Maine.

These outliers are validation targets, not proven errors. The model uses 2026 rules and assumed care, while the observed caseload is an average month of FY2023. The dates appear in explanatory text, but the ratio's own label does not make the cross-year comparison apparent and may be read as a current take-up rate.

Suggested improvements:

  • Label the ratio directly as FY2023 served / modeled 2026 qualifying, or align years where feasible; explain it is not a measured current take-up rate.
  • Round modeled headline counts to defensible precision (e.g. 16.9 million); retain detailed values in downloadable data if useful.
  • Validate high-share states and document sensitivity to care assumptions, activity rules, dataset/state calibration, and counting definitions.
  • Keep the hypothetical nature of the $151.5B scenario prominent and document the scope of the “upper bound” claim.

Sources: src/components/Impact.tsx, public/data/impact.json, public/data/acf_served.json.

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 in src/components/Impact.tsx and inspect public/data/impact.json alongside public/data/acf_served.json to trace the displayed years, ratios, counts, and state shares. Compare the modeled 2026 values with the FY2023 served data, then define the validation and sensitivity checks; done means the ratio and hypothetical upper-bound scope are explicit, headline precision is defensible, and high-share states and assumptions are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
analytics, data, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.