Verification#6
Merged
Merged
Conversation
Removed excessive emojis and made the presentation more minimalist: - Cleaner intro with core stats - More professional value proposition section - Simplified architecture visualization - Streamlined proven properties section - Cleaner example contracts table - More concise design principles - Professional tone throughout Goal: Make it compelling and clear for technical readers while maintaining the strong verification value proposition. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The useConfig() hook in nextra v4 returns { frontMatter, ... } structure
instead of having title directly on config object.
Fixed by destructuring frontMatter and accessing title/description from it.
This resolves the build error:
"Property 'title' does not exist on type..."
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Feb 14, 2026
Th0rgal
pushed a commit
that referenced
this pull request
Feb 22, 2026
AUDIT.md previously documented only the ContractSpec → IR → Yul proven pipeline. Add the AST compilation path (--ast flag) which bypasses ContractSpec/IR and compiles Verity.AST.Stmt directly to Yul without formal proofs. Changes: - Architecture diagram: show both proven (ContractSpec) and unproven (AST) compilation paths side by side - Key files table: add ASTDriver, ASTSpecs, ASTCompile - Trust boundaries table: add AST → Yul row (trusted: ASTCompile correctness, verified: CI bytecode diff baseline only) - Known risks: add #6 documenting AST path limitations (no events, custom errors, internal functions, isPayable; 6 known bytecode mismatches tracked in allowlist) - CI suite: clarify check_yul_compiles.py enforces legacy/AST diff baseline Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
Th0rgal
added a commit
that referenced
this pull request
Feb 22, 2026
AUDIT.md previously documented only the ContractSpec → IR → Yul proven pipeline. Add the AST compilation path (--ast flag) which bypasses ContractSpec/IR and compiles Verity.AST.Stmt directly to Yul without formal proofs. Changes: - Architecture diagram: show both proven (ContractSpec) and unproven (AST) compilation paths side by side - Key files table: add ASTDriver, ASTSpecs, ASTCompile - Trust boundaries table: add AST → Yul row (trusted: ASTCompile correctness, verified: CI bytecode diff baseline only) - Known risks: add #6 documenting AST path limitations (no events, custom errors, internal functions, isPayable; 6 known bytecode mismatches tracked in allowlist) - CI suite: clarify check_yul_compiles.py enforces legacy/AST diff baseline Co-authored-by: Claude <noreply@anthropic.com>
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
2 participants
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.
Note
Low Risk
Low risk documentation-only changes; the only behavior change is docs-site title/description generation which could affect SEO/page titles if front matter is missing or misconfigured.
Overview
Reworks
README.mdto be more verification-focused: tighter intro/value proposition, updated quick example with a concrete proof sketch, clearer architecture/properties/roadmap sections, and streamlined build/getting-started/docs links.Updates
docs-site/theme.config.tsxto derive the page<title>and meta description fromfrontMatter(instead ofconfig.title/config.frontMatter), making metadata consistently reflect per-page front matter.Written by Cursor Bugbot for commit 2945478. This will update automatically on new commits. Configure here.