Skip to content

Certify the policyengine.py 6.9.0 replay results - #216

Merged
MaxGhenis merged 1 commit into
mainfrom
uk-replay-results/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1
Oct 22, 2026
Merged

MaxGhenis merged 1 commit into
mainfrom
uk-replay-results/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1

Conversation

@policyengine

@policyengine policyengine Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Certify the policyengine.py 6.9.0 replay results

This PR commits the receiver's sealed qualification of pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1, with its release diff against pe6.5.0_uk2.130.1_policyengine-uk-data-1.58.1. The results workflow (.github/workflows/uk-replay-results.yml) built it from the committed receipt, as #188 and #190 were built by hand. Merging stays on the normal gates: CI and an independent review.

Request 705e2b7aeaaf3f9aa2996e7aeb109fc53c221e5b9f440e8905b02ff70438c0e0 (released_bundle, attempt 1)
Receipt SHA-256 e98830834ccdd9dfe3013edbca58198091965aaa85e1813a39c87ef355c23355, replay-state commit 755ceb7
Run https://github.com/PolicyEngine/policyengine-scorecard/actions/runs/39532413264
Engine policyengine.py 6.9.0, policyengine-uk 2.130.1, core 3.33.0
Data policyengine-uk-data-1.58.1, enhanced_frs_2024_25.h5 (056e80fd…3784)
Integrity complete, 0 failures; complete supported grids for 6 of 6 events, 0 inert measure-years
Diff vs pe6.5.0_uk2.130.1_policyengine-uk-data-1.58.1 construction 0, coverage 0, inertness 0, mapping 0, numerical 0, structural 0, support 0; 0 flagged rows

What changes

  • results/uk/replays/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1/ and results/uk/replays/diffs/pe6.5.0_uk2.130.1_policyengine-uk-data-1.58.1__pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1/: the receiver's requests/705e2b7a…/results/ tree, byte for byte: 231 files, 39.0 MB of aggregate outputs and release-diff packets.
  • docs/uk_replay/requirements/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1.txt: the variant's requirements freeze.
  • data/uk/replay_variants.json: the variant record, the qualification's VARIANT.json exactly plus a note, in canonical form. CI's replay-engine matrix lists the index's certified variants, so it replays this one too; no workflow changes.
  • tests/test_uk_replay_qualify.py and tests/test_uk_replay_determinism.py (NEWEST) and tests/test_uk_replay_variants.py (COMMITTED): the tests that name the newest certified variant move to it.
  • docs/uk_replay/RELEASE_REPLAY.md: a "Committed certified results" paragraph from the receipt's counts.

Validation in the results run

  • The receiver's output guard, applied again to the request's tree: every file an allowed, parsable aggregate.
  • Byte identity: all 231 committed result files have the blob replay-state holds; the receipt and results are unchanged since the receipt commit.
  • uk_replay_qualify verify-sealed: 3 sealed namespace(s) checked.
  • CI's .github/scripts/uk_replay_regenerate.sh leaves the tree unchanged.
  • scorecard_db.build_db: two builds agree (3ebf8a86…), and there is no tracked-file drift.

The table and the RELEASE_REPLAY.md paragraph state counts only. Reviewers add any interpretation of flagged rows.

axiom: n/a: replay results and the variant index; no policy encoding.

Commit the receiver's sealed qualification of
pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1 from replay-state request
705e2b7aeaaf3f9aa2996e7aeb109fc53c221e5b9f440e8905b02ff70438c0e0
(receipt
e98830834ccdd9dfe3013edbca58198091965aaa85e1813a39c87ef355c23355,
receipt commit 755ceb7): its results
and release diff and requirements freeze byte for byte, the variant
record (which adds it to CI's replay-engine matrix), the tests that name
the newest certified variant and a RELEASE_REPLAY.md paragraph from the
receipt's counts.

Replay-Request: 705e2b7aeaaf3f9aa2996e7aeb109fc53c221e5b9f440e8905b02ff70438c0e0
@vercel

vercel Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
policyengine-scorecard Ready Ready Preview Oct 22, 2026 12:35am UTC

Request Review

@MaxGhenis
MaxGhenis merged commit 4a6861d into main Oct 22, 2026
13 checks passed
@MaxGhenis

Copy link
Copy Markdown
Contributor

Merged by squash at head 54c0d004.

  • Review. The Opus 5.5 stack review rebuilt this PR offline for request 705e2b7a on post-stack main and judged it MERGE-SAFE (~/reviews/budget-coordinator/scorecard-results-stack/review-out-opus.md, sim/rebuild206.sh). This bot commit has the same git patch-id --stable as that rebuild (e4610529). GPT-6.1 Sol rated the 6.9.0 results MERGE-SAFE with the stack in.
  • Gates. gh pr checks exits 0, including the new 6.9.0 replay-engine leg. The PR is MERGEABLE, ready, on base main, with no changes requested.
  • 6.9.0 alone. It is on main without 6.6.0–6.8.0: those releases qualified on the same engine pair with 0 flagged rows against 6.5.0, and the builder refuses older releases once a newer one is certified. Certify the policyengine.py 6.7.5 replay results #195 and Certify the policyengine.py 6.8.0 replay results #204 explain this in their close comments.

6.10.0 (Microcosm) has not qualified yet. Both attempts lost the runner at the same AB2025 step. A follow-up measures memory before changing the worker count.

🤖 Generated with Claude Code

This branch was successfully deployed

1 active deployment
Preview — 54c0d004 Deployed Oct 22, 2026 by vercel[bot]
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