Skip to content

Revise the unsafe Rust skill after the V3 evaluation - #3531

Open
joshlf wants to merge 1 commit into
Glzlcl663nbggljjqi64x7gs3yyw5b7ysfrom
Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb
Open

Revise the unsafe Rust skill after the V3 evaluation#3531
joshlf wants to merge 1 commit into
Glzlcl663nbggljjqi64x7gs3yyw5b7ysfrom
Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb

Conversation

@joshlf

@joshlf joshlf commented Aug 3, 2026

Copy link
Copy Markdown
Member

Rework the proof model around lossless representations and locally checkable
certificates, following the V3 gate failure and qualitative diagnosis.

Require an explicit case domain for each quantified claim and describe how
inputs map to obligation fibers. For equality, containment, disjointness, and
incomparability claims, require the exact direction-specific certificate and
the separating witnesses the relation demands. Treat feature, target,
allocator, toolchain, and policy expressions as semantic sets whose operators
must be justified before their denotations may be composed.

Model ordered and fallible construction as a staged relation rather than an
endpoint summary. Require transformations to retain enough information to
reverse or independently check the derivation, and reject prose such as by
inspection or all cases when the case mapping is not shown. Scope
counterexamples to the verdict actually requested: one complete existential
unsoundness witness closes UNSOUND, while exhaustive characterization is a
separate deliverable.

Preserve the V3 strengths: whole-execution UB reasoning, exact supported-domain
coverage, producer quantifiers, verdict certificates, reconstructed-proof
reporting, module-local invariant discipline, and the conditional
abstraction-design workflow. Do not add fixture names or hazard lists to the
agent-facing skill.


Latest Update: v5 — Compare vs v4

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v4 v3 v2 v1 Base
v5 vs v4 vs v3 vs v2 vs v1 vs Base
v4 vs v3 vs v2 vs v1 vs Base
v3 vs v2 vs v1 vs Base
v2 vs v1 vs Base
v1 vs Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb && git checkout -b pr-Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb FETCH_HEAD

Checkout

git fetch origin refs/heads/Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb

Stacked PRs enabled by GHerrit.

@codecov-commenter

codecov-commenter commented Aug 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.85%. Comparing base (86a3709) to head (4179be5).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           Glzlcl663nbggljjqi64x7gs3yyw5b7ys    #3531   +/-   ##
==================================================================
  Coverage                              91.85%   91.85%           
==================================================================
  Files                                     20       20           
  Lines                                   6093     6093           
==================================================================
  Hits                                    5597     5597           
  Misses                                   496      496           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Rework the proof model around lossless representations and locally checkable
certificates, following the V3 gate failure and qualitative diagnosis.

Require an explicit case domain for each quantified claim and describe how
inputs map to obligation fibers. For equality, containment, disjointness, and
incomparability claims, require the exact direction-specific certificate and
the separating witnesses the relation demands. Treat feature, target,
allocator, toolchain, and policy expressions as semantic sets whose operators
must be justified before their denotations may be composed.

Model ordered and fallible construction as a staged relation rather than an
endpoint summary. Require transformations to retain enough information to
reverse or independently check the derivation, and reject prose such as by
inspection or all cases when the case mapping is not shown. Scope
counterexamples to the verdict actually requested: one complete existential
unsoundness witness closes UNSOUND, while exhaustive characterization is a
separate deliverable.

Preserve the V3 strengths: whole-execution UB reasoning, exact supported-domain
coverage, producer quantifiers, verdict certificates, reconstructed-proof
reporting, module-local invariant discipline, and the conditional
abstraction-design workflow. Do not add fixture names or hazard lists to the
agent-facing skill.

gherrit-pr-id: Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb
@joshlf
joshlf force-pushed the Glzlcl663nbggljjqi64x7gs3yyw5b7ys branch from 7a81574 to 86a3709 Compare August 29, 2026 11:11
@joshlf
joshlf force-pushed the Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb branch from b873e00 to 4179be5 Compare August 29, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants