feat(eval): verify selected Branch closure with receipt v1 - #36
Open
runyuan-wang wants to merge 1 commit into
Open
runyuan-wang wants to merge 1 commit into
runyuan-wang wants to merge 1 commit into
Conversation
9 tasks
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.
Summary
layerfs-eval check <store-db> <branch-id>verify the complete object closure reachable from the selected pinned Branch's effective root.--receipt-v1with a deterministic nine-field canonical receipt emitted only after closure verification succeeds.Compatibility and scope
The receipt describes one pinned Branch/root, not the whole Store. The change does not alter object encoding, schema, wire format, migrations, signatures, export behavior, dependency manifests or lockfiles. Legacy
checksuccess output remains unchanged when--receipt-v1is absent.Design provenance and evidence boundary
This change carries forward the still-valid design discipline from merged PRs #3 and #4:
The three Yuan Conjecture papers informed only the bounded method discipline: work on a finite selected scope, distinguish local verification from global claims, and state nonclaims explicitly:
They do not prove a LayerFS theorem, algorithm, performance result or novelty claim, and no collision/rank model is transferred into this implementation.
Validation
Validated from the current
mainparent with Cargo offline mode:cargo test --offline -p layerfs-content— 103 passed;cargo test --offline -p layerfs-layerstack-store— 47 passed, 1 pre-existing ignored;RUSTFLAGS='--cfg feature="macos-no-mount"' cargo test --offline -p layerfs-eval— 1 passed;cargo fmt --all --check— passed;git diff --check— passed.The plain evaluator build on this macOS host still encounters the repository's existing
fuser/missingfuse.pchost dependency; no dependency file was changed, and the repository's no-mount validation cfg was used for the evaluator test.