Known issues reviewed

The check reads proof/known-issues/*.yaml. Active records with a current review date stay informational. A review_date in the past, or release_disposition: block, becomes a warning. The hop does not fail the merge. Zero files is a pass: nothing to review. That pass is empty, not reviewed.

A KnownIssue is not an AcceptedRisk and not a waiver. proof known-issue review stamps a human and a new date after you re-read the failure. proof known-issue edit --set-status fixed closes a record that no longer reproduces. withdrawn is the recorded way to say the filing was never real. If the team is shipping with the behavior, that is risk acceptance, not a date bump on this YAML.

The silent case is a date refresh without a re-read. The hop sees a future day and stays informational. The record still describes a failure nobody checked. Refreshing a fixed issue is worse: it keeps resolved behavior in the active set as noise.

proof audit --check known_issues_reviewed --verbose
proof known-issue list --status open
proof known-issue review KI-3 --reviewer human:jane --new-review-date 2026-10-01
proof known-issue edit KI-3 --set-status fixed --set-remediation "reproduced no longer"

Re-read the failure before you stamp the date. Close it if it is gone. Do not delete the file to clear the warning. Do not flip release_disposition from block to ship without a human. Agents do not make that release call.

The teaching graph is still one KnownIssue next to its review day. Run the check. Read the id. Re-read the failure, then stamp, close, or withdraw. Do not bump the date to hide a fix that already landed.

proof workflow check --stage verify --verbose
proof audit --check known_issues_reviewed --verbose
proof known-issue list --status open
proof known-issue review KI-3 --reviewer human:jane --new-review-date 2026-10-01

The signed-ship hop stays on risk acceptance. The skip-date hop stays on waivers reviewed. Jama still authors. Proof vs Jama.

Zero files is a pass. That pass did not review anything. A future review_date is informational even if nobody reproduced the issue this week. The hop warns; it does not fail. It does not rewrite the YAML. It does not close a fixed record. It does not sign an AcceptedRisk. Flipping release_disposition from block is a human release call this hop will not make. We have not scored this graph against a frozen Jama pack or a Salesforce status page. The loss is named, not scored.

The signed-ship hop stays on risk acceptance. The engagement stays on software correctness audit. Jama still authors.

What is known issues reviewed? Same question. Same URL.

Is this risk acceptance? No. That hop is a named human shipping a known failure. This hop is whether an open KnownIssue still has a current review date. See risk acceptance.

Is this residual kill hygiene? No. That hop warns a closed quantitative hunt kill with empty samples. A residual is not a KnownIssue. See residual kill hygiene.

Is this concern adjudicated? No. That hop is whether an open KI-lite note is past review_due, or has no date. A Concern is not a KnownIssue until you promote it. See concern adjudicated.

Is this a Salesforce known issue? No. Ads known issue is that status page. A hosted vendor bulletin is not this cell.

Is this known issue complete? No. That hop is whether the record has evidence and an origin. This hop is whether review_date is still current. See known issue complete.

Is this known issue recheck due? No. That hop is whether an upstream_report schedule has lapsed on a non-terminal vendor status. This hop is whether review_date is still current. See known issue recheck due.

Is this known issue security remediation present? No. That hop is whether a security-relevant KI documents containment. This hop is whether review_date is still current. See known issue security remediation present.

Is this known issue severity prose consistent? No. That hop is whether the title grades one severity and the field records another. This hop is whether review_date is still current. See known issue severity prose consistent.

Is this known issue sibling disposition? No. That hop is whether a close left siblings or sites undispositioned. This hop is whether review_date is still current. See known issue sibling disposition.

Is this defect review current? No. That hop is whether the spec was claim-reviewed before a KI existed. This hop is whether an open KnownIssue still has a current review date. See defect review current.

Does a missing known-issues directory fail? No. Zero files is a pass. Put a YAML there when the behavior is confirmed.

Does a stale date fail the merge? No. The hop warns. A green VERIFY can still carry a past review_date unless you raise the fail level.

Is this approved guarantee KI conflict? No. That hop joins an approved guarantee against an open KI with no acknowledgement. This hop is whether review_date is still current. See approved guarantee KI conflict.

Is Proof a Jama alternative for the shall? No. Jama still authors. Proof vs Jama.