Skip to content

Treat the selected record as provenance in 99 replay checks (no new κ) - #5410

Merged
Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
jwr404:provenance-selected-record
Oct 24, 2026
Merged

Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
jwr404:provenance-selected-record

Conversation

@jwr404

@jwr404 jwr404 commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

What changes

99 verify.py files in research packages I authored. No other file changes.

  • The live check selected = json.loads(... certificates/selected-result.json ...) plus kappa == "<old value>" is removed. A one-line comment replaces it.
  • In 4 files the pin loop also hashed usage: "provenance" rows against the working tree. Those files now skip non-input rows, matching the other 95.

Results, RESULT.json, SOURCES.json, VERIFY.json, pins and evidence are all unchanged.

Why

docs/research/research-package-guide.md says the selected record is historical provenance, "so future priority changes do not invalidate a package". Each of these packages already pins certificates/selected-result.json as usage: "provenance", and scripts/research_package.py checks it at base_commit through Git. The verifiers asserted the live κ anyway, so every frontier change broke them. On main 1ec1119:

Re-pinning to the new κ would break again at the next frontier change, so this removes the live dependency instead.

Validation

On this branch (main 1ec1119 + this commit), CPython 3.12:

  • python3.12 -I -B <package>/verify.py: 99/99 pass. All 99 failed before this change.
  • python3 -B scripts/research_package.py --package <package> --check-only: 99/99 PASS_PACKAGE_METADATA_AND_PINS. This includes the base-commit provenance check of the selected record.

CI will replay all 99 packages because they changed. The heaviest is two-three-cycle-additivity, with a 600 s budget. The total declared budget is 8,280 s.

Scope

This is replay maintenance only. No mathematical claim, κ or frontier changes. Other contributors' packages with the same pattern are not touched.

🤖 Generated with Claude Code

Each verify.py asserted the working-tree selected kappa (60403/20000000,
23/10000 or older), and four hashed provenance rows against the working tree.
SOURCES.json already marks certificates/selected-result.json as provenance,
which scripts/research_package.py checks at base_commit, so every frontier
change broke these replays. Results, pins and evidence are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Mister-Meeseeks
Mister-Meeseeks merged commit e36f783 into CrocSwap:main Oct 24, 2026
100 checks passed
Mister-Meeseeks pushed a commit that referenced this pull request Oct 24, 2026
rank7-v45-margin and selected-record-parse-cache were missed by #5410
because their TASK.json author field is "jwr". Both pinned the selected
record (and rank7 the family-status page) as live inputs, so every frontier
change broke them. The pins become provenance, checked at base_commit by
scripts/research_package.py. The parse-cache payload is still the live
record; its one-digit mutation no longer hard-codes the old decimal.
Results are unchanged.

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.

2 participants