Open
Conversation
9904666 to
9360461
Compare
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.
Interface out to a verified solver (cake_lpr)!
This PR is partially an exploration of how to improve trust at the critical connection point from the Lean kernel to proof checkers.
How do we automatically verify (when Lean is compiling) that the CNF we claim to be UNSAT is the same CNF as the one checked by a proof checker?
current answer:
we might actually be able to run Cayden's checker via
native_decidesuch that the only axiom isreduceBool_corrector whatever it is called!for cube&conquer results, this becomes more complicated and I don't know how to give a good trust story.