Topic · acceptance review current

Acceptance review current

Gist

Acceptance review current is whether every active stakeholder requirement that already carries acceptance_criteria has stamped acceptance_review.disposition as reviewed, not_applicable, or deferred. Proof runs proof audit --check spec_lint_acceptance_review_current. Jama still authors.

proof audit --check spec_lint_acceptance_review_current

Keep Jira if it already owns the story Done list. Keep Jama if it already authors the shall. Neither one asks whether the AC was reviewed, or whether the text just restates a unit test.

Request demo Last silent missing stamp vs this hop

01 · The silent pending analysis

An AC list can sit on the STK while nobody stamps that anyone read it.

The hop is the acceptance-criteria counterpart of a hazard review stamp. A missing stamp is pending analysis, not a silent pass.

The check is spec_lint_acceptance_review_current. The lint rule is lint-acceptance-review-current. Stage spec. Default-on. Severity warning. It walks every active requirement that already carries acceptance_criteria. Requirements with no criteria are silent. Terminal and rejected requirements are skipped.

Three things fire. No acceptance_review block at all. A block whose disposition is empty or not one of reviewed, not_applicable, deferred. Acceptance-criterion text that matches unit test, case-insensitive. The slogan warning is separate from the stamp. Both can fire on the same row.

proof audit --check spec_lint_acceptance_review_current
# STK-REQ-001 has acceptance_criteria.
# acceptance_review is missing.
# lint-acceptance-review-current warns: AC analysis still pending

Stamp the review after the ac-sweep analysis. The hop does not write the YAML. It does not run the acceptance test. The witness that a testable criterion has its own acceptance test stays on acceptance criteria.

acceptance_review:
  reviewed_at: "2026-09-26T00:00:00Z"
  reviewed_by: "agent:ac-sweep"
  disposition: reviewed
  notes: "Observable fixture, actor, action, assert. Not a unit-test restatement."

Run the role for the procedure. Onboard checklist confirm of ac-sweep stays refused until acceptance_criteria_witnessed is green, or the step is honestly not confirmed. Never annotate a unit test as :acceptance.

proof role show ac-sweep --format agent
proof audit --check spec_lint_acceptance_review_current
proof audit --check acceptance_criteria_witnessed

02 · The exhibit

Same STK-REQ-001. Silent missing stamp, or this hop.

Active status. AC list present. No acceptance_review. Click the tabs.

The row

Ask does STK-REQ-001 exist and carry an AC list
Stamp the YAML is there, acceptance_review is blank, nobody asked
Why a Done list on the story never asks whether anyone reviewed the AC

Status green

This hop

Nobody asked whether the AC was reviewed, deferred, or not applicable. The finding kind is this hop.

Stamp unread

The row

Keep the Jira story. Keep the Jama AC field. That is not this hop.

Keep the record

Proof

Ask does every active STK with ACs stamp reviewed, not_applicable, or deferred, and is the text not a unit-test slogan
Out STK-REQ-001 has no acceptance_review stamp. AC analysis still pending. Run proof role show ac-sweep --format agent

Pending counted

Same STK-REQ-001. Silent missing stamp, or this hop. Click the tabs.

Surface	What they do	What Proof does	What we lose
Jira Done list	Acceptance criteria as story copy.	A stamp that the AC was reviewed, deferred, or marked not applicable.	Not the story template.
acceptance_criteria_witnessed	Whether a testable AC has its own acceptance test, not a child unit test.	Whether the AC list was stamped at all, and whether the text is a slogan.	Not the witness hop. See acceptance criteria.
hazard_review_current	Whether a hazard analysis stamp is present on the requirement that needs one.	The same pending-analysis shape, for acceptance criteria instead of hazards.	Not the hazard hop. See hazard analysis tied to the component.
Cucumber scenario	Given / When / Then as living documentation.	A YAML disposition. Slogan text that names a unit test is a warning.	Not the Gherkin runner.
Jama field	The authoring programme. An AC if you put it there.	A stamp the audit can name next to the STK that already carries criteria.	Not Jama's V&V. Jama still authors. We have not run a frozen Jama pack.

The teaching graph is still one AC list next to an empty stamp. Write the disposition, or opt out on that requirement. Do not treat a Jira Done field as this cell. Do not treat a unit-test restatement as an observable criterion.

proof role show ac-sweep --format agent
proof audit --check spec_lint_acceptance_review_current --verbose
proof audit --check acceptance_criteria_witnessed

The witness hop stays on acceptance criteria. Jama still authors. Proof vs Jama.

03 · The honest loss

Proof names a missing stamp. It does not write the review, and it does not prove the Go.

A quiet proof audit --check spec_lint_acceptance_review_current can still mean there were no acceptance criteria. Jama still authors.

The hop does not call ac-sweep for you. It does not write acceptance_review. It does not execute an acceptance test. Severity is warning; findings do not fail the first install. Zero ACs on a requirement is a silent pass. Terminal and rejected rows are skipped. Slogan detection is the substring unit test, not a quality model of the criterion. Opt-out is lint-acceptance-review-current on audit_ignore, or the check id on project.checks.disabled; that is skip, never pass. An extras stamp with a valid disposition still counts. 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 witness hop stays on acceptance criteria. 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 acceptance review current? Same question. Same URL.

Is this acceptance criteria? No. That hop is whether a testable AC has its own acceptance test. This hop is whether the AC list was stamped, and whether the text is a unit-test slogan. See acceptance criteria.

Is this hazard review current? No. Same pending-analysis shape, different object. See hazard analysis tied to the component.

Does a requirement with no ACs fail? No. Zero criteria is silent. The hop only runs on rows that already carry acceptance_criteria.

Does a missing stamp fail the merge? No. The hop warns. A green VERIFY can still carry pending AC analysis unless you raise the fail level.

What is a slogan AC? Criterion text that matches unit test, case-insensitive. Write an observable fixture, actor, action, and assert. Do not restate a unit test.

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.