PolicyEngine / PolicyEngine/microcosm

Weeks-unemployed eligibility constraint makes its battery incidence band infeasible (max ratio 0.31 vs floor 0.8)

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

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
94

Description

Defect

The weeks-unemployed transfer's eligibility constraint makes its by-origin battery incidence band mathematically unpassable. The 25% candidate post-transfer receipt records:

  • ASEC reference positive share: 0.0330323
  • raw ACS share before calibration: 0.0060545
  • ACS share after calibration: 0.0103014, with capacity_limited=true

The spec allows positive weeks only where unemployment compensation is positive; that eligible ACS share is 0.0103014, so the maximum achievable incidence ratio is 0.0103014/0.0330323 = 0.312, far below the battery floor of 0.8. Calibration executed correctly and reached its declared capacity; the gate/spec pair is infeasible by construction. (The residual 1% variant without this constraint reached a ratio near 1.0007.)

Fix direction (owner adjudication)

Reconcile the constraint with the band: widen the eligibility rule, re-scope the comparison to the eligible subpopulation, or mark the leg diagnostic under the constraint. Adjudicated spec change with receipts, not a band tweak.

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 by reviewing the weeks-unemployed transfer, its unemployment-compensation eligibility constraint, the battery incidence-band gate, and the cited calibration receipts. Establish an adjudicated spec change—widen the rule, scope the comparison to the eligible population, or mark the diagnostic under the constraint—and consider the issue done when the receipts demonstrate that the resulting specification is coherent.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
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.