Check the evidence behind a defect disposition

What the check reads

The verify-stage check reads proof/problem-reports YAML. It validates schema and disposition fields, resolves linked requirements and closure evidence, checks KnownIssue and AcceptedRisk alignment, and inspects required hardening for gap-rooted covered_by_requirement closures. Review debt is advisory. Dangerous findings remove advisory treatment, so configured fail-level policy can make them blocking; the result is not uniformly an error for every report.

An illustrative case

Illustrative case: a report says a missing boundary requirement was added and the defect is covered_by_requirement. The new requirement exists, but the claimed obligation is not attached to its checklist. The hardening claim remains unsupported. Repair the actual requirement and evidence relationships or revise the disposition to reflect the unfinished work.

Resolve the finding

1. Inspect the named report and finding kind with proof problem-report show and triage.
2. Resolve missing references and supply the evidence required by the chosen disposition. Keep a still-live failure in a KnownIssue.
3. Review any missing requirement, test partition or MC/DC-variable hardening, then rerun validation and the audit.

proof audit --check problem_reports_reviewed

Keep the conclusion bounded

A resolving evidence reference is not an executed result, and a completed closure record does not prove every instance in a defect class is impossible. Scope the closure to the reviewed obligations and observed evidence. An empty report corpus passes because there are no records to inspect, not because the software has no defects.

Continue with one real issue

Software problem report · Known issue sibling disposition

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