PolicyEngine / PolicyEngine/ccdf-calculator

Use a reference month or explicitly distinguish annual eligibility from current eligibility

Open
#4 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

For Indiana, select one adult, one preschooler age 3, annual income $30,000, $1,500/month provider charge, and default care/provider inputs.

The committed grid shows $224.76/month and the headline says “Eligible.” Direct monthly model reads give approximately $674.27/month in January–April 2026 and $0 in May–December. The displayed value is the annual total divided by 12, and the grid eligibility flag means eligible in any month.

The methodology explains averaging, but a user seeking assistance under September 2026 rules can reasonably interpret the headline as a current monthly payment. The repository already records the month-snapshot design as an open decision; this issue tracks resolving it.

Prefer a visible reference month shared by calculator, comparison, and live requests. Alternatively, label the result explicitly as an annual average and show eligible months/current-month status beside the amount. Do not retain a generic current-looking “Eligible” badge for a household eligible only earlier in the year. Update related data contracts and regression coverage.

Sources: scripts/precompute.py, docs/PLAN.md, src/components/CalculatorResults.tsx.

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 with docs/PLAN.md to understand the open month-snapshot decision, then inspect scripts/precompute.py and src/components/CalculatorResults.tsx. Trace the calculator, comparison, and live-request data contracts and existing regression coverage. Done means the chosen eligibility and amount presentation is consistent across these paths, with updated contracts and tests covering the January–April and May–December example.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, python, typescript
Domain
data, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.