Repository navigation
Verify production invariants with Kani and negative controls - #3
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
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.
Changes generated by AI need independently checked evidence for specific invariants. This pilot extracts three primitives used by the actual Rust engine and verifies that exact source with Kani 0.68.0: budget reservation, strict contract gates and bounded text-range preservation.
The report records input/log SHA-256 hashes, tool metadata, completed harness results and explicit scope. Three deliberate mutations must fail the corresponding assertions. Missing tools, timeouts, incomplete checks and stale reports cannot pass. The reusable test workflow now includes this verification job and stores its evidence; proof-policy diffs are exposed for independent review.
Validation locally: all three properties verified and all three mutations detected; 149 core tests, 29 CLI integration tests, MCP tests, three evaluation scenarios, collector regressions, fmt and clippy passed. Source links, frontmatter and release metadata validated.
Limits: the text proof covers 0–4 ASCII bytes with unwind 6, while Unicode and caller wiring have regression tests. The pilot does not prove parser/filesystem behavior, complete OpenAPI compatibility, whole-program correctness or release-compiler equivalence. Specification review remains necessary. The v1.5.0 tag/binaries are unchanged; this is documented as unreleased work.
See
verification/PLAN.md,verification/RESULTS.md,verification/rules.jsonanddocs/verification-pilot.mdfor reproduction and trust assumptions.Remote validation: full test workflow and lint passed, including Linux/macOS/Windows, AST, ML, LSP, evaluations, all three Kani properties and all three negative controls. Downloaded the verification artifact, matched every source/log/result hash against this checkout, and successfully ran the report freshness checker on the downloaded evidence. Verification artifact.