# Review proof and activate independently

Approve exact expert definitions and whole plans through distinct decisions.

Source: https://help.smartfact.ai/manuals/checkstation/proof-and-approval

Review edition: 25 October 2026

Roles: author, reviewer

Use proof to check the plan's selected requirements against independently supplied business answers. Use human approval to establish that the exact method and source are appropriate. Neither can replace the other.

## Resolve pending expert definitions

On Plans, inspect Expert approval needed entries. The Reviewer reads the complete proposed definition, supplied expert statement, method identity and exact hash. Check the engineering authority behind each value, including unit, limits, repetition and evidence requirements.

Enter Expert review and reason and use Approve this exact definition only when eligible. The Reviewer must be independent of every plan contributor and have recent Accounts authentication. A person holding both roles remains ineligible if they contributed.

Definition approval creates a new draft revision and invalidates proof. It does not activate a release or automatically add the check to a binding. The Author must ensure the intended approved revision is selected in the complete plan.

## Run and review full proof

Save all intended changes and choose Run proof examples. Inspect each expected selection and refusal against the calculated result. Cover both ordinary and additional requirements, supervision and meaningful invalid contexts.

Resolve differences against the approved method. If an expectation was wrong, correct it transparently; do not copy unexplained output to manufacture a passing result. A changed plan needs a current proof.

## Activate the unchanged plan

The eligible independent Reviewer checks the entire saved draft and proof, enters Review decision and reason and chooses Approve and activate. Current authority, revision, exact proof and active bindings are rechecked. Another active plan with an ambiguous binding is refused rather than selected by convenience.

After success, inspect the retained release and its identities. Tell the Supervisor which unit contexts it covers and whether supervision is mandatory. A release freezes its checks and selection; later edits do not rewrite started attempts.

## Withdraw deliberately

If a release must stop being used, select the exact retained release, inspect its scope and choose Withdraw this release with a reason. Affected work needs operational review and restart handling. Do not clear a hold and continue an attempt whose references are invalid.

For a stale or uncertain approval, refresh or reconcile the original request before another command. Use [failures and release](/manuals/checkstation/failures-and-release) for unit decisions, which require Supervisor authority rather than plan Reviewer authority.