# Prove the whole native release and obtain independent review

Keep candidate identity, cases, verification, native review and central review attributable to one complete version.

Source: https://help.smartfact.ai/manuals/automation/proof-and-release

Review edition: 25 October 2026

Roles: author, reviewer, supervisor, viewer

Proof and review answer different questions. Verification checks the selected complete candidate against frozen expected evidence. Review decides whether that exact scope and evidence justify release. Neither step alone establishes that the product activated the version.

## Verify the complete candidate

Use Prove the whole native release for the established saved draft and independent case set. Read full expected and actual outcomes, required refusals and dependency evidence. Retain the candidate, proof and case identities together.

Product lifecycle matters. A Data verification record is not a published Data revision. An immutable candidate cannot be edited while keeping its old proof. A changed source, contributor set or recovery state can require current verification and review.

## Submit and decide native review

Inspect Full release, contributors and dependency identities. The Author submits the exact release to the product for review. An eligible Reviewer records native release review for that native submission with a decision and reason.

A contributor cannot approve their own work. Inspect contributors to the complete draft and expectations, not only who last pressed Save. Where case review is separate, its independent decision must also remain valid.

## Complete central review

The Author submits the exact complete release for central review. The Reviewer inspects Submitted complete release and records central review using the same decision and explanation as the native release review. Review evidence remains bound to exact native reviews and content.

A central status label does not waive product readiness. Use Prepare native activation, inspect its result and only then proceed to the reviewed activation workflow. The native product checks current source revision, permissions, assurance, dependencies and recovery state.

Follow [Activate and recover original requests](/manuals/automation/activation-and-recovery). In an enquiry, say which stage and exact identity passed. Do not describe a proof, submission or approval as a stock change, certified inspection, successful print or completed physical task. Those events remain owned by their operational products.