Skip to content

UK: take up #1095's actionable items on policyengine-uk 2.165.1 (draft) - #1422

Open
juaristi22 wants to merge 31 commits into
mainfrom
uk-1095-next
Open

juaristi22 wants to merge 31 commits into
mainfrom
uk-1095-next

Conversation

@juaristi22

@juaristi22 juaristi22 commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Draft, not ready for review. Main is merged in after #1420 and #1421, the lock moves to policyengine-uk 2.165.1, and the national and local target surfaces are regenerated once on the pinned feed (Chronicle 53815b2). Phase B (the spine and calibration items) follows on this branch.

Summary

This PR takes the engine-free items of #1095 that María ruled on 29 October (Phase A), and the first re-bump past #1421 (Phase C): policyengine-uk 2.165.1. The spine and calibration items (Phase B) follow on this branch, each measured in its own arm.

policyengine-uk 2.165.1

The lock moves from 2.164.2, which #1421 brought, to the newest release.

Regeneration on feed 53815b2

The national and local references, membership and compile-parity receipts are regenerated once on the merged tree, on main's feed pin (Chronicle 53815b2, #1420's re-pin). The vendored resources check against the full artifact unchanged. The local census, the local references, the local parity receipt and the coverage manifest regenerate unchanged.

  • National surface: 1,409 active references, up from 1,403, and no row left without a fact (four before). The new rows are the three OBR council tax nation rows (D14e) and SLC's three nation rows (R4). The DfE rows, the R7 windows and obr.council_tax move as described above. The incumbent's three devolved SLC metrics now match the nation rows exactly.
  • Local surface: 27,168 active references, every status count unchanged. The signed deferrals fall from 94 to 77, as the support-floor deferrals now follow each target's nations.
  • A window fix the regeneration found: R7's calendar-2025 window on dfi_ni.bus.passenger_receipts failed to compile, because its selector pins two services and the window counted series only from list-valued source keys. A dimension pinned to several values now names one series per value. The window of the sum is the sum of the windowed series, and a service short of a year refuses the window. No other UK, US or NZ window reference pins several dimension values.

Targets

  • OBR council tax by nation (D14e): the three nation rows are pinned to the UK and held as measured diagnostics.
  • Declared geography wins (R8, R9): a selector's declared geography_id is returned before the inferred pin, and the authoring refuses a disagreeing pin.
  • SLC devolved repayments (R4): slc.repayments.devolved_total becomes one row per nation. Wales binds. Scotland and Northern Ireland are held out, by María's ruling. Their 2024-25 outturn binds at the 2025 period under a matched-period hold she signed on 29 October.
  • Calendar-2025 window (R7): Scottish Child Payment, the TFC top-up, Northern Ireland bus receipts and the four SLC England repayment rows.
  • Ledger observation_period: a reference can select its facts at a declared period while the target keeps its own.
  • DfE (D5): the eight rows bind the January 2026 census at model year 2025. The three in_year_snapshot holds are retired.
  • Window-ratio complement: a numerator can be its denominator less the listed cells.
  • OBR council tax (D14f): binds the main-residence share: England's chargeable dwellings less second homes and empty homes, over chargeable dwellings (MHCLG, October 2025, about 0.968). Scotland and Wales take England's share, as a stated approximation.
  • Signed exclusions: D3 keeps Scotland's three-plus-children rows out with a corrected reason. D18a signs the MSOA income deferral. D18c keeps Northern Ireland's UC area cells out.

Spine and stage records

Gates

  • Zero-weight strata (Adjudicate the UK spine grain at the ingest/calibration seam #688): both SPI-synthetic strata are capped at 0. The June caps of 100,000 counted the retired ten-clone grain, and the national seam ships no zero-weight row.
  • Export surface (WS-E spine deferrals: known bugs and signed inconsistencies awaiting their increment #796): the all-zero incapacity_benefit_reported exclusion never matched the pinned reference, so it is dropped. The release boundary still drops the column.
  • macro_realism (Swap the microcosm-built UK spine into the national build and retire the incumbent feed #757): not declared, and the battery's policy text records why. The solve binds the income components directly, and the national accounts' household disposable income differs in scope. The release contract refuses a not_applicable entry in this spec vintage.
  • Take-up flags at their stages (María's ruling, "do both"): frs_take_up, frs_person_draws and frs_household_draws record their flags' shares at the stage's weights. Three assembled-phase gates hold them to their contract targets, at the terminal gate's bounds until a spine receipt measures them. The terminal uk_take_up_signal gate stays release-blocking.
  • The battery, spine-part, release-cut and dense digests in microcosm-data's contract move with the manifest.

Disclosure floor of 3 (A1)

María ruled on 29 October to move every UK disclosure floor from ten source households to three, CD171's absolute floor. One constant, receipt_counts.UK_DISCLOSURE_FLOOR, now sets it for the stage receipts, the stage-health gates and the report tools. A withheld figure reads "<3", and banded counts gain a "3-9" band. The statistical floors stay: the zero-support floor, the private-rent tool's ten-row group rule, and the SPI coherence tool's floor for medians and quantiles. The signed rules in local_small_cell_rule.json defer published cells, not survey cells, so they are unchanged.

Default UK load (#823): a change for every consumer

microcosm.data.load("uk") now follows latest-national.json. That pointer names the certified national cut promoted on 26 October (microcosm-uk-2024-25-national-20261025T091414Z-a6299504, built on policyengine-uk 2.151.0). The default used to be the June 2023 populace_uk_2023 artifact, which stays at load("uk", 2023). The national variant key retires.

Text

Stale tracker text in notes, docstrings and the vendored bus resources' purposes. The Incapacity Benefit leaf note now names the FRS 2024-25. The charter-H2 fixture and the release input coverage manifest follow the stage contract digests.

Not in this PR yet

Tests

  • Engine tier on policyengine-uk 2.165.1 (at e40eabd1b, before the regeneration): every UK engine test passes, run in full locally because CI stops at the first failure. Three needed updates: Tax-Free Childcare's top-up now lives in a shared helper, which still reads the spend the build routes; the company car's list price and capital contributions are person-level stocks that are no one's capital; and the graph build's stage records list each stage's rewrites beside its outputs (Carry manifest rewrites into the shared Stage/StageRecord producer graph #721).
  • Engine-free suite: before the regeneration, the merged surfaces passed (1,075 and 571 tests) bar the one test that waited for it. The full suite on this head is running locally in 30-file chunks, and the feed-reading tests run one file at a time after it.
  • Checks: tools/ci_test_plan.py verify, tools/spec_engine_coverage.py --check, the vendoring check against the full artifact, and ruff on the edited files.

🤖 Generated with Claude Code

juaristi22 and others added 21 commits October 29, 2026 12:59
OBR's table 4.1 is UK-wide, so Chronicle stamps its England, Scotland and
Wales council tax rows K02000001, and the substring rule's nation pins
compiled no fact. The rows now pin to the UK, as obr.council_tax and
obr.domestic_rates do; each binding still scopes the model column to its
nation. obr.council_tax binds their sum, so measure exclusions hold the three
as diagnostics, measured on every evaluation as evidence for CT-C (María's
ruling of 2026-10-29, microcosm#1095 D14e). The references and membership
regenerate with the PR's shared regeneration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 R8 and R9: a wrong geography pin reads as "no fact", and the
generator's inference (one-by-one pins, prefix pins, then the substring rule)
silently overrode any geography a target's selector declared, because the
authoring merged the pin over the selector. María ruled on 2026-10-29 that a
declared geography wins. The UK generator now returns a selector's declared
geography_id first and refuses a one-by-one pin that disagrees with it, and
the shared authoring refuses a pin that differs from a declared selector key
instead of overwriting it. No committed selector declares a geography yet, so
no reference changes; the devolved SLC rows are the first to use it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 R4. slc.repayments.devolved_total took one fact per devolved
nation, but the "slc." rule pinned it to Great Britain, where no fact sits, so
it never compiled. It becomes slc.repayments.wales_total, .scotland_total and
.northern_ireland_total, each declaring its nation's geography in its selector
(the R8 rule), measuring the frame's own year (measurement_period 2024)
against SLC's 2024-25 outturn, and filtering the model to its nation. The
incumbent registry's three per-nation metrics now map one to one.

María ruled on 2026-10-29: bind Wales, and hold Scotland and Northern Ireland
until their borrowers' plan thresholds are modelled (plan_4_imputation is
False; policyengine-uk#2636 closed as not planned). Measure exclusions hold
the two. The matched-period hold for the three rows waits for her signature,
so the membership assertion in test_uk_target_references fails until the
shared regeneration, which needs that hold.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follows the split of slc.repayments.devolved_total (microcosm#1095 R4): the
contract has 453 targets, the registry scope 393, and the incumbent's three
devolved metrics map one to one, so 185 mapped targets. geography_id joins
the national selector vocabulary, as the R8 rule lets a selector declare its
fact's geography.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 R7: Scottish Child Payment spending, HMRC's Tax-Free Childcare
top-up, Northern Ireland's Translink bus passenger receipts and SLC's four
England repayment rows took their 2025-26 fact alone, outside María's rule of
2026-09-22 that fiscal-year facts take only the months to the end of the
calibration calendar year. She extended the rule to them on 2026-10-29, so
each declares calendar_year_window: three twelfths of 2024-25 and nine of
2025-26. The pinned feed has both years for all seven (Scottish Child Payment
has 2026-27 too). No hold or measurement period names them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 D5: a target is measured at the model's period, but some
publications observe a period with another label. DfE's January census for
model year Y is January Y + 1, the spring term of the year's entitlements, so
the rows could only bind the census a year out: every selection path refused
a fact after the target period.

LedgerTargetReference gains observation_period. Fact eligibility, the
latest-not-after choice, the exact-period match and the resolved-fact guard
read it in place of the target period; the TargetSpec keeps the target period,
and its metadata records ledger_observation_period. Operations that compose or
pin periods themselves (the calendar-year windows and average, latest_plateau,
the two ratio translations) and the monthly windows refuse it, as does an
unparseable period. The authoring passes a target's observation_period into
its reference rows and checks eligibility at it. Nothing declares one yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 D5. The eight dfe.funded_childcare rows bound the January 2025
census, but model year 2025's entitlement year runs from April 2025 to March
2026: its spring term starts on 1 January 2026, and the spring-term measures
count children by their age on 31 December 2025, the basis DfE's January 2026
census uses. The January 2025 census was a year out, held as an in-year
snapshot. María ruled on 2026-10-29 to bind January 2026.

Each row declares observation_period 2026-01, so its fact is selected there
(the universal-only difference's two operands too) while the target stays at
2025. A fact after the target period carries no uprating hold, so the three
in_year_snapshot holds retire. The reference and membership assertions wait
for the shared regeneration; the childcare take-up refit follows on the arm's
spine.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 D14f needs OBR's council tax receipts restated for the main
residences households hold: England's chargeable dwellings less its second
homes and empty dwellings, over the chargeable dwellings. No published cell
is that remainder, and a window-ratio operand can only sum cells.

A calendar_year_window_scaled_by_ratio numerator may now declare complement:
true. Its cells are taken off the denominator before the quotient, which
keeps the (0, 1] subset-share check. complement is operand metadata, never a
selector field; only a numerator may declare it, and only as true. The spec
records ledger_value_numerator_rule, and the formula reads
"(denominator - numerator) / denominator".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 D14f. obr.council_tax bound OBR's Great Britain receipts,
which include council tax on second homes and empty dwellings. Households do
pay it on property they own, but the frame's council_tax is each household's
main-residence bill only and the engine has no input for council tax on
other property, so the solve met the whole line by pushing main-residence
bills up. María ruled on 2026-10-29 to bind the main-residence share.

The row now scales its calendar-2025 window by England's chargeable dwellings
less its second homes and empty dwellings, over its chargeable dwellings
(MHCLG Council Taxbase, October 2025), through the window ratio's new
complement numerator. A private compile of the row against the pinned feed
resolves the window and the three taxbase cells once each. The count-based
share and England standing for Scotland and Wales are stated in the notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095, María's rulings of 2026-10-29:
- D3: ons.population.scotland_households_3plus_children stays signed out,
  but its reason was wrong: a fact exists, Chronicle's Scotland cut, and it
  counts couple households only, so binding it would fix part of the group
  and leave lone parents free. The register entry takes the corrected reason
  (couples_only_composition_fact), her approval of 2026-10-29 and an
  adjudication line; it tracks #1095, as #736 closed.
- D18a: ONS's small-area income rows (BHC and AHC means, housing costs) were
  deferred "pending the signed mean-aggregation design". ONS models them
  from the FRS, so binding them would partly fit the FRS to itself: they are
  kept out as circular (frs_model_based_circularity).
- D18c: Northern Ireland's UC area cells stay out; the reason now records
  that DfC publishes claimants, counting a joint claim twice (uk-data#590).

The membership and local surfaces carry the new texts at the shared
regeneration; test_uk_target_references pins the D3 text to the new reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095's "stale register and gate text" items that need no signature:
- weight_year's docstring quoted 0.72% growth from 2024 to 2025, the figure
  before policyengine-uk 2.155.0's population; it now points at the pinned
  dataset_projection block, which every lock re-pins.
- The certifier and the calibration run said local-candidate gates stay out
  of national certification "until microcosm#146"; #146 closed when the local
  variant shipped, so they now say the local line certifies them.
- was_wealth's bedrooms note pointed at the closed #145; the question is
  #1095's "num_bedrooms as a WAS predictor" (uk-data#463).
- dwp.uc.households_lcwra_element's note quoted a September baseline and an
  open #882 question; it now records pe-uk#1989's proxy and María's NS6
  ruling of 2026-10-29 to keep it.
- obr.universal_credit's note said both "UK incl. Northern Ireland" and
  "Scoped to Great Britain" (CF1); it now says Great Britain.
- obr.sdlt's note called pe-uk#2322 unreleased; it has been in the lock since
  #1400, and the note now states how its projection compares with the row's.

Signed register text (the JSA and ORR reasons, tracking fields of closed
issues) waits for the renewals PR, so each entry is re-signed once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#721 (tracked in #1095): a stage can declare rewrites, columns an
earlier stage produced that it replaces, but StageRecord kept only the
declared outputs, so provenance credited a rewritten column to its first
producer, and the UK spine's final nonzero-share list kept a hard-coded
FRS_EDUCATION_GRANT_REWRITES carve-out (redundant, as frs_spine already
produces education_grants).

StageRecord gains rewrote, the stage's declared rewrites, and its
nonzero_share covers them as they stand after the stage. A rewrite absent
after the stage is refused, like a missing output. The spine manifest's
stage_records carry rewrote, and the final list reads every record's
outputs and rewrites, so the carve-out and its import go. #721 can close
once this lands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 (from #796): the support-floor loop deferred E06000053 and
E09000001 for every local-authority target outside the bound families,
including the nine Welsh and eight Scottish families whose area_scope holds
no English authority, so their membership listed deferrals for cells they
never have. The loop now reads each target's local_authority gss_prefixes,
keeps only the areas in scope, and skips a target with none. Thirty-two
targets take the deferral (59 area entries, E06000053 in 27 and E09000001 in
32), down from 49 (93; 44 and 49). The local references and membership
regenerate with the shared regeneration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 items from #688, #796 and #757.

- uk_zero_weight_strata: the two strata kept June's caps of 100,000 each,
  10,000 SPI-synthetic households times ten output-area clones, a grain the
  national seam no longer builds. Its calibrated control of 2026-10-28
  (4374e0bf) holds 78,093 households and no zero-weight row in any of the
  four SPI-synthetic and capital-gains-clone strata, because the SPI stage
  gives the stacked donors their prior mass before calibration. Both strata
  are re-declared at a cap of 0 under current names; they keep their
  selectors so that a zero-weight row there is named by stratum.
- uk_export_surface: the reviewed exclusion for
  person.incapacity_benefit_reported never matched. The pinned reference
  (efrs_parity_reference.json) lists the all-zero column among its zero-share
  inputs, not on its export surface, so the gate reported the exclusion as
  unused. The release boundary still drops the column, and the shared check
  refuses it as an unlisted extra, so the guard holds without it.
- macro_realism: María ruled on 2026-10-29 to drop it and record why. The
  plan declared it not_applicable, but the release contract's verifier
  refuses an excused entry in this spec vintage (test_gate_battery_contract_
  pins holds every UK entry to not_applicable None). So the battery's policy
  text records the reason: the solve binds the household income components
  directly, and the national accounts' household disposable income differs
  in scope (imputed rent and, in the headline series, non-profit
  institutions serving households).

The battery, part and dense digests in microcosm-data's contract move with
the manifest, as in a094f5d. The take-up stage-time checks (her ruling of
2026-10-29) follow in their own commit. The Carer's Allowance stage-health
gate waits on her: the take-up contract records her 2026-10-20 ruling of no
such gate until a caseload target binds the rate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
d2a1f9c gave StageRecord its rewrote field and read the spine's final
nonzero-share list from every record's outputs and rewrites, but only the
legacy plan path filled it. The graph build, the production path, projects
its records from node artifacts and left rewrote empty, so its records
dropped the rewrite provenance microcosm#721 asks for, and
test_driver_writes_spine_h5_sidecars_and_logbook lost education_grants from
the final list (the real roster still lists it through frs_spine's outputs).

A declared rewrite is an owned cell of its node, as an output is, so the
graph projection now reads its share from the node's artifact and records
the stage's declared rewrites.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
María's ruling of 2026-10-29 on microcosm#1095 ("do both"): keep the
terminal uk_take_up_signal gate release-blocking on the calibrated shares,
and check the same flags at stage time.

- The twelve flags the terminal gate measures are drawn by three stages
  before the assembled boundary: frs_take_up (the four childcare flags, the
  UC childcare element and the under-2 usage), frs_person_draws (Marriage
  Allowance, Scottish Child Payment) and frs_household_draws (TV ownership,
  licence evasion, the first-home and purchase flags).
  take_up_signal_outputs selects each stage's flags, and a test holds the
  three sets to a partition of the terminal gate's.
- The terminal gate's per-flag measurement moves into
  _measure_take_up_signal, unchanged, so that uk_take_up_signal_receipt
  measures the same thing at the stage's weights. The receipt is
  aggregate-only: support is a band of distinct source households, and a
  share or target resting on fewer than ten is withheld.
- Each stage records the receipt in its checkpoint evidence, and the graph
  hashes frs_take_up and receipt_counts with the two draw stages.
- stage_health gains a take_up_signal check: the receipt must carry
  exactly the declared outputs; each must vary, sit within the declared
  bound of its target, and keep the universal hours nested; a withheld
  share fails, as it cannot be measured.
- gates.json declares uk_stage_frs_take_up_signal,
  uk_stage_frs_person_draws_take_up_signal and
  uk_stage_frs_household_draws_take_up_signal (assembled, release-blocking,
  evidence_absent_blocks, population_fact_check) at the terminal gate's
  bounds, 0.05 and 0.10 for the under-2 usage, until a spine build's
  receipt measures the stage-time deviations. The spine scope, the data
  contract's entry, evidence and spine-part mirrors and the battery, spine
  and release-cut digests follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#823 (tracked in #1095). The registry kept the UK 2024-25 national
line off the default variant until its first certified cut existed on the
Hub, so that resolve("uk") never chased an absent pointer; its comment named
the flip a one-line follow-up after promotion (review of #966, Max's #823
ruling). Checked on 2026-10-29: latest-national.json on
policyengine/populace-uk-private names
microcosm-uk-2024-25-national-20261025T091414Z-a6299504 (updated
2026-10-26), with its release certification, built on policyengine-uk
2.151.0, the version #1095 names for the flip.

The entry's variant becomes DEFAULT_VARIANT, so resolve("uk") and
load("uk", 2025) follow latest-national.json, and load("uk", 2023) stays on
latest.json. This changes the default UK load for every consumer of
microcosm.data; no other local repository names the retired national
variant. The registry, loader and assembler tests and the release runbook
follow; the live pointer test now branches on the line pointer, not the
variant, and resolves the promoted cut.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two items from microcosm#1095's stale-text list, both without a signature:

- The three vendored bus resources said that the LCFS and ETB bus-fare and
  bus-support rakes consumed them. microcosm#930 and María's ruling of
  2026-09-23 replaced those rakes with the bus fare and bus support pricing.
  The purposes in the selection register and in the vendored files now name
  the pricing, and dft_bus_value_anchors.json lists bus_support_pricing,
  which reads its net support, among its consumers.
- The Incapacity Benefit SPI leaf (FRS benefit code 17) was "a structural
  zero in the audited 2023-24 FRS". A private check of the FRS 2024-25
  benefits table found no code-17 row, so the note now names both vintages.
  The text is in sources.yaml, its source_stages.json projection and the
  contract's expected string.

Both move stage contract digests, of frs_hmrc_spine_leaves, lcfs_consumption
and etb_services. So tools/graph_uk_spine_fixture.py regenerated the
charter-H2 fixture (only those three digests and the leaf note change), and
the release input coverage manifest takes the new source manifest digest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8e3394b gave LedgerTargetReference an observation_period field. The
monetary binding serialises the reference with asdict, so every activated
and source reference receipt now carries the key (None unless declared), and
microcosm-calibrate's integrity check refused it as an unknown key: the full
engine-free run failed test_monetary_targets' two binding tests. The
verifier's reference keys gain observation_period, as #834 added the operand
keys, and the calibrate fixture's hand-built receipt carries it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fff37ea held the three OBR council tax nation rows (ruling D14e) and
ae1edf7 held SLC's Scottish and Northern Irish repayment rows (ruling R4),
which takes the packaged calibration measure exclusions from 40 to 45 and
the census's slc. marker from 3 to 5. test_uk_measure_simulation still
said 40 and 3; the full engine-free run caught it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
microcosm#1095 R4. ae1edf7 split SLC's devolved repayments into one row
per nation; each resolves SLC's 2024-25 outturn, the latest each nation
publishes, at the 2025 target period and measures the frame's own year
(measurement_period 2024). The compile needs a signed matched_period hold
for that, and test_every_committed_hold_is_signed refuses a proposed one,
so the hold waited for María's signature. She signed it on 2026-10-29
(approved_by juaristi22, expires 2027-01-29). The shared regeneration can
now compile the three rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
María's ruling of 2026-10-29 on microcosm#1095 (A1): "move everything to 3".
CD171's absolute floor is three; the build used ten, CD171's working
minimum against secondary disclosure across outputs. Her ~/.claude/CLAUDE.md
now sets three for what people read too.

- receipt_counts gains UK_DISCLOSURE_FLOOR (3), UK_WITHHELD ("<3") and
  UK_BELOW_TEN_BAND ("3-9"). small_cell_share withholds one or two records;
  support_band and extreme_count print "<3" and "3-9" below ten;
  rounded_count prints three to nine exactly.
- Every stage receipt that withheld on fewer than ten sources now withholds
  on fewer than three, through the shared names: annual income, the
  apprentice draw, Carer's Allowance, the Move to UC and UC take-up draws,
  pension coherence, property purchases, the SPI band mean, the NTS fare
  mix, the gambling fits, the high-value home gates and the single years of
  age (diagnostics.UK_DIAGNOSTIC_MIN_SOURCE_HOUSEHOLDS). stage_health reads
  the new label and bands, and its detail key becomes
  regions_rewritten_under_floor.
- Tools: the private-rent receipt (its output key becomes
  cells_under_floor_source_households), the childcare realised take-up
  report and, through the diagnostics constant, the council tax liability
  comparison.
- Kept on purpose: the zero-support floor (1); local_small_cell_rule.json,
  whose three signed rules defer published cells too small to fit, not
  survey cells, so they need no re-signing; the private-rent tool's
  ten-row group rule (no summary describes one district); and the SPI
  coherence tool's cell floor for correlations, medians and quantiles,
  since a median of a few records is one record's own value.
- Six gate notes and four stage notes state the new floor; the battery and
  spine-part digests, the coverage manifest's source digest and the
  charter-H2 fixture's data bundle follow (its graph is unchanged).
- About 86 test expectations across 21 files: a withholding test keeps its
  purpose on one or two sources and expects "<3"; an incidental "<10" now
  reads the exact figure, "<3" or "3-9".

1,270 tests across the touched files, the gate and contract pins and the
coverage manifest pass; the charter-H2 parity test passes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vahid-ahmadi

Copy link
Copy Markdown
Contributor

@juaristi22 this is an early look at 5a944e449, not a full review, since the body says it isn't ready. It covers must and should items only, and nothing on your own pending list. I'll do a full pass after main merges in and the references regenerate.

  1. must: an engine-uk failure the body doesn't list. tests/engine/uk/test_uk_graph.py:84 still asserts set(nonzero_share) == set(stage.outputs). But _graph_stage_records now adds stage.rewrites to shares (Carry manifest rewrites into the shared Stage/StageRecord producer graph #721). So age_tail fails in engine-uk on both Pythons (run 40917095981, at this head). Regenerating won't fix it. The assertion needs set(stage.outputs) | set(stage.rewrites). The body's engine-tier line covers only the charter-H2 parity test, so this one was missed.
  2. should: rounded_count now prints exact counts from three to nine (receipt_counts.py:103). The module docstring still says "no exact count that ... narrows a small group by difference". extreme_count and support_band print "3-9" there instead. Printing exact counts just above the floor is where differencing bites. That matters more now that the floor is three rather than ten, CD171's working minimum against secondary disclosure across outputs, as the docstring says. I'd keep "3-9" in rounded_count too. I'm not reopening the ruling. Please link the UK: every open data item: uk-data parity, engine locks, the local surface, consumption and high-value homes #1095 comment that records it from the module and the changelog, and say there that the SN 9422 conditions (HMRC sees SPI-based material ten working days ahead) are unchanged.
  3. should: UK #1095 A/B fixes: the SPI age band (uk-data#628), households' HRAD from Table 8a receipts, and the SPI pay floor (uk-data#629) #1426 adds new "<10" sites. The SPI pay-floor receipt in UK #1095 A/B fixes: the SPI age band (uk-data#628), households' HRAD from Table 8a receipts, and the SPI pay floor (uk-data#629) #1426 hardcodes ten in several places. Whichever of the two lands second should move them onto UK_DISCLOSURE_FLOOR. Otherwise one receipt stays on the old floor without anyone noticing. I've raised it on UK #1095 A/B fixes: the SPI age band (uk-data#628), households' HRAD from Table 8a receipts, and the SPI pay floor (uk-data#629) #1426 too.
  4. should: ship the Promotion for the constant-id national line: pointer and certified-loader extension #823 default-load flip on its own. Pointing load("uk") at latest-national.json and retiring variant="national" affects every consumer. It doesn't depend on Budget 2026 slower data fixes, PR C of #1418: electricity at the ONS level, pension income by area #1420, Budget 2026 ISA data, PR B of #1418: ISA subscriptions per adult, the Lifetime ISA anchor, additive ISA income, policyengine-uk 2.164.2 #1421 or the regeneration. As its own small PR it could land now, and it wouldn't be held behind this one. The old 823-national-variant-until-promoted.changed.md entry, which describes the opposite state, should go in the same change.

The D14f main-residence share (0.968) is covered on #1423: #1423 (comment).

What I ran. I read the diff at 5a944e449 against its base fddbc7073 and the failing CI logs. I didn't run anything locally. I didn't review the target, gate or ledger changes in detail, and I'll leave those for the full pass.

🤖 Generated with Claude Code

juaristi22 and others added 3 commits October 30, 2026 15:44
Main now carries #1420 (electricity at the ONS level, pension income by
area, Rural Fuel Duty Relief areas, the balanced Carer's Allowance draw)
and #1421 (policyengine-uk 2.164.2, ISA subscriptions, the Lifetime ISA
anchor, the additive ISA contract), with the feed at Chronicle 53815b2.

Hand-merged:
- uprating_holds.json: main's holds, re-pointed to microcosm#1095, less
  the three DfE in_year_snapshot holds this branch retires (D5), plus the
  signed SLC nation hold (R4) and main's ONS electricity hold.
- gates.json: the export surface keeps main's tax_free_savings_income
  exclusion (microcosm#1360) and drops the all-zero incapacity benefit
  layer as this branch does; its notes name both.
- sources.yaml: main's Carer's Allowance stage note, with its receipt
  floor restated at three source households.
- weight_year.py keeps the docstring that names no lock's growth figure.
- calibration_run.py, test_country_spec.py, contract.py and
  test_contract.py list both sides' new gates in gates.json's order.
- The tests take the merged counts: 458 targets (registry 396, profile
  62; mapped 185, unmapped 211), 44 measure exclusions, and 34 support
  floor rows over 61 area entries ({E06000053: 27, E09000001: 34}).
- The Carer's Allowance receipt test takes main's balanced placement at
  the floor of three; two stale comments restate that floor.

Regenerated on the merged tree with policyengine-uk 2.164.2:
source_stages.json, the release input coverage manifest (143 required,
2 reviewed exclusions), the gate battery, spine-part and release-cut
digests, and the charter-H2 fixture. The national and local references,
membership and compile-parity receipts regenerate next, on feed 53815b2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The UK lock moves from 2.164.2, which #1421 brought, to 2.165.1, the
newest release (microcosm#1095, Phase C's first re-bump):

- 2.164.3 (policyengine-uk#2736) counts other investment income in
  market income and in HBAI household net income, before and after the
  reset to zero. The LCFS, NEED and NTS stages band recipients on that
  HBAI income with its deductions added back, so their gross income now
  counts it, as the surveys' gross incomes do.
- 2.164.4 (policyengine-uk#2746) counts it in capital_income too. Its
  changelog says nothing reads capital_income; the WAS stage does, as a
  predictor, and the recipients' figure now matches the donor's
  DVGIINVR8, WAS's gross income from all financial investments.
- 2.165.0 (policyengine-uk#2750) adds the company car and car fuel
  benefits in kind and the Class 1A NICs on them, read from nine person
  inputs. The build writes none, so no one has a company car and both
  benefits are zero, as before. The inputs are signed at their default
  in UK_ENGINE_DEFAULT_INPUTS for María's signature; the company car PR
  for the Autumn Budget dashboard's #316 supplies six of them.
- 2.165.1 (policyengine-uk#2754) lets a family that would claim UC keep
  Tax-Free Childcare instead when the top-up is worth more than the
  award (forgoes_universal_credit_for_tax_free_childcare), and takes no
  debt deductions from an award only a reform creates. Every new
  variable is a formula.

Two lockstep tests follow the engine: Tax-Free Childcare's top-up is
one helper from 2.165.1, which reads the spend the build routes; and the
person-level GBP stocks gain the company car's list price and the
capital contributions towards it, which are no one's capital.

No economic assumption moves: the vendored uprating pins and the
bonus-sacrifice anchor change only their version stamps, and no gate
digest moves. The three pyproject floors, uv.lock (policyengine-uk
alone), the approved lock digest, the engine-core pin test, the
concept coverage report, the version mentions in code, notes and
tests, source_stages.json, the coverage manifest and the charter-H2
fixture follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
610a1bc records a stage's declared rewrites beside its outputs in the
graph build's stage records, as d2a1f9c does in the plan build
(microcosm#721). The engine-lane test of the record projection still
expected the outputs alone, so it failed on age_tail, which rewrites
age. It now expects both, and the record's rewrote field.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
juaristi22 and others added 2 commits October 30, 2026 17:40
R7 puts dfi_ni.bus.passenger_receipts on the calendar-2025 window. Its
selector pins two services (Ulsterbus, and Metro and Glider), so each
year carries two facts of one measure. The window counted series only
from list-valued source concepts, measures and tables, so it read the
two services as an ambiguous selector, and the row fell out of the
references on the regeneration (a signed-deferral compile error).

A dimension the selector pins to several values now names one series per
value, as a list-valued source key does: the window of the sum is the
sum of the windowed series, and a service short of a year refuses the
whole window. A member's label in the window's metadata names the
pinned dimension's value, so the two services stay apart. No other UK,
US or NZ window reference pins several dimension values.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The one regeneration this PR owed after merging main: the national and
local references, membership and compile-parity receipts on main's feed
pin, Chronicle 53815b2 (#1420's re-pin), with policyengine-uk 2.165.1.
The vendored resources check against the full artifact unchanged, and
the local census, the local references, the local parity receipt and
the coverage manifest regenerate unchanged.

National surface (1,439 candidates, 396 contract targets):
- 1,409 active references, up from 1,403, and no row without a fact (4
  before): the three OBR council tax nation rows pinned to the UK (D14e,
  held as measured diagnostics) and SLC's three nation rows (R4; Wales
  binds, Scotland and Northern Ireland are held).
- The eight DfE rows select the January 2026 census (observation_period
  2026-01) at model year 2025, with no uprating (D5).
- Scottish Child Payment, the Tax-Free Childcare top-up, Northern
  Ireland's bus receipts and SLC's four England repayment rows take the
  calendar-2025 window (R7).
- obr.council_tax binds the main-residence share of OBR's receipts
  (D14f).
- The national compile-parity receipt: 1,409 compiled, 1,417
  differences (calibration drift 561, fixture only 42, ledger only 814).
  The incumbent's three devolved SLC metrics now match the nation rows
  exactly.

Local surface: 27,168 active references, every status count unchanged.
The membership's signed deferrals fall from 94 to 77: a target scoped to
Wales or Scotland no longer defers the two English micro-authorities
(microcosm#796, via #1095). The MSOA income deferral carries D18a's
signed reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@juaristi22 juaristi22 changed the title UK: take up #1095's actionable items on the current policyengine-uk (draft, waits for #1420 and #1421) UK: take up #1095's actionable items on policyengine-uk 2.165.1 (draft) Oct 30, 2026
@juaristi22
juaristi22 marked this pull request as ready for review October 30, 2026 18:25
@vahid-ahmadi

Copy link
Copy Markdown
Contributor

@juaristi22 review of b46be0044, round 2. The title and body still say draft, but GitHub shows the PR as ready for review. Worth marking it draft, or dropping "(draft)" from the title, so the two agree.

Earlier findings (round 1, at 5a944e449)

  1. must, engine-uk graph records test: fixed. e40eabd1b expects outputs and rewrites (tests/engine/uk/test_uk_graph.py:84-89) and checks rewrote. engine-uk passes on both Pythons.
  2. should, rounded_count exact from three to nine: still open. receipt_counts.py:102-103 still returns the exact count, and the module docstring (receipt_counts.py:5-7) still rules out an exact count that narrows a small group by difference. The changelog now says it plainly, which helps. It still doesn't link the UK: every open data item: uk-data parity, engine locks, the local surface, consumption and high-value homes #1095 comment that records the ruling.
  3. should, UK #1095 A/B fixes: the SPI age band (uk-data#628), households' HRAD from Table 8a receipts, and the SPI pay floor (uk-data#629) #1426's hardcoded "<10": still open. UK #1095 A/B fixes: the SPI age band (uk-data#628), households' HRAD from Table 8a receipts, and the SPI pay floor (uk-data#629) #1426 hasn't moved (457af0274, e.g. spi_income.py:936 < 10, and its tests assert "<10"). The body's Overlaps paragraph names only the shared generated files. One line there would cover it: whichever lands second moves those sites onto UK_DISCLOSURE_FLOOR.
  4. should, the Promotion for the constant-id national line: pointer and certified-loader extension #823 default-load flip: still in this PR. Two older fragments still describe the opposite state, and they would ship in the same release notes as 823-national-line-default-load.changed.md. They are changelog.d/823-national-variant-until-promoted.changed.md and the last sentence of changelog.d/823-uk-2025-registry.changed.md.

D14f's main-residence share: there's no reply on #1423 yet and the PR is unchanged, so that point stays there: #1423 (comment)

New findings

  1. must: engine-free is red on both Pythons, with five failures and two causes. CI shows only one failure because it runs with --maxfail=1. I reproduced all five locally.

    • test_uk_target_references.py:126 still pins ACTIVE_REFERENCE_COUNT = 1403. This is probably the test the body says waited for the regeneration, but b46be0044 didn't update it. The regenerated surface has 1,409, so :345 and :1116 fail. The status counts at :1119 also need no_fact_at_or_before_period gone.
    • The second cause is new. The regeneration puts slc.repayments.england_plan_2 on the calendar-2025 window. The fixture feed tests/fixtures/uk_target_reference_feed_rows.jsonl has its two series (full-time and part-time) only for FY2024, so the compile refuses: "needs the years opening in [2024, 2025] from each of 2 series; found [2024]". That fails test_uk_ledger_targets.py:599 and two tests in test_uk_target_references.py: compile_from_real_staged_feed_rows and constrain_a_frame_with_prepared_columns. With 4962bc3f3's surfaces the fixture test passes. Adding FY2025 rows for both plan 2 series to the fixture should fix all three.
  2. should: the regeneration moves 21 SPI uprating holds that the body doesn't mention. In target_reference_membership.json, the eight self-employment band holds go from 1.11763 to 1.11152 (about -0.55%), and the 13 dividend band holds go from 1.088147 to 1.088151. The new values are right. Budget 2026 ISA data, PR B of #1418: ISA subscriptions per adult, the Lifetime ISA anchor, additive ISA income, policyengine-uk 2.164.2 #1421's 2.164.2 lock refreshed hmrc_uprating_engine_pins.json with the October EFO: per-capita mixed income, 2023 to 2025, falls from 1.0384 to 1.0327. But main's surfaces were last generated before that (ead8943d6), so this regeneration catches them up. The lock's "no economic assumption moves" holds for c5d40e4c8. But the regeneration section lists what moves (DfE, the R7 windows, obr.council_tax) and leaves these out. Please add the 21 holds there, so nobody reads the SPI rows as unchanged.

  3. should: 2.164.3 reaches more stages than the body lists. pe-uk's own test (other_investment_income_in_household_income.yaml) shows household_net_income gains other_investment_income too, not only market, HBAI and capital income. These stages also read the moved incomes:

    • was_wealth reads household_net_income against DVTotinc_bhcR8 (was_wealth.py:64, :350).
    • was_lisa reads it as a predictor and for its tertiles (was_lisa.py:164, :1405).
    • etb_services reads hbai_household_net_income against ETB's disinc (etb_services.py:62, :322), and etb_vat reads etb_disposable_income, which is built from the engine's HBAI income (household_income.py:110-125).

    The body names LCFS, NEED, NTS and WAS's capital_income only. Worth listing these too, and saying whether each donor's income measure already counts this income.

  4. nit: the selector windowing (4962bc3f3) looks correct. Each pinned value partitions by the fact's dimensions, a service short of a year refuses, and a missing service fails len(complete) != expected_series. The regeneration drops expected_member_count: 2 from dfi_ni.bus.passenger_receipts, and the window's series count now carries that check. One test where a service is absent entirely, not just short a year, would pin that.

Interactions. The feed pin is right: chronicle_feed.json and all 57 vendored source_commit values are on 53815b2, the same pin #1420 and #1421 used, with no stale pins. #1430 is stated on both sides: it locks 2.165.0 and this PR locks 2.165.1, the newer lock is kept, and the second PR removes only the six company car inputs its stage writes. test_uk_terminal_gates.py:514 would catch a written input left among UK_ENGINE_DEFAULT_INPUTS. pe-uk 2.164.2 to 2.165.1 changes no economic_assumptions parameter; uprating_indices.yaml gains only the three company car inputs under CPI.

Verdict: not ready to approve. Finding 5 has to go green first. Findings 2 to 4, 6 and 7 are small body or fragment edits. The body still says Phase B follows on this branch, so I'll look again when that lands.

What I ran. A fresh clone at b46be0044 with uv sync --all-packages --locked. These engine-free files: shared/test_ledger_targets.py, shared/test_engine_core_pins.py, uk/test_uk_receipt_counts.py, uk/test_uk_terminal_gates.py, uk/test_uk_chronicle_feed.py, uk/test_uk_ledger_targets.py, uk/test_uk_target_references.py. Only the five failures above failed. I also ran the fixture test against 4962bc3f3's surfaces. I diffed the national and local surfaces against main, and diffed pe-uk 2.164.2...2.165.1. I didn't run the engine tier, a build or the full engine-free suite, and I didn't check the 2.165.1 Tax-Free Childcare claim (fewer than three source households) or the local surface beyond the deferral and status counts. engine-us was still running when I checked.

🤖 Generated with Claude Code

juaristi22 and others added 2 commits October 31, 2026 00:49
… surface

CI's engine-free lane failed on the regenerated surface:

- R4's three SLC nation rows declared the frame's own year
  (measurement_period 2024) under a matched-period hold. The solve
  honours a declared period only at the calibration year, or at the
  frame's year for a value the frame stores, and student_loan_repayment
  is computed by the engine (#1420's period check). So the national
  solve would refuse slc.repayments.wales_total, the one that binds.
  María's ruling of 2026-10-30: carry SLC's 2024-25 outturn to 2025 by
  policyengine-uk's OBR average earnings index, since repayments are a
  share of earnings above the plan thresholds. The three rows drop the
  declared period and declare the index, and their matched-period hold
  retires. Scotland and Northern Ireland stay held out of the solve by
  their own signed exclusions (their plan thresholds are not modelled).
- The fixture subset compile read SLC Plan 2 with 2024-25 alone, so R7's
  window refused it. The four Plan 2 rows (full-time and part-time,
  2024-25 and 2025-26) now come verbatim from the pinned feed, and the
  staged-rows test pins the windowed value.
- The pins follow the regenerated surface: 1,409 active references, no
  row without a fact, and 34 support-floor rows over 61 area entries.

The national references, membership and compile-parity receipt are
regenerated for the three uprated rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Vahid's review of #1422 (its second and third points).

- Since the move to a floor of three, rounded_count printed three to nine
  exactly, while extreme_count and support_band print "3-9" and the
  module's own rule is that no exact count narrows a small group by
  difference. It now reads "3-9" there too. Two tests that read an
  incidental exact count follow.
- The module docstring and the changelog say that the SPI Public Use
  Tape's two conditions (SN 9422) are unchanged by the move to three.
- A guard test fails when a UK runtime module, the UK spec, the gate notes
  or a tool still writes the old "<10" label, so that a receipt left on
  the floor of ten cannot land unnoticed. #1426's SPI pay-floor receipt
  writes it today; whichever of the two lands second moves it onto
  UK_DISCLOSURE_FLOOR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
juaristi22 and others added 2 commits October 31, 2026 01:01
Vahid's review of #1422 (its fourth point): pointing load("uk") at
latest-national.json and retiring the national variant changes the default
load for every consumer and depends on nothing in this PR. It moves to
#1432, which can land now and also removes #966's unreleased changelog
entry that described the opposite state.

This reverts commit 5c7a40d.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erence tests

Two tests in test_uk_target_references.py read the pinned feed, so CI skips
them, and they still expected values from before D5 and R7. On feed 53815b2:

- the DfE rows bind the January 2026 census (D5), so the compiled caseloads
  and the signed-out age-4 cells move to DfE's January 2026 headline figures;
- the Tax-Free Childcare top-up and Northern Ireland's bus receipts take the
  calendar-2025 window (R7), three twelfths of FY2024-25 and nine twelfths of
  FY2025-26, which the test now writes out;
- the extended sum's refusal reads the January 2024 census through the target
  period, as it did before D5, since the row itself now selects January 2026.

Every expected value matches the pinned feed's facts and the committed
membership. The 15 feed-gated test files pass on 53815b2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants