Prepare a finding for external review

What the check reads

The default-on document-stage error applies to active KnownIssues carrying submission or upstream_report, or a disposition containing submit. It checks natspec_review, commit_origin, intended_path_verified and master_status, plus presence of poc_quality. High or critical claims need a recorded severity anchor or the permitted in-flight state. Filed severity is compared with the issue’s severity dimensions, and prior-audit duplicate signals receive additional scrutiny.

An illustrative case

Illustrative case: a PoC demonstrates an unsafe downstream operation, but no one checked whether documented use or an ingress guard prevents an external caller reaching it. A filled intended_path_verified field is not enough. Test the intended route and control path, then make the report’s conditions and claimed consequence match those observations.

Resolve the finding

1. Inspect the documentation, introducing change, current upstream code and actual usage path.
2. Retain the PoC quality review, severity basis and differentiation from prior findings. Correct any filed-versus-recorded grade drift.
3. Rerun this check and the per-rule PoC quality check before an authorized external send. Keep an awaiting external grade explicitly in flight.

proof audit --check submission_validated

Keep the conclusion bounded

The audit reads documentation and metadata; it does not authenticate a vendor verdict, independently query production value or verify the truth of every checklist answer. Passing it neither sends a report nor grants permission to contact a third party. Enforcement must be part of the actual submission workflow.

Continue with one real issue

Poc quality checked · Deployment tvl verified

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