Topic · approved guarantee KI conflict

Approved guarantee KI conflict

Gist

Approved guarantee KI conflict is an approved guarantee that an open known issue already names, with no explicit ship-despite acknowledgement. Proof runs proof audit --check approved_guarantee_ki_conflict. A bulk-approve wave can still stamp the shall. Jama still authors.

proof audit --check approved_guarantee_ki_conflict

Keep the live shall if it is still true. Keep Jama if it already holds it. Neither one fails the merge when the approval and the open KI live in separate files.

Request demo Last silent approval vs this hop

01 · The silent approval

The stamp can sit on a guarantee an open known issue already violates.

You can keep verification.review.status: approved after a KnownIssue names the same id. The suite still runs. The approval file still looks current.

The check is approved_guarantee_ki_conflict. It is spec-stage. Severity of a conflict is warning, not fail. The inspect command is the same audit, plus proof workflow check --stage spec --verbose.

The hop joins active requirements whose req_type is guarantee and whose review status is approved against KnownIssues that name that id in affected_requirements. Open means status open, reviewed, or absent. fixed and withdrawn never conflict. Acknowledgement is the issue's release_disposition: ship, ship_with_known_issue, not_in_scope, or fixed clears the finding. Unset and block do not.

The help file teaches the bulk-approve wave first. Approval and known-issue tracking live in separate files. Nothing in the suite asked whether they contradicted.

# specs/sys/PAY-SYS-025.yaml
id: PAY-SYS-025
req_type: guarantee
verification:
  review:
    status: approved

# .proof/known-issues/KI-441.yaml
id: KI-441
status: open
affected_requirements:
  - PAY-SYS-025
# release_disposition: unset

# proof audit --check approved_guarantee_ki_conflict
# [SPEC] approved_guarantee_ki_conflict -- PAY-SYS-025: approved guarantee is violated by open known issue(s) KI-441 with no acknowledgement
# silent approval: the suite still printed green

Close the known issue if the guarantee holds. Record ship_with_known_issue if the project ships with eyes open. Reopen review if the stamp should not stand. Then re-run the same check. Do not mark the KI fixed because the finding is inconvenient.

proof known-issue edit KI-441 --set-release-disposition ship_with_known_issue
proof known-issue edit KI-441 --set-status fixed --set-remediation "deadline packing no longer truncates"
proof review req PAY-SYS-025
proof audit --check approved_guarantee_ki_conflict
proof workflow check --stage spec --verbose

02 · The exhibit

Same guarantee. A silent stamp, or this hop.

One approved shall. An open KI names it. No disposition. Click the tabs.

The stamp

Ask did the suite still print green
Stamp PAY-SYS-025 approved. KI-441 still open. No disposition
Why the approval file still looks current. The tests still run

Suite green

This hop

Nobody asked whether the open KI that names this guarantee had an explicit ship-despite record. A green suite is not a cross-check. The finding kind is this hop.

KI unread

The stamp

Keep the live shall. Keep the Jama cell. That is not this hop.

Keep the record

Proof

Ask does this approved guarantee share an id with an open KI that has no acknowledgement
Out PAY-SYS-025 violated by KI-441 with no acknowledgement

Silent approval counted

Same guarantee. A silent stamp, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Green suite	The tests that still ran.	Whether an approved guarantee shares an id with an unacknowledged open KI.	We do not rerun the suite here. A green stamp is not this hop.
Approvals current	Whether the stored fingerprint still matches the shall.	Whether that current approval contradicts an open KI on the same id.	Not the fingerprint hop. See approvals current.
Known issues reviewed	Whether an open KI still has a current review date.	Whether that KI names an approved guarantee with no disposition.	Not the review-date hop. See known issues reviewed.
Risk acceptance	A named human shipping a known failure.	A structural `release_disposition` on the KI, or a closed status.	Not the named-human hop. See risk acceptance.
Jama cell	A shall, and a note if you type it.	A warning the audit can name next to the requirement id.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one guarantee whose board called the stamp done and whose open KI never recorded a disposition. Close it by fixing the issue, recording ship_with_known_issue, or reopening review. The same hop also catches block: refusing to ship the very guarantee you approved is still a contradiction. A prose mention in the KI title is silent. Do not treat a Jama note as this hop. Do not treat a green suite as a cross-check.

# .proof/known-issues/KI-441.yaml
id: KI-441
status: open
affected_requirements: [PAY-SYS-025]
release_disposition: block

# proof audit --check approved_guarantee_ki_conflict
# PAY-SYS-025: approved guarantee is violated by open known issue(s) KI-441 with no acknowledgement

The fingerprint hop stays on approvals current. The review-date hop stays on known issues reviewed. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names the silent contradiction. It does not write the disposition, and it does not prove the Go.

A quiet proof audit --check approved_guarantee_ki_conflict can still mean there were no open unacknowledged KIs, or no approved guarantees. Jama still authors.

Warning, not fail. Not blocking. No project loaded is a pass. No open unacknowledged known issues is a pass. The hop looks at req_type, verification.review.status, affected_requirements, KI status, and release_disposition. It does not read verification_state. It does not match prose in the title or notes. It does not write the KI. It does not reopen review. It does not prove the Go. Constraint and stakeholder rows are silent. A load error on the known-issue directory is a fail, not a warning. Scope can skip a path. We have not scored this floor against a frozen Jama pack or a ReqIF export. The loss is named, not scored.

The fingerprint hop stays on approvals current. 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 approved guarantee KI conflict? Same question. Same URL.

Is this approvals current? No. That hop is whether the stored fingerprint still matches the shall. This hop is whether that stamp contradicts an open KI. See approvals current.

Is this known issues reviewed? No. That hop is whether review_date is still current. This hop is the join against an approved guarantee. See known issues reviewed.

Is this risk acceptance? No. That hop is a named human shipping a known failure. This hop is a structural disposition on the KI. See risk acceptance.

Is this concern adjudicated? No. A Concern is not a KnownIssue until you promote it. See concern adjudicated.

Does a tree with no known issues pass? Yes. No open unacknowledged KIs is a pass. That is not a proof that other languages are covered. It is a proof that this hop had nothing to join.

Does a green hop prove the code matches the shall? No. The hop observes YAML fields. It does not prove the Go.

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