Topic · known issues reviewed

Known issues reviewed

Gist

Known issues reviewed is whether an open KnownIssue still has a current review date. Proof runs proof audit --check known_issues_reviewed. A fresh date without a re-read is not a review. Jama still authors.

proof audit --check known_issues_reviewed

Keep Salesforce if you already file product bugs there. Keep Jama if it already holds the shall. Neither one dates a KnownIssue YAML in this repo.

Request demo Last silent stamp vs this hop

01 · The record that outlived the date

A KnownIssue is confirmed bad behavior. This hop asks whether a human still stands behind that record.

You can keep KI-3 open, keep VERIFY green, and still ship after review_date is in the past, if this hop never ran or only warned.

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.

02 · The exhibit

Same KI-3. A silent current, or this hop.

KI-3 is still open. The last review_date is 2026-01-01. Click the tabs.

The row

Ask did VERIFY stay green
Review 2026-01-01
Why the hop warns, it does not fail

Stamp green

This hop

No known_issues_reviewed JSON. Stale date never named. Merge stayed green.

No stamp

The row

Keep the YAML. Keep the failure mode. That is not this hop.

Keep the record

Proof

Ask is review_date still a future day
Out KI-3: review_date 2026-01-01 is past

Stale review

Same KI-3. A silent current, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Salesforce Known Issue	A vendor status page for a hosted product.	Date a repo YAML under `proof/known-issues/`.	We do not host your customer-facing status page. Ads `known issue` is that SERP.
Risk acceptance	A named human ships a known failure with a review date.	Warn when an open KnownIssue is past its review day.	Not that hop. See risk acceptance.
`proof known-issue review`	The write. Human, new date, after a re-read.	The review of those dates on VERIFY.	This hop does not write the record. A date bump without a re-read still passes.
Jama	The authoring programme. Reviews if you put them there.	Warn on a stale review_date in this repo.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

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.

03 · The honest loss

Proof names a stale review. It does not re-read the failure for you.

A green known_issues_reviewed is current dates on eligible rows. It is not a proof of the Go. Jama still authors.

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.

Request demo How the install is bought

04 · Nearby questions

What people type next.

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 a Salesforce known issue? No. Ads known issue is that status page. A hosted vendor bulletin is not this cell.

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 Proof a Jama alternative for the shall? No. Jama still authors. Proof vs Jama.