Proof check reference
Reconcile approved guarantees with known issues
An approved guarantee and an active issue affecting that guarantee deserve to be reviewed together. This check highlights that tension when the issue has no nonblocking release disposition.
What the check reads
The default-on spec-stage check is an advisory warning. It selects active requirements with req_type: guarantee and review status approved, then joins active KnownIssues through affected_requirements IDs. Open, reviewed and empty issue statuses are treated as active. A nonempty release_disposition other than block acknowledges the conflict for this check. The join uses explicit IDs, not statements inferred from the issue’s prose.
proof audit --check approved_guarantee_ki_conflictAn illustrative case
Illustrative case: an approved guarantee says an unauthorized user cannot export records. A KnownIssue links that guarantee and records an export path that bypasses authorization. The conflict should lead to investigation and an explicit release decision. Filling in a nonblocking disposition clears this particular acknowledgement predicate, but cannot repair the path or supply authority to accept the exposure.
Resolve the finding
- Read the guarantee and linked issue together. Confirm that affected_requirements identifies the actual promise and that the issue’s evidence supports the recorded impact.
- Repair the behavior, narrow an incorrect claim through authorized review, or record an explicit, justified release disposition under the applicable policy. Preserve unresolved risk and its boundary.
- Rerun this check and the checks for approval freshness, issue completeness and evidence. Review the actual fix or release decision separately from this bookkeeping result.
What a clear result means
A clear result means no inspected approved guarantee has a linked active issue lacking the expected acknowledgement. It does not mean every issue was linked, the guarantee is true or the approval fingerprint is current. The check uses the stored approved status; approvals_current handles freshness. A release-disposition field is a recorded decision, not independent verification of its authority.
Continue with one real issue
Approvals current · 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.