Address the certificate wall by one hash#731
Merged
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
1 participant
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.
Certificate packages now name the exact checker-owned Lean wall with one aggregate wall_id instead of carrying 31 audited source copies and per-file hashes.
The wall identity is a domain-separated SHA-256 over sorted, length-framed filenames, exact source bytes, and the pinned Lean toolchain. The verifier resolves only embedded byte-exact walls, authors its own lakefile and witness, and has no filesystem, environment, or network fallback.
Generated packages contain artifact-specific untrusted data only. Checker-owned sources, toolchain, lakefile, and caches supplied by a package are ignored or replaced. Public schema and package format remain version 1.
The refactor centralizes wall ownership and removes 770 net lines. Documentation describes the current package and trust boundary, including the remaining trust-bearing Rust family, semantic-face, policy, and contract selection.
Validation includes wall identity unit tests, the real acceptance-wall kernel build, the goal matrix, the full verifier tripwire suite, and the isolated whole-module guard suite. Direct Lake tests resolve and materialize the exact wall named by each package.