Repository navigation
Add the Autumn Budget 2026 registry and harvest (tranche 1 of #230) - #231
Conversation
…ables 6.1, 6.2 and 6.4 Tranche 1 of #230, following the AB2025 port (#136). - data/uk/ab2026_measures.json: 104 measures. Every Table 6.1 line once, under a key written out per line in pipeline/ab2026_measure_keys.py, plus Table 6.2 line 4 (Sovereign AI) and five packages. The engine pin is policyengine-uk 2.151.0, which the dashboard's Budget-day receipts record. The seven dashboard measures carry pe_modifier with their receipt hashes. Savings rates and the BADR limit are parameter deltas; the bus fare cap is partial. 89 gaps each carry a computed name search at the pin. - pipeline/stage_ab2026_hmt_tables.py stages 762 rows from the two pinned workbooks. Table 6.4 recostings carry the earlier event's key. - The validator accepts executed_by_dashboard and package_of_registry_measures constructions and resolves replaced and read variables against the engine. - pipeline/harvest_counts.py writes and checks COUNTS.json. - The harvest README, the seed inventory and the tests for the registry and the harvest contract. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… its own family pipeline/ab2026_harvest_contract.py holds the row contract the tests applied inline, so a family being staged can be checked before COUNTS.json pins it. Only HM Treasury and OBR quotes run whole (README rule 6). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…re keyed Rule 8 keeps a measure's design (rates, thresholds, payment amounts, dates, durations, allocations, financing remits, contingent liabilities) out of the rows. Rule 9 keys a printed part of one Table 6.1 measure to that measure, marked as a component that is never summed with the total. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… for tranche 2 The contract now also checks that a quote contains the value as printed, that a measure_component row names its part and its measure (rule 9), and that a family's NOTES.md gives the scope of every proposed key its rows name. tests/test_ab2026_harvest_contract.py breaks each rule on an otherwise valid row, and Hypothesis checks the FY-end-year and 15-word quote rules for every input. pipeline/ab2026_proposed_keys.py writes PROPOSED_KEYS.md, the one list tranche 2 registers or folds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Table 6.1 line 2 costs the whole electricity VAT cut from 1 October 2026, so a package of the energy payment, the VAT cut and the fuel duty cut is exactly lines 1 to 3; the old example said otherwise. Rule 2 now names the three kinds of proposed key (a measure with no Table 6.1 line, a package named by its scope, a producer's option), and PROPOSED_KEYS.md shows each key's kind. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Picking up tranche 1 for the Budget coordinator: finishing the red book and IFS reworks, applying the five harvest reviews, and landing the families from Generated by Claude Code |
|
Progress at 13:03Z on 3 November: no families have landed yet, and nothing is unpushed. What happened: after the pick-up comment at 03:09Z I set up (checkouts of Ownership check: the only pushes in the six hours before pick-up were your two staging commits (7a23c33, 7c97f3e), which are the hand-off itself, so I proceeded. Next, in the brief's order: Blocking: nothing. The container and venv survived the restart. Generated by Claude Code |
The 29 October rework cut the first staging's 1,699 rows to 432 under README rules 8 and 9 and stopped before its report. Checking each instruction of its brief against the rows found two loose ends, fixed here: Chart 1.6's six headroom-bridge labels used `component`, which rule 9 reserves for parts of a Table 6.1 measure, so they now name their bar in `chart_bar`; and two manifest notes named local machine paths, which a public repository should not carry. The family passes the contract with 0 problems and its stage.py (kept on uk/ab2026-harvest-staging) reproduces the gzip byte for byte. No primary was re-opened: this session's network policy refused gov.uk, so the 15-row spot check the brief asks for could not run, and NOTES.md says so. COUNTS.json and PROPOSED_KEYS.md are regenerated for the landed family. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
The landed family's edits sit in an explicit block at the end of the embedded data: Chart 1.6's labels move from `component` to `chart_bar`, and two manifest notes lose local machine paths. Keeping the script here means the gzip on uk/ab2026-harvest can be reproduced from GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
…7 rows) The first IFS lane predates README rules 8 and 9. Applying the addendum's sections 3 and 4 drops 19 rows that are design, not estimates (rates, payment amounts, thresholds, government targets, scenario inputs, financing and the DIP funding allocation), and re-keys eight. IFS's three cost-of- living giveaways are exactly Table 6.1 lines 1 to 3 (5,040 against its £5bn), so they take the registered package; the full-period VAT row is line 2; the self-assessment timing and compliance-staff figures match Table 6.3 items, so they are line 45 components; and the two remaining proposals use the names rule 2 gives their scopes. Sections 1 and 2 could not run here. The browser-read pages are listed as pending for the coordinator, and the seven Flourish data items are listed as unreached: this session's network policy refused the Flourish hosts and ifs.org.uk, so no primary was re-opened and no spot check was possible. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
The addendum's rule 8 drops and rule 9 re-keys sit in an explicit block at the end of the embedded rows, so the 87-row gzip on uk/ab2026-harvest can be reproduced from GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
…inktanks-b review applied The review approved all three with fixes, applied here as relabels; no printed value changes. - The Welsh Table 1 cells now say which are parts and which are totals, so an ingest cannot add Resource and Capital to their Total (finding 2). - The Welsh package key names its scope, the Budget's Barnett consequentials, so HM Treasury's figures for the same scope can share it (finding 3). - Real-terms settlement changes get their own metric, devolved_funding_real_terms_change, because AB2025's block_grant_effect means a policy's effect on the grant with the opposite sign (finding 4). - The Scottish Government's five rows join the Welsh ones in uk_devolved_govts (finding 7), leaving uk_fai_sfc empty. - CPS's PuFins figure names no Budget decision, so it is context with no proposed key (finding 1). - Trussell's row moves to a new uk_trussell_wpi family with AB2025's slug (finding 5). The README's slug table gains the three slugs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
uk_devolved_govts' script now writes the Scottish Government's rows too (moved from uk_fai_sfc, whose script now writes an empty family), and uk_trussell_wpi's script is uk_thinktank_misc's, filtered to Trussell's row, so every gzip on uk/ab2026-harvest can be reproduced from GitHub. uk_niesr's NOTES carries the review's corrected exclusion reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
…pplied The review approved all three with fixes; each is applied in an explicit block in the family's stage.py (kept on uk/ab2026-harvest-staging). - TPA's "£93" is the most tax the Pension Tax Allowance removes, the same quantity as its "up to £94" maximum, so rule 8 makes it design: the row goes (306 to 305) and the figure moves into the 53% row's conditions. "About two-fifths" gets its own proposed metric, because the registered revenue_share is a group's share of one measure's yield. - CenTax's £3bn, £0.6bn and £0.4bn are parts of its £4bn and are now tagged as components, so an ingest cannot add them to it. Its timely- payment derivation matches the red book's Table 6.3 cells exactly. The £20 million yield is no longer re-signed, and a 25th-percentile EATR uses the registered average_tax_rate. - IPPR's 0.2pp CPI figure names no scope of its own, so under rule 3 it is context rather than a proposed package, and it is an upper bound. No printed value changes; the families' sites were unreachable from this session, so no primary was re-opened. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
Each script now ends with the review's fixes as an explicit block, so the TPA, CenTax and IPPR gzips on uk/ab2026-harvest can be reproduced from GitHub. TPA's script reads uk_hmt_tables from its sibling directory. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
The review approved the 597 rows with fixes. p.50's UK tax gap is HMRC's whole-economy statistic, not a part of Table 6.1 line 45 nor even the costing's base, so its two rows become context with a null key, as the script's own context path intended. The p.41 British Business Bank costing keeps its proposed key, but its notes now warn that it very probably sits inside a Table 6.1 line and must never be added to one. The line 45 and 47 component notes now say that their notes do not sum to the line. No printed value changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
The review's three fixes sit in an explicit block before build(), so the gzip on uk/ab2026-harvest can be reproduced from GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
… 766 rows) The review approved RF's rows with thirteen mechanical fixes, all applied. The 25 rows for exactly Table 6.1 lines 61 and 62 take the name README rule 2 gives that scope. Restated rows name their sources; two RF statistics are pinned to the averages RF compares them with; six halves' averages carry Figure 8's cash basis; the £358 and 20 per cent rows are England, like the row beside them; and a workbook cell holding a floating- point zero (-7.46e-7 bn, with no bar drawn) is dropped. NOTES loses the passage contradicting README rule 3's corrected example, fixes a hash typo, and records Figure 8's lower rebate bars in v2 and the VAT-element wording as a discrepancy. No printed value changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
The review's fixes are the P_SAV_PROP constant and an explicit block before write(), so the 766-row gzip on uk/ab2026-harvest can be reproduced from GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6HuQUQ1obM9JvyhJbE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6KDzCrvKBEjHk8T31b
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6KDzCrvKBEjHk8T31b
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6KDzCrvKBEjHk8T31b
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6KDzCrvKBEjHk8T31b
…the a9f81e8 reviews GPT-6.1 Sol and a cloud session each requested changes at a9f81e8. Digits with no word of their own now take normalization's factor, failing that 1, where they could match at any of six fixed scales. The checker reports a year after a bare "in", a range whose first number exceeds its second unless neither is positive, and a fraction joined to a percentage. Under rule 4, the checker now marks a bar reading wherever we mention a bar, chart or graph in the locator, or say there that we took a number from a figure. It cancels such a phrase after one negation and not after two, and accepts any dash in a printed place. It also reads a fraction with a direct percentage word, a whole number in words up to the hundreds with a fraction, and a lone dash under a nil note. We change no staged row, and all 5,952 pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The list ran to 42 words, and "one out of every five" already shows "out of". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GPT-6.1 Sol and a cloud session each reviewed 3c65fd7 and requested changes, and this commit answers both. - `_factors` reads each operand whole, multiplies operations in a row, reads a factor in brackets, and returns None for one it can't read, so the checker reports that row at any value (R2). - A whole number with a fraction takes normalization's factor and reads a short multiplier (A3, R4). - The checker reads a dash as zero only under one whole clause that declares it for nil, and it reads the figure dash and the horizontal bar (A4, R3). - Rule 4 reads "Fig." and "Figs.", "on", "in", "using" and "of", plots, diagrams, visuals, a figure's column, readings by eye and "Figure 1(a)". It also counts a second negation anywhere in a clause (A1, A2, R1, R8). - The tests add each case (A5, R7). - The README's contract bullets state what the checker now does (B1 to B4, R5, R6, R9). We change no staged row, and the checker finds 0 problems in the 12 families. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GPT-6.1 Sol and a cloud session each reviewed 8206882 and requested changes, and this commit answers both. - `_factors` returns None for an operation on a bracket, sign, currency sign or number words, and for an operation in words, so the checker reports that row at any value (Sol F1). - `_CONTINUES` reads "hundred" too, so "x 1 hundred" no longer reads as 1 (Sol F1). - Rule 4 looks past a colon, bracket or quote before a figure (Sol F2), reads "fig1a" and "figure1.A" (cloud F4), accepts "Figure 1(a) data label" as a printed place (cloud F6) and ends a clause at a full stop (cloud F14). - The tests add each case, each short multiplier on a whole number with a fraction, and ordinary notes that state no factor (Sol F3). - The README's contract bullets state what the checker now does (cloud F1, F2, F7 to F10; Sol F4). We change no staged row, and the checker finds 0 problems in the 12 families. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LwQq6KnYGrWqigco2AXori
GPT-6.1 Sol and a cloud session each reviewed 4707e91 and requested changes. - The checker's `_UNREAD` now reports an operation in words with any spacing ("multiplied by 1e6", "x by 1e6"), an operation on a wrapped or quoted number word ("x (-one million)"), and an operator with no space before it ("£m×1e6", "£m;x 1e6", "%/100", "£m/100"). It still ignores a slash between digits ("2/3", "2026/27"). - Rule 4 now reads nested wrappers ('read from ("Figure 1.A")'), a word in a bracket or quotes before the figure ("read from [the Figure 1.A]"), and a word that holds an apostrophe or ends a bracket ("HMT's Figure 1.A", "(HMT) Figure 1.A"). A word's first character excludes quotes, so reading time stays flat on a long run of quotes, and a test holds it under two seconds. - New tests fail on 4707e91's checker where it missed these forms, and cover an unread factor on a number that owns a multiplier, a share, a fraction or nil. - The README states the forms the checker reports and tells stagers to write "page 3 of 4" for a slash that divides nothing. No staged row changed, and the checker reports 0 problems on 5,952 rows in 12 families. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GPT-6.1 Sol approved 2f60cdb with four low findings, and a cloud session requested changes with low findings only. - The checker's `_UNREAD` now reports a fraction as an operand ("times half", "/ a quarter", "x 1e6 / half"), a "by" after an operator ("× by 1e6"), "times by 1,000", and an operator right after an arrow ("£m→x 1e6", "£m→/100"). - Rule 4 now reads a word before a figure that ends in closing quotes or several brackets (`read off the "Impact on households" Figure 1.A`, `read from "HMT" Figure 1.A`, "read from ((HMT)) Figure 1.A"). A test holds reading time flat on long runs of quotes and brackets. - New tests cover each form and its negation, and "two and a half" and "half a million" under an unread factor. - The README lists "x half" among the forms the checker reports, says that rule 4 reads the locator, and states that the checker counts "figures" where it means numbers. No staged row changed, and the checker reports 0 problems on 5,952 rows in 12 families. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Merged at
🤖 Generated with Claude Code |
In tranche 1 of #230, we add the Autumn Budget 2026 registry and harvest every producer's figures from primaries we fetch and hash. We model it on the AB2025 port (#136/#137). No code reads the harvest yet; we add the ingest in tranche 2.
Changes
data/uk/ab2026_measures.json, 104 measures), whichpipeline/build_ab2026_registry.pywrites.pipeline/ab2026_measure_keys.pywrites out each line's key, so we keep the key when we reword its title.certified_pairs.jsonrecords only the 6.11.0 / 2.132.6 pair. In Certify the policyengine.py 6.11.1 replay results #242, we certified policyengine.py 6.11.1's replay results with 2.151.0, and we add that pair's record in tranche 3.pe_modifierthe module, the function, the variables it replaces and reads, and its receipt (path, file sha256, reform sha256, run identity).data/uk/bus_fares_gap.json's verdict at 2.89.2 with this one.pre_event_outcomeswhat became of each of the 14 pre-event keys (Autumn Budget 2026 (28 October): scoreability registry so counterparts can be computed on the day #96).uk_hmt_tables(768 rows, whichpipeline/stage_ab2026_hmt_tables.pystages from the two pinned workbooks).revenue_change, and Table 6.1's three totalsdecisions_effect_on_borrowing(README rule 10). It keys each Table 6.4 recosting to the earlier event's measure.financial_transaction_cash_impact, a proposed metric. In line 6, HM Treasury reprioritises financial transactions budgets to fund line 5's scheme, and it sums lines 1 to 9 into the total. HM Treasury lists neither line 6 nor the total in Table 6.1, so the stager gives each a proposed key.executed_by_dashboardandpackage_of_registry_measuresconstructions, and--resolvechecks replaced and read variables against the engine. We build packages withpackage_of, as in AB2025. The validator still accepts AB2025 and the pre-event registry.scorecard_db/signs.pyreads every sign convention on the harvest's borrowing rows. It reads a total of rows under two conventions, or an average of absolute values, as unknown. On revenue rows, it now reads the OBR workbook's legend, RF Figure 10's "reduces borrowing" and IFS's "positive = increase in net tax".signs.pyreads 2,290: 2,538 more rows onrevenue_change, 128 more ondecisions_effect_on_borrowing, and none fewer.signs.pyclassify all 29,894 exported rows from main'sdata/populations.jsonanddata/populations-pmd/identically.pipeline/harvest_counts.pywrites and checksCOUNTS.json.pipeline/ab2026_harvest_contract.pydefines the row contract as one function. The tests call it, and a lane runs it on its own family before pinning that family inCOUNTS.json. It readsvalue_rawonly if the whole string matches one of the forms the README lists, and reports any other string, so we narrowvalue_rawto the number.tests/test_ab2026_harvest_contract.pybreaks each rule on an otherwise valid row. A test runs every number from 0 to 999 in every spelling our number generator produces. Hypothesis checks the period, quote-length, number, ratio, percentage, money-cell, rule 4 and field-type rules, and that changing or deleting fields never makes the checker raise. We tested the checker with 574 mutations of its reader and rule 4, one at a time, and a test failed for each.pipeline/ab2026_proposed_keys.pywritesPROPOSED_KEYS.md: every proposed key we assign to a staged row, with its rows, families and producers. It finds 86 keys (15 measures, 58 packages and 13 options) on 973 rows. In tranche 2, we register or fold each one.reform_hintorconditions, never in rows. We stage HM Treasury's Tables 6.1, 6.2 and 6.4 and the OBR's policy workbook whole. Elsewhere, we treat an amount a scheme will lend or spend as design, and an effect on borrowing, debt or the financing requirement as an estimate;measure_component, and never sum the part with the measure's total;decisions_effect_on_borrowing, sincemodels.pydefines that metric as PSNB and keeps it apart fromrevenue_change, a receipts line. Also give it to the effect's identified parts and splits, and to any figure a producer derives by restating or recombining them. Keeprevenue_changefor receipts totals and tax-change estimates unless their evidence establishes PSNB scope, and for single measures, groups of measures and a total's lines by head unless their producer states the effect on borrowing. Keep a row's metric when a producer restates the row's Table 3.1 group or single measure as an effect on borrowing, and keeprevenue_changefor a total that includes the receipts effect of an option the Government didn't adopt. Give rows on the current budget deficit, or for an outturn the primary deficit, the proposed metricfiscal_balance_change, and name that deficit in their sign convention.Invariants (tested)
key(line). The Table 6.1 rows we stage share that key.COUNTS.jsonequalsharvest_counts.counts(...): rows, primaries, sources, claims sha256, totals.measure_keytakes one of three forms:recosting_ofnames;value_raw.value_rawwhole or reports it: a string that matches none of the README's forms gets a problem at any value. It reads a bracket only if a percentage restates a ratio or worded fraction to the nearest percentage point. It reads a range only if the range runs upward, or neither number is positive, and doesn't join a percentage to a multiplier or a fraction to a percentage. It reports a year from 2010 to 2099 after a bare "in".valuematchesvalue_raw's number within four units in the last place, at the scale the number's own word ornormalizationgives, failing that 1. The checker allows 0.1% rounding for ratios, worded fractions ("1 in 4", "a third") and whole numbers with a fraction ("two and a half"). It allows the same for a fraction of a multiplier or percentage ("half a million", "half per cent"), and none for digits or number words. At any value, it reports the unread operations the README lists innormalization, such as "x (1e6)", "times 1,000" and "£m×1e6".READABLEfails at any value with more around it or a word inside it. It checks that a qualifier, case and spacing change no reading, that a minus flips a reading, and that a multiplier scales only its own number under any normalization.measure_componentrow (rule 9).1eca3182: file sha256, reform sha256 and binding, generated_at, certified model version, dataset revision and sha256, and thepolicyenginewrapper's version.pipeline/build_ab2026_registry.pyregenerates the registry andREGISTRY_KEYS.mdbyte for byte. The test runs where the 2.151.0 venv exists. It passed at 6e06907 with policyengine-core 3.34.5 (comment 6639810412), and we haven't changed the registry or its builder since.decisions_effect_on_borrowingon every row. The Table 6.1 test also checks each row's metric: the borrowing metric on the three totals,revenue_changeon the lines.revenue_changeon those 288 lines and on the receipts total, and the tests require the borrowing metric, or a proposedfiscal_balance_change, on every other row on that key.revenue_changeon receipts totals and tax-change estimates: the OBR workbook's total of receipts measures (6 rows) and IFS's estimate of the Budget's tax change at the forecast horizon (1 row). We also keep it on RF's 11 totals with a continued fuel duty freeze.fiscal_balance_changeon 22 rows (red book 16, OBR 6). In each one's sign convention, we name the deficit its producer measures and not the other: the current budget deficit on 21 rows, and the primary deficit on the red book's primary balance outturn. The test reads that deficit from the producer's label, or for Chart 1.6 from the stability rule, never from the sign, and fails if we swap the two names in any row.signs.pyreads each borrowing row's sign convention as one direction, or declares it unknown.signs.pyreads a convention for both revenue and borrowing, it reads it opposite ways. A Hypothesis property samples the phrasessigns.pyreads as one direction, for either metric, and places them in random filler, with or without a negative leg after them. A second test runs every convention in the feed and the harvests, andsigns.pyreads at least 30 of them for both metrics.signs.pyreads each of the harvest's 76 (metric, convention) pairs, as a reviewer checked them. The test fails on a new phrase, or on an edit that changes a reading, until someone reviews it.Review fixes
The IFS addendum review, at d5e323d
GPT-6.1 Sol reviewed the IFS addendum at d5e323d on Subfleet, re-reading the local primaries, and requested changes in four findings. We answered them in f4c7c94 and 8b7b23d. In a delta review of both commits, GPT-6.1 Sol requested three more changes, and we made them in dfebe9c, which it approved in a second delta review. In these commits, we changed no value, year or sign a producer printed.
ab2026__package_ifs_new_giveaways, at medium confidence. IFS names no source for the 25% and 40% reserve shares in either primary where they appear, so we marked the restated attribution on their four rows as inferred, also at medium confidence. We also corrected two NOTES sentences, on IFS's reference line at 0.9% of GDP and on our failed fetches of the seven data-item pages and the briefing event page IFS names in the addendum.decisions_effect_on_borrowing. It also asked us to give the OBR's current budget deficit memo (6 rows) the proposed metricfiscal_balance_change, and to name that deficit in the sign of the red book's matching memo (6 rows). We did all three, and wrote README rule 10 to put every producer's totals of the Budget's decisions ondecisions_effect_on_borrowing. In that commit, we moved 172 rows to the borrowing metric: OBR 87, HMT tables 18, TPA 40, RF 25 and IFS 2.revenue_change, the receipts linemodels.pykeeps apart from PSNB. IFS doesn't tie its 0.2% of GDP, its own estimate of the Budget's tax change at the forecast horizon, to PSNB, so we returned that row too. We rewrote rule 10 to give the borrowing metric to a producer's stated effect on PSNB, its identified parts and any figure a producer derives by restating or recombining it. We keeprevenue_changeon receipts totals and tax-change estimates unless their evidence establishes PSNB scope. GPT-6.1 Sol also found that we gave the wrong count in the Signs bullet. At 8b7b23d,signs.pyread the conventions of 2,520 more harvest rows onrevenue_changethan f4c7c94's version did, not 2,576. At dfebe9c, it read 2,527 more revenue rows, after we returned the receipts total's 6 rows and IFS's 0.2% torevenue_change. The stagers then moved 165 rows: OBR 81, HMT tables 18, TPA 40, RF 25 and IFS 1.We applied rule 10 past the IFS review's table in three ways:
Reviews A and B, at 4f424b9
On 4 November, two reviewers fetched their families' primaries from the manifest URLs; review A couldn't refetch two superseded HM Treasury copies, since HM Treasury now serves the current versions at those URLs. Review A covered the registry, the HM Treasury families and the harness (comment 6635870934), and review B the OBR, RF and think-tank families (comments 6635496734, 6635498758 and 6635499259). A cloud session applied their findings in 6a1c06f to 15c0773 and listed each finding with its fix in comment 6639062906. It couldn't fetch primaries, so we finished its three open items from the pinned copies: red book rows 194, 365 and 368 (93d2407) and Table 6.4's footnote 2 (3b1abda). We also pinned each receipt's
policyengineversion (6e06907).cash_requirement_change, and Box 3.1's two counts), 2 CenTax rows from a second primary and Table 6.2's total (6 rows). It dropped 7 red book rows: four printings beyond the two the checker allows for one claim, and three figures outside the harvest's scope (its NOTES categories E, F and H).revenue_change. RF builds them by adding the receipts effect of an option the Government didn't adopt, and the OBR states that option's effect on borrowing for 2029-30 only. So the stagers now move 154 rows to the borrowing metric: OBR 81, HMT tables 18, TPA 40, RF 14 and IFS 1. The session also moved eight rows' registered metrics fromproposed_metrictometric(IFS 4, misc 3, Trussell 1) and gave RF rows 88 and 211gross_earnings_change. The balance-row test now selects every row with a proposedfiscal_balance_change: the 17 memo rows, the red book's three Chart 1.6 bridge steps and two Box 1.C outturns.signs.py, pinned the harvest's 76 sign readings in H-5's fixture, and sorted the registry builder's name search (R1), so--checknow regenerates the registry byte for byte.Delta reviews D1 to D3, at 6e06907
GPT-6.1 Sol reviewed 4f424b9..6e06907 and the staging branch in three parts. It requested changes in D1, on the harness (5 findings), approved D2, on the OBR and HM Treasury families, with one fix, and approved D3, on the think-tank families, with three. In D3, it couldn't spot-check every primary, since we hadn't given it local copies of RF's v2 report and workbook, CenTax's PDFs, TPA's primaries or the Welsh and Scottish pages; review B had fetched them all. We answered the three reviews in ac4d14a and f27b927, and on the staging branch in e928465 and 83d5a32.
signs.pydeclares unknown. We count only those it reads as one direction: 2,666.The final review, at f27b927
GPT-6.1 Sol reviewed f27b927 on Subfleet and requested changes in 12 findings. We answered F1 to F4, on the contract checker, in fe58796 without changing a staged row. For F5 to F12, we corrected two counts of
signs.pyreadings, two OBR row references, the Plan's readiness box and our account of fetches and test procedures. We also gave "we" or a program the verbs we had given rows and totals.normalization. It now also checks ten rows where a producer prints a ratio in words: six from CenTax and four from Resolution Foundation.value, or with an integer too large for a float. The checker now reports both, and it also reports a line it can't parse as JSON, a file it can't read and a field with nesting too deep to print.We also rewrote the harvest README in active voice and cut its review history. On f27b927's checker, 37 of fe58796's 123 contract tests fail.
Our own pass, at fe58796
Before the delta review, we probed the checker again and found gaps in two checks, which we closed in 1bf4507 without changing a staged row.
On fe58796's checker, 20 of the 152 contract tests fail. In 72cdfdc, we split a 44-word sentence in the README's rule 4 bullet.
Our own pass, at 72cdfdc
While the delta review of 72cdfdc ran, we widened what the checker reads in 615d6a8. It now reads "1 in 2 million" as 5e-7, "one in every ten" and "3 out of 10" as shares, compound number words in a ratio ("twenty-five", "a hundred and five"), worded fractions ("three-fifths") and number words alone ("four"). Across the 5,952 staged rows, it reads 5,943 as before and compares 9 rows it skipped before, and all 9 pass. On 72cdfdc's checker, 47 of the 208 contract tests fail.
The delta review of 72cdfdc, at 92f364c
GPT-6.1 Sol reviewed 72cdfdc and asked for five changes, which we answer in 92f364c. The checker reads every staged row as 615d6a8's checker did, and finds 0 problems in the 12 families.
ULPS = 64passed every test. A test now builds values withmath.nextafter, for both signs: one to four units pass, and five fail.source_model: []passed.type_problemsnow reports each field of a type the row contract doesn't allow, before any check reads the field, and a new property checks it for every text field,period, each condition and eachpublicationfield. We renamed the old propertytest_changing_or_deleting_fields_never_raisesand gave it Sol's docstring, extended to name the rows it pairs.On 615d6a8's checker, 168 of the 401 contract tests fail, and the tests kill all 41 mutants.
The delta reviews of 92f364c, at a9f81e8
GPT-6.1 Sol and a cloud session each reviewed 92f364c, and both requested changes. The checker scanned
value_rawfor numbers and accepted any matching reading. It passed "1 in .5" at 1, "4 - 5 in 10" at 0.5 and "two and a half" at 0.5. It also passed "half a million" at 0.5, "four million; five thousand" at 5,000,000 and "2 million in 5 years" at 400,000.We replaced the scanner instead of patching it again, since we staged few forms. In
value_raw, we staged digits on 5,900 of the 5,952 rows, a ratio or worded fraction on 31, number words on 7, a range on 6, a bracket on 1 and a rating on 7. The checker now readsvalue_rawonly if the whole string matches a form the README lists, and reports any other string, so no string passes on a number inside it. We removed the token scanner and the year logic, and every staged row passes unchanged. We also ran both checkers on each row at seven values: as staged, ×1,000, /1,000, negated, ×1.01, ×100 and /100. They give the same verdict on all but 6 of the 41,664 cells, where "four" and "one" no longer pass at ×100, ×1,000 or /100, since number words now takenormalization's factor or 1.On 92f364c's checker, 203 of the 518 contract tests fail, and the tests kill all 194 mutants.
The delta reviews of a9f81e8, at 3c65fd7
GPT-6.1 Sol and a cloud session each reviewed a9f81e8, and both requested changes. In 9fd73b1 and 3c65fd7, we tightened how the checker reads a number's scale, ranges and years. We also made it mark a bar reading on any bar, chart or graph in a locator. We changed no staged row, and the checker found 0 problems in the 12 families.
normalization's factor, failing that 1. All 737 staged rows with digits, no word of their own and no factor innormalizationmatch at 1.unit_concept: percentrow, it compares a fraction of a percentage at the same values.normalizationmentions nil, and reports it elsewhere, since a producer may print one for "not available".READABLEto 27 examples.We also ran both checkers on each row at seven values. They agree on all but 2,196 of the 41,664 cells. In each of those, a9f81e8's checker passed one of 732 rows at ×1,000, ×100 or /100, where 3c65fd7's checker reports it. We store 0 in the other 5 of the 737 rows, and every scale leaves it at 0. On a9f81e8's checker, 93 of the 725 contract tests fail, and the tests kill all 303 mutants.
The delta reviews of 3c65fd7, at 8206882
GPT-6.1 Sol and a cloud session each reviewed 3c65fd7, and both requested changes. In 8206882, we made the checker read each factor in
normalizationwhole and require a complete clause declaring a dash for nil. We also widened rule 4 to abbreviated figures and rarer wordings. We changed no staged row, and the checker finds 0 problems in the 12 families.normalization's factor, failing that 1, and it reads a short multiplier ("2 and a half bn").normalizationto declare the dash ("dash for nil", "the table prints nil as a dash"). It also reads the figure dash (U+2012) and the horizontal bar (U+2015).We also ran both checkers on each row at seven values, and they agree on all 41,664 cells. On 3c65fd7's checker, 85 of the 857 contract tests fail, and the tests kill all 434 mutants.
The delta reviews of 8206882, at 4707e91
GPT-6.1 Sol and a cloud session each reviewed 8206882, and both requested changes. In 4707e91, we made the checker report more unsupported factor forms. We also widened rule 4 to punctuation before figures and more figure citations. We changed no staged row, and the checker finds 0 problems in the 12 families.
normalizationas a factor. We stage none of these, and we would reword them.We also ran both checkers on each row at seven values, and they agree on all 41,664 cells. On 8206882's checker, 264 of the 1,169 contract tests fail, and the tests kill all 502 mutants.
The delta reviews of 4707e91, at 2f60cdb
GPT-6.1 Sol and a cloud session each reviewed 4707e91, and both requested changes. In 2f60cdb, we made the checker report operations in more wordings and operators with no space before them. For rule 4, we also made the checker look past nested punctuation, possessives and a bracketed word before a figure. We changed no staged row, and the checker finds 0 problems in the 12 families.
read from ("Figure 1.A"), "read off ([Figure 1.A])", "taken from HMT's Figure 1.A" and "read from (HMT) Figure 1.A". It now marks them, and it still ignores the phrase right after one negation.We also ran both checkers on each row at seven values, and they agree on all 41,664 cells. On 4707e91's checker, 506 of the 1,718 contract tests fail, and the tests kill all 555 mutants.
The delta reviews of 2f60cdb, at 05265c2
GPT-6.1 Sol approved 2f60cdb with four low findings, and a cloud session requested changes with low findings only. In 05265c2, we made the checker report seven more spellings of an operation and fractions as operands. For rule 4, we also made it look past more punctuation before a figure. We changed no staged row, and the checker finds 0 problems in the 12 families.
read off the "Impact on households" Figure 1.A,read from "HMT" Figure 1.Aand "read from ((HMT)) Figure 1.A". It now marks them, and it still ignores the phrase right after one negation.read from ("the Figure 1.A")andread from ( the Figure 1.A, and rows for each new form. We also added "two and a half" and "half a million" under an unread factor.We also ran both checkers on each row at seven values, and they agree on all 41,664 cells. On 2f60cdb's checker, 359 of the 2,103 contract tests fail, and the tests kill all 574 mutants. We then merged
main, with #251, in 4dd5281, so #247 can take #251 and still show only tranche 2.The review of 4dd5281
GPT-6.1 Sol approved 4dd5281 with three low findings, and we merge at this head. The checker reads a numeric mixed fraction as a partial factor, so "4" under "x 2 and a half" passes at 8 (F1), and we test no locator with repeated closing square brackets (F2). We stage neither form, and we answer both in a follow-up PR.
Plan
COUNTS.json. We list each family's rows and primaries insources/harvest-uk-ab2026-2026-10-29/README.md, with the four families that have no rows (uk_cpag,uk_smf,uk_niesranduk_fai_sfc).PROPOSED_KEYS.md, then ingest. Before the ingest, we also:signs.pythe conventions it can't yet read: 14 OBR prose rows onrevenue_changeand 12 rows on other metrics;percentwith a GDP denominator) on the OBR's and TPA'spercent_of_gdp;uk_hmt_tableslines 45 and 46;financial_transaction_cash_impactfor Table 6.2 and give OBR row 2684 the registeredcash_requirement_change;revenue_changefrom the OBR (rows 2190–2195) and on the borrowing metric, under the tax decisions key, where RF restates it (RF rows 385–390);build_ab2025_registry.py, as we did for AB2026 (R1), and decide whether to rename the one-row welfare-savings key (RB-8).🤖 Generated with Claude Code