Anchor high-impact deployment claims

What the check reads

The document-stage advisory warning auto-applies to detected Web3/DeFi projects; other projects must explicitly enable it. It examines active KnownIssues with high or critical severity claims, including code_severity and bounty_severity. It accepts recorded production_tvl or an attributable external verdict upholding a high or critical grade against a cited ruleset. A findable report awaiting grading is tracked as in flight, not counted as anchored or flagged.

proof audit --check deployment_tvl_verified

An illustrative case

Illustrative case: an author files a high-severity report with a vendor. The ticket proves that the report exists, not that the vendor agreed with its severity. An acknowledgement without a grade leaves the claim in flight. If the eventual verdict downgrades or rejects the claim, the record needs reconciliation rather than an unchanged high label.

Resolve the finding

1. Identify whether deployment exposure or an independent severity decision is the relevant basis for this issue.
2. Retain the evidence and fill the corresponding deployment, submission or upstream_report fields accurately.
3. Record incoming verdicts and update any conflicting severity claim. Rerun the check while preserving unresolved grading as in flight.

What a clear result means

The audit reads recorded fields; it does not independently query a chain or authenticate a vendor decision. Explicit low or informational bounty severity has a separate downgrade path. This specialized policy is not a universal measure of software risk, and an anchor does not prove exploitability.

Continue with one real issue

Submission validated · High severity reproducer grade

Bring one finding, its requirement and the current evidence to scope a walkthrough of what your reviewer can establish and what still needs work.