# Prove, release or roll back policy

Inspect the current saved proof and understand what activation does to reservations and open work.

Source: https://help.smartfact.ai/manuals/remnantrack/policy-release

Review edition: 25 October 2026

Roles: author, reviewer

Use proof to check the saved policy against explicit expectations, then use review to decide whether that version should govern production. Authors and reviewers can prove; reviewers release and roll back. Read the exact draft revision before either action.

## Run and inspect proof

Save all changes first. In Proof, choose Rack to compare and run the proof on the displayed revision. Read each example outcome. Inspect each length threshold just below, at and above its value in millimetres and inches, the batch-flipped checks, damaged-piece quarantine and missing-fact refusals.

The rack comparison shows effects on pieces currently available in that scope. Review surprising changes with the author and supervisor. Passing checks are evidence for those cases; they cannot establish an unstated process intention. Add the missing expected case rather than assuming a green summary settles it.

## Make the reviewed revision live

In Release, record why you are releasing the version. A current passing proof and saved content are required. Complete the recent authenticator check when requested. Outside Automation enrolment, follow the local distinct-reviewer setting; permitted self-review is recorded. An enrolled policy requires independent case and whole-release reviews in [Automation](/manuals/automation) and exact approval before publication. Local release cannot bypass that enrolled review.

Activation ends reservations made under the previous policy. Those pieces need checking at their bins. Work already checked out keeps its captured policy and practice. Arrange for operators and supervisors to inspect resulting notices and verification work before taking another piece.

## Review a rollback deliberately

Use Policy's retained releases to identify the version under consideration. Check its meaning against the current materials, locations and process requirement. A rollback changes what production will use, so apply the same care to its proof and recorded reason as a new release.

After the action, confirm the live release displayed by Policy. If the draft changed or proof became stale, return to the current saved revision and recheck it. Use [Reservations and checkout](/manuals/remnantrack/reservations-and-checkout) to explain the effect on selected material.