[policyengine]

Certify the policyengine.py 6.8.0 replay results

This PR commits the receiver's sealed qualification of pe6.8.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	10074ccc871436e5cd332189ab0b5c977cde2333f518aec5497ba875d74ede4e (released_bundle, attempt 1)
Receipt	SHA-256 cc5b19b7705203b8dfc25c08b69783e21e500a3e2d8e58d0bfd940f2dabad6ef, replay-state commit cb37261
Run	https://github.com/PolicyEngine/policyengine-scorecard/actions/runs/39313743241
Engine	policyengine.py 6.8.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.8.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.8.0_uk2.130.1_policyengine-uk-data-1.58.1/: the receiver's requests/10074ccc…/results/ tree, byte for byte: 231 files, 39.0 MB of aggregate outputs and release-diff packets.
• docs/uk_replay/requirements/pe6.8.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.

[vercel]

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

Project	Deployment	Actions	Updated
policyengine-scorecard	Ready	Preview	Oct 19, 2026 11:05pm UTC

[MaxGhenis]

Closing as superseded by the 6.9.0 results PR, which is rebuilt once the fix stack (#199, #196, #201, #202) is on main. Both stack reviews recommend this: Opus 5.5 at ~/reviews/budget-coordinator/scorecard-results-stack/review-out-opus.md and GPT-6.1 Sol at review-out.md in the same folder.

Why it is safe to skip 6.8.0:

• The builder can't append it after 6.9.0. pipeline/uk_replay_results_pr.py:291-296 refuses any release older than latest_certified, which uk_replay_qualify.py:178-180 defines as the last certified record in the append-only index.
• Nothing is lost. On replay-state, 6.6.0, 6.7.1, 6.7.2, 6.7.4, 6.7.5, 6.8.0 and 6.9.0 all qualified complete on the same engine pair (policyengine-uk 2.130.1 with policyengine-uk-data 1.58.1). Each has 0 flagged rows against 6.5.0, and 6.9.0's own diff against 6.5.0 is 0 rows, so it covers the interval. This release's receipt stays on replay-state.
• No reader on the scorecard side (scorecard_db, app) uses the variant index. Committing every release would add byte-identical aggregates and a permanent CI leg each.

Do not re-dispatch this request after 6.9.0 lands: the builder refuses it, and the run goes red.

🤖 Generated with Claude Code