PolicyEngine / PolicyEngine/policyengine-scorecard

UK compute campaign, run 3: paired runs to size the OBR divergence axes (employee incidence, CY interpolation, announcement baselines)

Open
#78 0 comments 0 reactions 1 assignee View on GitHub

@vahid-ahmadi is already working on this.

Since Aug 20, 2026.

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

Description

The divergence registry (#67, approved) carries its biggest components as unsized with sizing recipes — each recipe is a paired managed run. This issue executes them, converting the employer-NICs picture (observed gap −£7.36bn, like-for-like disagreement −£12.67bn) from labelled-honest to decomposed.

The paired runs

  • employee_incidence_and_base (the dominant driver): re-run the employer-NICs measures with the incidence parameter at OBR-comparable settings vs PE's employee_incidence = 1 construction; the delta between paired runs sizes the component. This is the −£8.5bn income-tax-head question.
  • cy_proxies_fy: compute each measure at both adjacent CYs and interpolate to the FY — sizes the axis exactly, per the registry recipe.
  • baseline_vintage: re-run against announcement-time baselines where the #71 baselines registry (53 registered worlds) carries the leg; where it does not, register the world first — the registry exists precisely so these runs are attributable.
  • Re-emit the decomposition artifacts: components re-classified explains_gap/masks_gap with values, divergence_understated updated, residuals shrunk or honestly kept.
  • Any residual that survives the sized axes files as a policyengine-uk issue with the Scorecard rows as evidence — the #59 model-development loop.

Depends on #67 merging and shares the managed session with #76/#77-era runs.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.