recheck

Run recheck against the slice that failed signoff, for example "recheck slice B". It assembles the still-open BLOCKER and MAJOR items from the record, has an independent reviewer verify each failure scenario against the current source, and flips the status card only on evidence.

Signoff is the open-ended adversarial review that hunts for problems in a built slice. Recheck is a closed-checklist re-inspection that only verifies whether the specific findings signoff named were fixed — it never hunts for new issues.

Yes. Recheck makes one readers call on the claude-session row with the repo-with-tools profile so an independent reviewer, not the session that wrote the fixes, verifies each item. The call carries a floor of opus and is refused below it.

No. The session that wrote the fixes never grades them, and it cannot upgrade a reviewer's "not fixed" verdict on its own work. It records the dispute, leaves the item open, and recommends a fresh-session recheck.

A fix-introduced defect is recorded as its own new item with an assigned severity, file:line, claim, and failure scenario, and it joins the open set. Pre-existing issues newly noticed stay out of the verdict, with at most one line offering a full signoff.

Do not use recheck for a fresh open-ended review — that is signoff's job. Also avoid it when no findings exist on the record, since an empty checklist against an open card is treated as a record gap requiring the original verdict, not a clean slate.