Verification compares a frozen candidate with intended kit requirements. Have the saved draft, independently written examples and the proposed operational change ready. Authors prepare drafts and candidates; Reviewers activate, withdraw or perform the permitted rollback path.
Review examples and coverage
Save each example with its full expected outcome. Changing an existing expectation needs a reason. Use Mark reviewed for the exact version after checking it; saving or verifying does not mark it reviewed automatically. In the ordinary native workflow, this review can be performed by an Author or Reviewer and is not by itself proof of a different human actor.
Create a candidate from the exact saved revision and choose Verify. Inspect all differences and coverage. The full gate requires at least five examples per family, matching and nonmatching rules, included and omitted omittable slots, alternatives, required-field failures and necessary lookup-miss cases. All examples must pass and be reviewed.
If a difference appears, establish the correct business answer first. Change a faulty expectation only with an honest reason. Do not train the expected result from unexplained calculated output.
Activate after checking impact
The Reviewer opens the latest passing proof and checks the candidate, current examples and runtime. Use the activation control after recent Accounts authentication. Activation checks that the active release is still the one the page showed; a competing activation or changed proof can refuse the old page.
After success, inspect the active release. Unstarted attempts on an older release are refreshed through plan preparation; started attempts keep their frozen plan. Tell the Supervisor which jobs or stations need a fresh view.
Withdraw or roll back deliberately
Withdraw with a reason if the release must stop being used. Open work on that release is held, retaining evidence. Do not clear the hold and continue under withdrawn requirements.
The ordinary rollback operation copies earlier released content into a new draft revision and candidate. Verify it afresh before activation. Where an enrolled workflow refuses ordinary rollback, prepare the required new reviewed candidate instead. Historic records are never edited into the replacement release.
If a request is refused as stale, reload and inspect current candidate and active state before retrying. If its response is uncertain, settle the original action first. Use source and release changes to coordinate the physical impact.