Repository navigation
Conversation
… split from a helper Follow-up to release dashboard-data-20261010 (#208), fixing the two non-blocking nits from its round-2 final review. 1. The upgrades table cell built its 14 returned / 4 ruled parenthetical inline in paper/index.qmd. With zero ruled outputs it would print "the 0 ruled on ... stay scored", and with one, "the 1 ... stay". The new restored_split_clause in policybench/paper_results.py, beside restored_split_sentence, builds the whole verb phrase. It handles no fixed outputs, all returned, all ruled, a mix, and singular and plural ("one", "returns", "stays"). The cell calls it through engine_upgrade_restored_split_clause. For this release's (18, 4) it gives the same text the cell printed before. 2. engine_upgrade_restored_sentence called all 18 fixed outputs "restored", though the four ruled on 2026-10-06 while still scored never left scoring. It now says "The fixed outputs take the upstream fixes for ...". The docstrings and the per-entry refusal messages that cover all of them say "fixed" too. The rendered paper changes in two words only: "restored" becomes "fixed" in the paragraph and in the table, in both the HTML and the PDF. No number changes. Re-rendered with paper/render_paper.py and re-pinned with scripts/freeze_snapshot.py --rendered-only. Tests: - A Hypothesis property test over (restored, ruled) for the clause checks the total and its noun, that it says "return" and "stay" exactly when the split sentence does, verb agreement, and no "the 0", "the 1" or lone "1". - The clause is pinned for this release, and the paper must call it. - The fixed sentence is pinned. - Rendered HTML and PDF checks require "fixed outputs take" and refuse "restored outputs take". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Follow-up to release dashboard-data-20261010 (#208, merged as 5a8164a). This fixes the two non-blocking nits from its round-2 final review (
~/reviews/policybench-haiku-5-5/final-review/round2/review.md).Changes
US references on policyengine-us … (October 2026 upgrade)cell inpaper/index.qmdbuilt its parenthetical inline fromr.engine_upgrade_restored_count - r.engine_upgrade_restored_ruled_countandr.engine_upgrade_restored_ruled_count. With zero ruled outputs it would print "the 0 ruled on … stay scored", and with one, "the 1 … stay".restored_split_clause(restored, ruled, ruling_date)inpolicybench/paper_results.py, besiderestored_split_sentence, builds the whole verb phrase. It handles no fixed outputs, all returned, all ruled, a mix, and singular and plural ("one", "returns", "stays", "output", "defect").r.engine_upgrade_restored_split_clause.engine_upgrade_restored_sentencenow reads "The fixed outputs take the upstream fixes for …". The four outputs ruled on 2026-10-06 while still scored never left scoring, so "restored" didn't fit them.EngineUpgrade,partition_engine_upgrade_changes,engine_upgrade_restored_count,_fixes,_fix_phrase,_targetsand_target_sentence.restored/newlyScored/restoredRuledfacts and its "{newlyScored} restored outputs" (the 14 that did return) are already accurate and stay unchanged.Rendered paper: two words, no numbers
I re-rendered with
.venv/bin/python paper/render_paper.pyand re-pinned with.venv/bin/python scripts/freeze_snapshot.py --rendered-only. Word-level diffs of the old and new renders:pdftotext): "restored" becomes "fixed" twice. Nothing else changes.app/src/paperSnapshot.jsonchange only in the pdf andindex.htmlhashes.Invariants (load-bearing prose helper)
For every
0 ≤ ruled ≤ restored,restored_split_clause:restored − ruled > 0, and "stay" and the ruling date iffruled > 0;restored_split_sentenceon both;ruled > restoredandruled < 0.Tests
test_the_split_clause_counts_both_kinds: a Hypothesis property test over (restored ∈ 0..40, ruled ∈ 0..restored) of the invariants above. I also checked the same properties exhaustively over 0..200 by script.test_the_fixed_outputs_split_into_returned_and_still_scoredpins this release's clause. It also requires the cell to callengine_upgrade_restored_split_clauseand refuses the old inline arithmetic.test_the_upgrade_sentences_name_what_the_sidecar_recordspins "The fixed outputs take the upstream fixes for …" and refuses "restored outputs take" in the source.test_rendered_html_calls_the_upgrade_fixes_fixed_not_restoredrequires the clause and the fixed sentence (twice) in the rendered HTML.test_rendered_pdf_calls_the_upgrade_fixes_fixed_not_restoredchecks the PDF.tests/test_paper_results.py,tests/test_disclosures.pyandtests/test_snapshot_artifacts.pygive 202 passed and 1 skipped (pre-existing); the full suite is in the notes below.uv run ruff format .andruff check .are clean.🤖 Generated with Claude Code