As Reviewer, control which configuration becomes active. Inspect the exact saved candidate, independent expectations, review state and proof before activation.
Inspect the intended requirement
Open Configuration and its candidate proof. Check each family, component choice, quantity and evidence policy. Review cases for all rule paths, alternatives, omitted slots and invalid inputs. A passing result with incomplete coverage or unreviewed examples cannot pass the full gate.
The native example-review action can be performed by an Author or Reviewer. Independent expectations mean that intended answers must come from the business requirement rather than calculated output. Do not claim that the ordinary native workflow always enforces two different people merely because roles have different names. Additional enrolled review controls can impose further restrictions.
Activate the exact proof
Use the latest passing proof for the candidate. Complete recent Accounts authentication when requested. Activation rechecks the candidate, current examples and reviews, runtime and active-release state. A stale page cannot silently replace somebody else's activation.
After activation, check the current active release. Unstarted kits can be refreshed to the new configuration, while started work retains its frozen plan. Discuss the operational effect with the Supervisor before changing a configuration during a shift.
Stop or recover a release
Withdrawal requires a reason and holds affected open work. Rollback creates a new revision and candidate from earlier content and requires fresh verification; it is not an instant reversal of history. Some enrolled workflows require a new reviewed candidate instead of the ordinary rollback action.
Read proof and activation and source and release changes. The Supervisor still decides physical disposition of kits and handles station exceptions.