Topic · concern adjudicated

Concern adjudicated

Gist

Concern adjudicated is whether an open informal observation under proof/concerns/ is past review_due, or has no review_due at all. Proof runs proof audit --check concern_adjudicated. Jama still authors.

proof audit --check concern_adjudicated

Keep Jira if it already owns the sticky. Keep Jama if it already authors the shall. Neither one asks whether a note in this repo was promoted or waived.

Request demo Last silent open Concern vs this hop

01 · The silent open note

A YAML observation can sit forever while nobody decides if it is a defect.

A Concern is KI-lite. Promote it to a KnownIssue, or waive it with a written reason. Leaving it open with no date is unscheduled debt.

The check is concern_adjudicated. Stage verify. Default-on. Severity warning. It reads proof/concerns/*.yaml. Missing that directory is a pass of no concerns directory (concern adjudication no-op). An empty directory is a pass. Terminal statuses promoted and waived never fire, even when review_due is in the past.

The object is lighter than a KnownIssue on purpose. No CVSS. No severity basis. No evidence floor. The hop only asks whether an open record still has a clock, and whether that clock has run out. See known issues reviewed.

proof concern list --status open
# CONCERN-12 is open.
# review_due is empty.
# concern_adjudicated warns: missing review_due

Two things land in the due set. An open Concern whose parsed review_due is today or earlier. An open Concern whose review_due field is blank. Omitting the field is not an escape. The hop counts it as due so mandatory adjudication cannot be skipped by deleting the date.

The hop does not promote the record. It does not waive it. It does not file a KnownIssue. Status on a finding is warn, not fail. A green VERIFY can still carry overdue notes unless you raise the fail level.

proof concern list --status open
proof concern show CONCERN-12
proof known-issue new --title "..."
proof concern promote CONCERN-12 --known-issue KI-9
proof concern waive CONCERN-12 --reason "Out of audit scope after reviewing the sample domain thoroughly."
proof audit --check concern_adjudicated --verbose

A waive rationale must be at least 32 characters. That floor lives on proof concern waive, not on this hop. Extending review_due is only honest while you are still investigating. Pushing the date out to hide a confirmed failure is the wrong object. File the KnownIssue.

02 · The exhibit

Same CONCERN-12. Silent open note, or this hop.

Open status. Empty review_due. Click the tabs.

The row

Ask does CONCERN-12 exist and say open
Stamp the file is there, review_due is blank, nobody asked
Why a note in YAML never asks whether anyone decided

Status green

This hop

Nobody asked whether the observation is a failure mode or noise. The finding kind is this hop.

Clock unread

The row

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

Keep the record

Proof

Ask is every open Concern inside review_due, with the field actually set
Out CONCERN-12: review_due=(unset). Promote to a KnownIssue, or waive with ≥32 characters

Debt counted

Same CONCERN-12. Silent open note, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Jira sticky	An informal ticket with no clock.	A YAML Concern whose open state still has a due date, or is flagged.	Not the ticket thread.
known_issues_reviewed	Whether a live KnownIssue still carries a current `review_date`.	Whether a KI-lite note was promoted or waived before the clock ran out.	Not the live-bug hop. See known issues reviewed.
residual_kill_hygiene	Whether a closed quantitative hunt kill still has samples.	Whether an informal observation still has a decision.	Not the hunt hop. See residual kill hygiene.
risk acceptance	A named human shipping a known failure.	A note that has not yet been decided as a failure.	Not the shipping hop. See risk acceptance.
waivers_reviewed	Whether a Proof-check exception still carries a current review.	Whether a Concern was waived as not a tracked defect.	Not the check-exception hop. See waivers reviewed.
Jama field	The authoring programme. A comment if you put it there.	A YAML Concern the audit can name next to the shall it related.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one open note next to an empty clock. Promote it, waive it, or set a real review_due while you are still looking. Do not treat a Jira "To Do" as this cell.

proof concern list --status open
proof concern show CONCERN-12
proof concern promote CONCERN-12 --known-issue KI-9
proof audit --check concern_adjudicated --verbose

A confirmed user-observable failure is a KnownIssue, not a Concern that keeps getting its date pushed. See known issues reviewed. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names overdue notes. It does not write the decision, and it does not prove the Go.

A quiet proof audit --check concern_adjudicated can still mean there is no concerns directory. Jama still authors.

The hop does not call proof concern promote for you. It does not waive. It does not file a KnownIssue. Missing proof/concerns/ is a pass that reviewed nothing. An empty directory is the same kind of pass. Severity is warning; findings land as warn, not fail. Opt-out reports skip, never pass. A non-empty review_due that does not parse as RFC3339 or YYYY-MM-DD is not counted as due. Pushing the date is allowed while you investigate; it is not a resolution for a confirmed defect. The hop does not check CVSS, evidence, or waive-reason length. 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 live-bug hop stays on known issues reviewed. The hunt hop stays on residual kill hygiene. 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 concern adjudicated? Same question. Same URL.

Is this known issues reviewed? No. That hop is whether a live KnownIssue still carries a current review_date. A Concern is KI-lite until you promote it. See known issues reviewed.

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

Is this risk acceptance? No. That hop is a named human shipping a known failure. This hop is whether an informal note still has a decision. See risk acceptance.

Is this waivers reviewed? No. That hop is a Proof-check exception. Waiving a Concern means the observation is not a tracked defect. See waivers reviewed.

Does a missing concerns directory fail? No. Zero files pass with no concerns directory (concern adjudication no-op).

Does an empty review_due fail the merge? No. The hop warns. A green VERIFY can still carry unscheduled debt unless you raise the fail level.

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.