PolicyEngine / PolicyEngine/snap-qc-sim
Scenario lever: adopt a verified rules engine
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 5
Description
A lever showing each state's measured-rate distribution with computation-caused error removed — what mechanically changes if benefit computation runs on a verified engine (the one channel where the accounting identity IS the mechanism: correct arithmetic on the same facts). Needs (1) a per-state computation/agency-cause error-dollar share artifact from the FY2024 QC file's element-level finding codes, with field semantics verified against the technical documentation before use; (2) the Colorado engine-verified anchor (the replay's partition of error cases) as the calibration reference; (3) honest labeling: fact-errors untouched, the bound is on the computation channel only. Dispatch the artifact leg first; app wiring after.
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 locating the FY2024 QC file and its technical documentation, then verify the element-level finding-code semantics before using them. Build the per-state computation/agency-cause error-dollar share artifact and compare it with the Colorado engine-verified replay; done means fact-errors remain untouched and the computation-only bound is labeled honestly.
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
- Mostly clear
- Newbie friendliness
- 55/100