Skip to content

Count Belgium's ten gate entries in the gate contract - #1642

Merged
MaxGhenis merged 2 commits into
mainfrom
be/gate-contract-be-count
Nov 16, 2026
Merged

MaxGhenis merged 2 commits into
mainfrom
be/gate-contract-be-count

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Ready. Round 1 of the Subfleet hard-tier review (20261116-091127-be-gate-contract-count-r1) approved 08b8548 with no in-scope finding, so the review has finished. f843a9d takes its one out-of-scope note: the BE incumbent-posture cell read as if external oracles already replace self-parity, and be/gates.json's policy text leaves them to microcosm#264, so the cell now says they are planned there.

The BE column of the "Two postures, one executor" table in docs/gate-battery-contract.md still counted nine entries, eight blocking and one diagnostic. #1602 (e555b4d) added release_input_coverage, so be/gates.json on main declares ten: nine release_blocking and one diagnostic. #1626 made two of them not applicable (calibration_per_family_fit, awaiting d1902, and commune_fiscal_income_fit), which the entries row now says.

I left this row until #1609 landed, since #1609 rewrote the same table (noted in #1626's body).

The incumbent-posture row's first half still holds: the manifest's policy text says Belgium has no incumbent dataset and selects no incumbent-comparison gate. No test reads the table (test_gate_battery_contract_example.py runs its own worked example).

Documentation only; Belgium stays inactive.

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits November 16, 2026 09:10
The BE column of the "Two postures, one executor" table still counted
nine entries, eight blocking and one diagnostic. #1602 added
release_input_coverage, so be/gates.json now declares ten: nine
release-blocking and one diagnostic. #1626 made two of them
(calibration_per_family_fit and commune_fiscal_income_fit) not
applicable, which the entries row now says. The incumbent-posture row
still holds: the manifest's policy text selects no incumbent-comparison
gate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The review of the count fix noted that the BE column's incumbent-posture
cell read as if external oracles already replace self-parity.
be/gates.json's policy text says their implementation (EUROMOD-BE
baselines and Federal Planning Bureau reform scores) remains separate
work in microcosm#264, so the cell now says they are planned there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis force-pushed the be/gate-contract-be-count branch from a7da921 to f843a9d Compare November 16, 2026 14:51
@MaxGhenis
MaxGhenis merged commit d49326f into main Nov 16, 2026
10 checks passed
@MaxGhenis
MaxGhenis deleted the be/gate-contract-be-count branch November 16, 2026 18:32
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>
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.

1 participant