Use verification to compare a frozen procedure with independently supplied expectations. Have the complete saved draft, current examples and intended release identity ready. The Author prepares the candidate; the Reviewer controls publication and family assignment.
Lock and inspect the proof
- In the procedure, enter examples from the intended method. Changing or retiring an existing example needs a reason. Keep a case that must block for missing or invalid input.
- Exercise each optional slot both selected and omitted. Cover exclusion groups with the intended ready route or expected conflict. Add boundaries and changed-source situations relevant to the business.
- Choose Lock revision N and verify. Check that N is the revision intended for review.
- Read all expected-versus-actual differences and coverage. Passing examples with missing required coverage are insufficient.
- Correct the procedure or expectation only after establishing which disagrees with the approved method. Save, lock and verify again as needed.
The candidate stays frozen even if someone continues editing the draft. A later example edit or runtime change can make an existing proof stale. The displayed latest proof is the one relevant to publication.
Publish the intended release
The Reviewer opens the exact proof, checks the method and confirms that its evidence is complete. Use the publication form only when the latest proof passed. Check the release key already retained in the candidate and complete recent Accounts authentication when requested. The Author supplies that key in the draft definition before the candidate is locked.
If the native form permits self-approval, it requires and retains a reason when the publisher authored or locked the candidate. State the actual review arrangement honestly. A policy requiring a different reviewer must be satisfied by another eligible person.
After publication, check the release's state, author, publisher and recorded reason. The publication checkbox Use it for new [family] ([kind]) travellers can assign it immediately. If it was left unassigned, use Releases to assign it later when intended for future issuance. Tell the Supervisor which release is now assigned.
Handle a changed review
A refusal because the proof, examples, runtime or release key changed means the old page cannot authorise the action. Refresh and inspect current records. Do not reuse a different candidate simply because its title is similar. Concurrent publication can leave one successful release and one refusal; inspect Releases before submitting anything again.
Continue with release changes when stopping future use or withdrawing unsafe instructions.