[juaristi22]

Placeholder for the next update of the UK data pipeline and calibration-targets pages (/uk/model/data/pipeline, /uk/model/data/calibration). It is for when policyengine.py certifies the next Microcosm UK pair, now being built on 90ff43f with policyengine-uk 2.162.12 and one unreleased engine change. Its one commit updates a label the extraction will need. It holds no page or data changes yet.

Already done

• A dry run of the extraction on the next pair's first local-area attempt reads every target.
• It found that the Child Benefit families row, new in this pair, filters on payment status as well as number of children. This PR re-keys its label to number_of_children,payment_status.
• With that change, every row is labelled and every label is used, including the local-area Council Tax single-adult discount label added in Describe the Microcosm UK pipeline and calibration targets, and update UK validation and capital gains copy #56.

When that policyengine.py version is out

1. Re-check the pipeline page against the Microcosm code the certified pair was built from. The page is src/data/ukPipelineStages.ts and the UK intro in src/components/data/DataPipeline.tsx. Compare it with:
   • uk/source_stages.json;
   • the gates and their scopes in uk_runtime/calibration_run.py;
   • the solver settings in the uk_runtime doctrine files.
2. Set ukPipelineSource.commit to the commit on main that carries that code, and ukPipelineSource.modelVersion to the policyengine-uk version the release was certified with. That is 2.162.12, or the policyengine-uk release that carries the unreleased engine change. Do this before the extraction, because the extractor refuses releases built with another engine version.
3. Regenerate src/data/ukCalibrationTargets.json from the certified pair's files, using the bundle manifest of the certifying policyengine.py version.
   • Then run the committed-JSON check: scripts/test_extract_uk_calibration_targets.py, with the four release-file variables set.
   • The release files are licensed, so this runs only on a licence holder's machine.
4. If the national file brings a row key the dry run could not see, add its label. The script names any unlabelled key.
5. Run the UK vitest files, the extractor tests, eslint and tsc --noEmit. Check both pages at 375 px and 1440 px.
6. Before pushing, run an independent disclosure-control review of the diff and the PR text. Then mark this ready.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
policyengine-model	Ready	Preview	Oct 27, 2026 6:08pm UTC