Skip to content

Certify the policyengine.py 6.9.0 replay results - #206

Closed
policyengine[bot] wants to merge 1 commit into
mainfrom
uk-replay-results/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1
Closed

policyengine[bot] wants to merge 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 21, 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.
  • .github/workflows/ci.yml: the replay-engine matrix gains the variant.
  • 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 CI matrix; 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, the CI matrix entry, 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 21, 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 21, 2026 5:36am UTC

Request Review

@MaxGhenis

Copy link
Copy Markdown
Contributor

Closing so the results bot can rebuild this PR on post-stack main (#199, #196, #201 and #202 have all merged; main is at 5a7ae4c5). Both stack reviews recommend this route. The old tip → rebuilt tip change touches workflow files, which the post-#196 bot token can no longer push, so a fresh branch and PR are cleaner than an update.

The rebuild is uk-replay-results.yml for request 705e2b7a… (6.9.0 on policyengine-uk 2.130.1 with uk-data 1.58.1, 0 flagged rows against 6.5.0). #195 and #204 are closed as superseded; their close comments give the reasons.

🤖 Generated with Claude Code

@MaxGhenis MaxGhenis closed this Oct 22, 2026
@MaxGhenis
MaxGhenis deleted the uk-replay-results/pe6.9.0_uk2.130.1_policyengine-uk-data-1.58.1 branch October 22, 2026 00:12
MaxGhenis added a commit that referenced this pull request Oct 30, 2026
#217)

The results bot now runs ci.yml's python-job checks on the assembled tree in
the build job, which holds no write credential. A failing check no longer
stops the run: the pull request opens as a draft that names what failed.
Results PRs #195, #204 and #206 opened ready and failed CI's pytest job.

The test that pins what propose runs now reads each command as bash would and
checks it against an allowlist, in place of a shell-name regex that matched
before quote removal. The stack review's two bypasses are must-flag cases.

GPT-6.1 Sol reviewed this over five rounds; the last, at ed25ea0, returned
MERGE-SAFE WITH NITS. The pull request states the invariants, the known limits
and the review history.

axiom: n/a: CI and test tooling

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

This branch was successfully deployed

1 active deployment
Preview — 4676a32d Deployed Oct 21, 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