Rules decide routing, priority, due targets, urgency approval and escalation for new refill requests. A release contains the complete reviewed decision and its reference revisions. An existing admitted cycle keeps the obligation recorded when it was requested.
Save the intended rule set
In Rules and releases, check rules in their decision order and the Default outcome used when none match. Check queue choices against the loop's permitted queues. Include the working calendar and supported escalation policies where applicable.
Describe conditions in specific business terms using the supported fields. When a proposal is produced, read its typed condition and restatement. Adoption changes the draft; it does not prove or release it. A proposal with a plausible explanation still needs independent expected outcomes.
Supply examples that could disprove the rule
Under Examples the release must decide as you expect, include each rule, the default, an urgent case and invalid or missing input. Where two rules can both match, include an overlap case that shows which should decide. Choose the expected result and rule from the intended business policy before viewing the proof.
For a loop supplying ten seals to Press 2, check the routine default, an urgent request that needs supervisor approval, and a matching special rule with its intended queue. Use actual saved loop codes and queues. Also test missing or invalid input through the provided controls. These cases should expose a wrong route, not merely repeat a successful normal example.
Prove the saved revision
Before proof, have the owner enable the intended supplying queues on Stores queues. The default queue must already be enabled for release qualification. Choose Save draft, then Prove the saved draft. Read failures, examples, every input of every loop, timing evidence and changes against the active release. The candidate is bound to the saved draft and configuration. Unsaved changes are not included, and later changes, including queue enablement, stale it.
A reviewer chooses Release rules after current review and recent verification. If they contributed and the site requires independence, another reviewer must activate. If self-review is allowed, the contributor must state what they checked in the recorded statement.
Automation-managed candidates additionally require current independently reviewed expectations and release evidence. Those checks are not waived by the local review policy. Direct rollback can be refused in favour of a reviewed candidate.
For ordinary rollback, choose a release that was active before, give the reason and pass current qualification and plan checks. The rollback changes future admission; it does not rewrite open or terminal cycles. Communicate the effective release and changed decisions to supervisors and stores.