Conversation
Define when derived proof obligations are sufficient evidence for an Anneal claim about Rust behavior, without committing to a particular source model or proof pipeline. Agent-authored-by: AI agent acting on Josh Liebow-Feeser's behalf
Route the design contract to the detailed claim-reduction semantics for Rust-level verification. Agent-authored-by: AI agent acting on Josh Liebow-Feeser's behalf
Connect verification-result evidence to the detailed Rust-level verification reduction model. Agent-authored-by: AI agent acting on Josh Liebow-Feeser's behalf
Remove an evidence-policy aside so the document stays focused on semantic adequacy and claim-relative trust. Agent-authored-by: AI agent acting on Josh Liebow-Feeser's behalf
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## anneal-verification-results #3702 +/- ##
============================================================
Coverage 91.90% 91.90%
============================================================
Files 20 20
Lines 6175 6175
============================================================
Hits 5675 5675
Misses 500 500 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch has not been deployed
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.
Add
anneal/docs/rust-verification.mdas the next detailed design document below the verification-result model.The document models Rust-level verification as an adequate reduction from an exact Rust claim to proof obligations, relative to the result's explicit TCB. This deliberately avoids requiring one canonical source model: source/model correspondence, translation validation, simulations, or other mechanisms are possible realizations of the same requirement.
The model treats weak obligations and unaccounted-for behavior as two manifestations of one adequacy failure, makes coverage semantic rather than syntactic, explains how adequate reductions compose across translation stages, and makes circular UB assumptions visible rather than allowing a successful model theorem to stand in for Rust-level evidence.
anneal/DESIGN.mdandanneal/docs/verification-results.mdgain only routing links to the new document.This PR is stacked on #3701 because the verification-results document it elaborates has not yet merged. Both the conceptual model and the prose articulation were refined using
model-refinementatjoshlf/skills@7aa3d651bc7abfeb7403d6ccfe962fa11cc4b049before publication.Authored by an AI agent acting on Josh Liebow-Feeser's behalf.