PolicyEngine / PolicyEngine/policyengine-scorecard

Reform-score adapters (mode 2: deltas, not levels)

Open
#4 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
0
Avg merge
6d 12h
Merged PRs (30d)
32

Description

Run reform pairs on the certified artifact; compare scores. Ledger already carries JCT reform facts (populace reform validation uses them — calibration_relationship: consumed for those; held_out for new ones).

  • JCT tax expenditures + revenue estimates
  • CBO cost estimates (per-bill lanes)
  • TPC distribution tables
  • Tax Foundation
  • PWBM
  • Yale Budget Lab

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

No files or tests are named. Start by locating the certified-artifact scoring entry point and the Ledger's existing JCT reform facts, then trace how calibration_relationship marks consumed versus held_out data. Done means reform-pair score deltas are compared for JCT, CBO, TPC, Tax Foundation, PWBM, and Yale Budget Lab analyses.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.