Review known issues on a usable cadence

What the check reads

The verify-stage warning reports active issues with missing, unreadable or stale review_date values, plus release_disposition: block. The default review interval is 90 days and can be configured with review_interval_days. Setting it to zero treats review_date as a due date. Current non-blocking issues remain visible in a passing summary. An unset issue status is treated as active by the shared predicate.

proof audit --check known_issues_reviewed

An illustrative case

Illustrative case: an issue was reviewed last week and remains accurately described. Under the default interval, it is current. An issue last reviewed four months ago needs reassessment, while deleting its date produces a never-reviewed finding. If a fix already landed, updating only the review date would keep resolved work circulating unnecessarily.

Resolve the finding

1. Inspect the issue and current evidence before choosing a disposition.
2. If it remains live, record an actual review. If fixed or withdrawn, retain the supporting reason and update status accurately.
3. Resolve a release block through the responsible authority. Record any accepted product risk separately rather than silently changing the field to suppress a warning.

What a clear result means

A recent date cannot establish that someone reviewed the behavior, and the audit does not rerun every issue. Warning handling depends on the project’s enforcement configuration. Keep the review act, current reproducer evidence and release authority distinct so the next reviewer can understand each decision.

Continue with one real issue

Known issue recheck due · Risk acceptance

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