PolicyEngine / PolicyEngine/policyengine-app-v2

Show federal vs. state fiscal impact in budget view

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

Nobody has claimed this yet.

Dominant language
HTML
Stars
1
Forks
3
Avg merge
1d 50m
Merged PRs (30d)
39

Description

Context

PolicyEngine-US and policyengine-api are adding federal vs. state fiscal impact attribution (see PolicyEngine/policyengine-us#8075, #8076). The app does not currently show a federal/state split in budget impact views.

Proposed change

On the budget/fiscal-impact section of the reform output:

  1. Add a stacked bar (or two side-by-side bars) showing federal vs. state fiscal impact of the reform, alongside the existing total.
  2. Detailed budget table: add columns for "federal" and "state" next to the existing "difference" column, so per-program attribution is visible (the existing detailed_budgetary_impact keyed by program becomes a matrix of program × level-of-government).
  3. Copy update on the fiscal impact narrative: current phrasing conflates "federal fiscal impact" with total cost. Distinguish once the API exposes the split.

Dependency

Blocked by policyengine-api change to expose federal_budgetary_impact and state_budgetary_impact (separate issue). Variables already exist in policyengine-us post-#8076: federal_benefit_cost, state_benefit_cost, and per-program medicaid_federal_cost / medicaid_state_cost / chip_federal_cost / chip_state_cost.

Why this matters

For reforms that shift cost between levels of government (Medicaid expansion rollback, OBBBA SNAP state match, FMAP changes), the fiscal story is federal-vs-state, not aggregate. Users currently can't see this from the app.

Related

  • PolicyEngine/policyengine-us#8075 (scoping)
  • PolicyEngine/policyengine-us#8076 (Medicaid + CHIP attribution)
  • policyengine-api issue for the API surface

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 the budget/fiscal-impact section of the reform output and trace how detailed_budgetary_impact and the existing total are rendered. Confirm the policyengine-api fields federal_budgetary_impact and state_budgetary_impact are available before changing the view. Done means federal and state values appear in the chart, per-program table, and narrative without conflating them with the total.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.