Topic · problem reports reviewed

Problem reports reviewed

Gist

Problem reports reviewed is whether every DEFECT under proof/problem-reports/ is structurally sound, and whether any closure claim is backed by the artifacts that disposition requires. Proof runs proof audit --check problem_reports_reviewed. Jama still authors.

proof audit --check problem_reports_reviewed

Keep Jira if it already owns the ticket. Keep Jama if it already authors the shall. Neither one asks whether a closed class actually hardened.

Request demo Last silent closed DEFECT vs this hop

01 · The silent closed class

A DEFECT can stamp covered while the hardening never landed.

A ProblemReport is post-fix class-closure evidence. A false closure is more dangerous than an honestly open stub, because it makes an unverified class look verified.

The check is problem_reports_reviewed. Stage verify. Default-on. Severity warning. Advisory until a dangerous finding is present, then the hop is a hard failure. It reads proof/problem-reports/*.yaml. An empty corpus passes with no problem reports. That is correct when there are no closed classes yet. Live unfixed bugs live in proof/known-issues/, not as open DEFECTs. See software problem report.

The object page is that URL. Its command is proof problem-report validate: one record, the fields the chosen disposition requires. This hop is the always-on audit over the whole corpus. A single validate can look clean while the ledger still carries a false closure, a dangling evidence id, or an open DEFECT on a product surface.

proof problem-report new --template --output -
# DEFECT-44 stamps covered_by_requirement.
# root_cause names a missing requirement.
# no hardening.new_requirements.
# problem_reports_reviewed fails: hardening_missing

Dangerous findings fail the hop: invalid_schema, false_closure_claim, release_blocking_open_report on a strict surface (runtime / config / data / security / error handling), trace_missing under a closure status, known_issue_alignment_missing, risk_alignment_missing, closure_evidence_missing, mcdc_alignment_missing, hardening_missing. Advisory findings stay visible without flipping the hop by themselves: open_report on a non-strict surface, stale_review past 90 days, triage_debt, unfixed_bug_semantics.

The hop does not write the disposition. It does not file a KnownIssue. It does not attach the obligation. proof problem-report triage <id> names the missing fields. Then you edit the YAML, or you retract the claim.

proof problem-report list
proof problem-report show DEFECT-44
proof problem-report triage DEFECT-44 --include-prompts
proof audit --check problem_reports_reviewed --verbose

A covered_by_requirement closure on a gap-rooted defect must record the resolving hardening, and any obligation it claims to have added must actually sit on that requirement's obligation_checklist. Listing the class in the report is not attaching it.

02 · The exhibit

Same DEFECT-44. Silent closed class, or this hop.

Covered stamp. Missing requirement named. No hardening. Click the tabs.

The row

Ask does DEFECT-44 exist and say covered_by_requirement
Stamp the report is closed, the id resolves, no hardening block
Why a covered stamp never asks whether the class was hardened

Status green

This hop

Nobody asked whether the missing-requirement root cause recorded a new shall, or whether the claimed obligation is on SYS-REQ-501. The finding kind is this hop.

Hardening unread

The row

Keep the Jira ticket. Keep the Jama field. That is not this hop.

Keep the record

Proof

Ask does every closed DEFECT back the claim its disposition requires
Out DEFECT-44: hardening_missing. covered_by_requirement on a gap-rooted defect with no resolving hardening

Closure false

Same DEFECT-44. Silent closed class, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Jira ticket	A closed bug with a status enum.	A DEFECT whose closure fields resolve in the repo.	Not the ticket. See software problem report.
software problem report	The object and `proof problem-report validate` on one file.	The always-on corpus hop over every DEFECT.	Not the object page. Validate can look clean on one file while this hop still fails.
known_issues_reviewed	Whether a live KnownIssue still carries a current `review_date`.	Whether a post-fix DEFECT's closure is honest.	Not the live-bug hop. See known issues reviewed.
defect_review_current	Whether an adopted defect still has a review stamp in window.	Whether the class-closure record can back the stamp it already made.	Not the stamp hop. See defect review current.
change_record_lands	Whether a CHG or DEFECT with `affects:` is cited back from each named shall.	Whether the DEFECT's own disposition is backed.	Not the inverse cite. See change record lands.
Jama field	The authoring programme. Attributes if you put them there.	A YAML DEFECT the audit can name next to the requirement it claims to have hardened.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one covered stamp next to one missing hardening. Attach the obligation for real, record the corrective artifact, or retract the claim.

proof req edit SYS-REQ-501 --add-obligation <class-id>
proof problem-report validate --strict
proof audit --check problem_reports_reviewed --verbose

An open DEFECT on a strict surface is release_blocking_open_report. If the bug is still live in shipped code, the right object is a KnownIssue, not an open DEFECT. proof known-issue new. See software problem report.

The object hop stays on that URL. The live-bug hop stays on known issues reviewed. Do not treat a Jira "Done" status as this cell. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names a false closure. It does not write the disposition, and it does not prove the Go.

A quiet proof audit --check problem_reports_reviewed can still mean there are no problem reports. Jama still authors.

The hop does not call proof problem-report triage for you. It does not file a KnownIssue. It does not attach an obligation. An empty corpus is a pass of no problem reports, not proof that every class closed. Severity is warning; dangerous findings escalate to a hard failure, advisory findings do not. A dangling id is dangerous under a closure status and advisory under open / not_in_scope / non_product_change. covered_by_known_issue is legacy: do not park a new DEFECT on an open KI. Deleting the YAML destroys the historical record instead of dispositioning it. --strict being off is not a resolution. The hop does not prove the Go. We have not scored this floor against a frozen Jama pack. The loss is named, not scored.

The object hop stays on software problem report. 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 problem reports reviewed? Same question. Same URL.

Is this software problem report? No. That page is the object and proof problem-report validate on one file. This hop is the always-on corpus audit. See software problem report.

Is this known issues reviewed? No. That hop is whether a live KnownIssue still carries a current review date. A DEFECT is post-fix class-closure. See known issues reviewed.

Is this defect review current? No. That hop is a review stamp in window on an adopted defect. See defect review current.

Is this change record lands? No. That hop is whether a CHG or DEFECT with affects: is cited back. See change record lands.

Does an empty corpus fail? No. Zero reports pass with no problem reports.

Does a green hop prove the Go? No. The hop does not execute the function. It does not prove the shall.

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