Repository navigation
Pin Belgium's Axiom engine at 753ce7d9 and refresh its input surface - #1643
Merged
Merged
Conversation
Belgium's input surface (be.json) is regenerated at rulespec-be 632e1da1, the bindings' RuleSpec pin, and axiom-rules-engine 753ce7d9, New Zealand's engine pin. The refresh used the NZ hub's 753ce7d9 CLI and dense extension (the engine tree matches the commit file for file; wheel sha256 054c9196...). The same setup regenerates main's nz.json byte for byte. No module's bytes, inputs, status or canonical names move, only rulespec.commit and engine.commit: the five rulespec-be country trees are identical at b105e2b3 and 632e1da1. - axiom_rules_bindings.json pins engine commit 753ce7d9 and the wheel's sha256, as nz/axiom_rules_bindings.json does. The surface is now generated at the RuleSpec pin, so the verification note drops its ancestor check, and verified_on moves to 2026-11-16. The period and views notes cite parse_period_kind and parse_dtype at 753ce7d9. - axiom_input_closure.json records the new surface pins and the mapping's new RuleSpec commit, and engine_optional_evidence is re-cited at 753ce7d9. One sentence changes in substance: at 753ce7d9 a RuleSpec document has an inputs block, which gives no input a default (the engine keeps it only for only_related and selected-year checks and for elections), and none of the 116 surface modules has one. The evidence also says that the first row error fails the whole request. The four engine source pins move to 753ce7d9. - axiom_concept_mappings/be.json takes the surface's RuleSpec commit as its engine_version, as test_axiom_concept_mapping.py requires, and five unmapped reasons now say "at 632e1da1". The concept-coverage golden and doc are regenerated. - The engine-pin test now checks that the pin is the surface's and the closure's engine. Belgium's activation test no longer expects the two pin gaps; a benefit-unit rule and a transport graph remain. The country-spec golden moves by two resource hashes and the fingerprint. - The surface README and the refresh tool's docstring say both snapshots record 753ce7d9, build the extension with --locked, and give Belgium's new RuleSpec commit. Belgium stays inactive. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis
marked this pull request as ready for review
November 16, 2026 15:31
MaxGhenis
added a commit
that referenced
this pull request
Nov 16, 2026
Main brought five first-parent merges since 14797c6: #1640 (UK dense bus floor for 21 families), #1642 (Belgium's ten gate entries in the gate contract), #1643 (Belgium's Axiom engine pinned at 753ce7d9), #1608 (promotions notify collector; emitter-interface floor 0.16.0) and #1614 (LWI's US county facts pin). Main changed nothing under packages/microcosm-fit or packages/microcosm-graph. Two pin files conflicted, both through #1614; each block took main's text plus this branch's own comment lines, placed after main's sentence: - docs/evidence/spec-engine/us-f0-coverage.json: two spec_sha256 blocks, main's side (the branch has no comment there). - packages/microcosm-build/tests/engine_workflow/us/test_us_multispine_pool_tool.py: main's #922 county-facts comment, then the branch's #1543 line, then spec_sha256. No code or test file other than these two pins conflicted, and no other file was changed by both sides. The tools then wrote every value on the merged tree: - tools/repin_us_spec_engine_contracts.py: the multispine pool spec_sha256 9ad067de (tools/generate_us_bundle_from_constants.py --check computes the same digest). It left the branch's EXPECTED_HASHES seed_map d5898b93 and seed_protocol 206be396 and the loader golden b7c843a1 as they were, and main's field-usage and coverage-tool pins as main has them. - tools/spec_engine_coverage.py: us-f0-coverage.json's two spec_sha256 lines (42401/42401 configuration fields; 41/41 inventory checks). - fit.qrf/pins.json keeps the branch's values: the merged fit sources equal the branch's and the kernel's implementation hash reproduces, so tools/graph_parity_repin.py was not run. The repinner's quote style was then reformatted with ruff format. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ready. Round 1 of the Subfleet hard-tier review (20261116-095720-be-axiom-pin-r1) approved 0f628e7 with no findings, so the review has finished. It reproduced the Belgian surface, both concept-coverage outputs and both country-spec goldens, and checked every engine citation at 753ce7d9. The NZ hub OK'd the four shared files below at 0f628e7. Waiting on CI.
Belgium's Axiom input surface moves to the pins its bindings already carry for RuleSpec and to New Zealand's engine pin, and Belgium's bindings now pin that engine. This is the follow-up that #1602's
engine.statusnames.What moves
be.jsonrulespec.commitbe.jsonengine.commitbe/axiom_rules_bindings.jsonengine.commit,wheel_sha256Nothing in the surface changes but the two pins. All 116 modules keep their bytes, inputs, status and canonical names: the five rulespec-be country trees are identical at b105e2b3 and 632e1da1. So PR 4a's closure counts (277 roots: 39 encoded, 238 defaulted) and every default stand.
How it was generated.
tools/refresh_axiom_input_surface.py --country bein dense mode, with the NZ hub's 753ce7d9 CLI and dense extension. The engine directory matches the commit file for file (336 files), and the wheel's sha256 is the onenz/axiom_rules_bindings.jsonpins. Two checks back the setup: the same run with--check --country nzreproduces main'snz.jsonbyte for byte, and the Belgian run's differential found 0 input, status or catalog mismatches between the dense surface and the CLI walk (147 of 156 entity programs dense-compiled; 7 modules dense-unsupported, as before).What follows from it
inputssection; at 753ce7d9 it has one (src/rulespec.rs:664-668). The block still gives no input a default: the engine keeps it only to checkonly_relatedand selected-year reads and to read elections. None of the twelve bound modules, nor any other surface module, has aninputskey. The evidence now also cites where the first row error fails the whole request (src/dense.rs:1539,python-ext/src/lib.rs:404-409), as NZ's does. The fourengine_source_pinsmove to 753ce7d9.period_notecitesparse_period_kind(python-ext/src/lib.rs:985-992) andviews_notecitesparse_dtype(src/formula.rs:1419-1430) at 753ce7d9. Both behave as at 04315d94: a custom period kind keeps its name, and aCountdtype still falls through to Decimal. The RuleSpec verification note no longer needs its ancestor check, since the surface is now generated at the pin;verified_onis 2026-11-16.engine_versionis the RuleSpec commit it was reviewed against, andtest_axiom_concept_mapping.pyrequires it to equal the surface's, so it moves to 632e1da1 (not to the engine commit; NZ's mapping likewise records its surface's RuleSpec commit). Five unmapped reasons say "rulespec-be at 632e1da1"; their claims rest on module text that is identical at both commits. The concept-coverage golden anddocs/concept-coverage/axiom-be.mdare regenerated withtools/refresh_concept_coverage.py.test_the_engine_pin_is_the_engine_that_generated_the_surfacereplaces the test that required null pins: the pin must equal the surface's and the closure's engine commit, and the wheel digest must be a sha256.test_belgium_still_refuses_to_activatedrops the two pin gaps and now asserts noaxiom_rules_bindingsgap; the benefit-unit rule and the transport graph remain gaps, so Belgium stays inactive.axiom_input_closure.json,axiom_rules_bindings.json) and the fingerprint.Shared files
The surface README and the refresh tool's docstring now say both snapshots record 753ce7d9, give Belgium's new RuleSpec commit, and build the extension with
--locked. The note that explained the missing--lockedat 04315d94 is kept as one parenthesis, since no snapshot records that engine now. The NZ hub's record of its 054c9196 wheel namesmaturin build --release --locked. Two shared test files change only for Belgium: a comment intest_axiom_concept_mapping.pyandtest_belgium_still_refuses_to_activateintest_be_target_references.py._separation_violations, which NZ loads by path, is untouched. The NZ hub checked these four files' hunks and blobs at 0f628e7 and OK'd them; its OK covers those files at that head.Verification
At 0f628e7 (on main 9504278), one file per process with
-n 0:test_axiom_concept_mapping.py: 15 passed.test_be_axiom_input_closure.py: 20 passed.test_be_target_references.py: 156 passed, 32 skipped (the Chronicle feed audit;BE_CHRONICLE_ARTIFACTunset).test_transport_holdout_separation.py: 51 passed.test_concept_mapping.py,test_country_spec.pyandtest_refresh_axiom_input_surface.py: all passed.tools/refresh_concept_coverage.py --engine axiom-be --engine axiom-nz --checkandtools/refresh_axiom_input_surface.py --country be --checkat the two pins: up to date.ruff checkandruff format --check(0.15.16, the lockfile's version) pass on the four changed Python files.In a run by the reader that mapped the change (below), with only
be.jsonchanged, three tests failed: the mapping's RuleSpec commit test and two closure tests (the mapping and surface pins, and the engine-source pins). The rest of the change answers them.Two independent readers drafted the re-citations from the 753ce7d9 source, and two more checked each draft, one for the cited lines and one for the substance. Their two corrections are taken: the
RulesDocumentspan is narrowed to theinputsfield, and "can't declare a default" becomes "gives no input a default", since an inertdefaultkey is accepted, not refused. A third reader mapped every file the move touches. No kernel identity or gate-battery binding source hashes these JSON files. The builder source digest (code_identity.py) does change, since it covers all packaged JSON, but it is computed live and has no committed value.No engine was built here, and nothing runs the bindings yet: Belgium has no transport graph (PR 4b).
🤖 Generated with Claude Code