fix(hex-primality): run deterministic verdict tiers before certificate fuel - #9838
Merged
Conversation
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.
Closes #9781
Summary
Public behavior
At explicit fuel zero,
primeCert?can now return a small table certificate or a proved.compositeverdict, andisPrime?can returnfalsefor composites decided by its fixed front end. Inputs that pass the fixed front end and require certificate construction still exhaust without consuming attempts or Rand state.Verification
lake build HexPrimality HexConformancelake build HexPrimality +HexPrimality.Conformance(after second-opinion documentation refinements)Second opinion
Claude Opus found no soundness, termination, or accounting defect and independently reproduced the key low-fuel totals. Its SPEC wording concerns were addressed in f80d47f.