Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Skeleton for the follow-up to the rind launch post: rind, but formally verified. It covers every correctness mechanism, not just the proofs. Headings are the outline; bullets are notes and PR links to write from. Every
TODOis yours to fill.Facts gathered
Source: moq-dev/rind
origin/main0f4e45f0 (2026-11-12), plusproofs/README.md,TESTING.mdandquest/.Proof stack:
admin/prove bytesties the proofs to the shipped object code.What "verified" means here: functional correctness only. Memory safety and panic-freedom are not proven. Constant time is proven only for the asm compares and s2n-bignum's
_SAFEroutines.The launch post needs a caveat. It says AES-GCM is verified, but it's proven only on x86_64 AES-NI. VAES CPUs and aarch64 are not covered.
Five checks per primitive, enforced by
admin/testing:On top of that: cross-arch runs (SDE plus qemu), mutation testing, and the adversarial
REVIEW.md.Roadmap: m3 is SHA-NI SHA-256. m4 is the hot tiers, 24 quests. m5 is the cold tiers.
Waiting
<Coverage />and the launch post's cover.libraries.jsonneeds regenerating from current rind for this post. Should it stay shared with the launch post or be split?Public API and wire impact
None.
Validation
bunx biome checkandbun astro build --mode stagingpass, and/blog/rind-verifiedrenders with the coverage chart.Models
Size: S
Implementer: Claude Code, claude-opus-5-5, unknown effort
(Written by Opus 5.5)
🤖 Generated with Claude Code