Source revision changes and configuration activation affect work differently. First establish which changed, which kits have started or completed, and what physical disposition is required.
Review a changed job
A higher source revision is retained as a pending candidate and places the job on hold. Open the job and compare its change details. Identify every started or completed kit needing a physical disposition. Discuss the approved order with the source owner and control the physical kits while the decision is pending.
Record the required dispositions, then activate the new source revision only when all are present. Activation cancels open attempts while retaining evidence, annotates earlier completions as source-revision superseded and prepares fresh plans. Retained kits restart from zero; previous scans do not prove the revised requirements.
If the upload was mistaken, use the rejection path with a reason and the explicit assertion that the previous revision remains authoritative in the factory system. A rejected revision remains recorded and cannot be revived merely by uploading it again. Omission from a later file does not cancel a job.
Review a configuration activation
The Reviewer activates a proved configuration separately from job imports. Unstarted attempts on older configuration can be refreshed and replaced. Started attempts remain pinned to the plan under which they began. A Supervisor's deliberate cancellation is not normally undone by a later activation.
Withdrawal holds open attempts using the withdrawn release. They cannot simply resume that plan. The Supervisor must use the permitted cancellation and replanning path, with a suitable active configuration, while preserving physical disposition and evidence.
Verify the handover
After the change, inspect the job's active source revision and each relevant kit's plan and attempt. Tell Operators which old references or open pages need a fresh view. A historic Verified result is not proof that the new source revision has been checked.
If activation refuses because the source, preview or active configuration changed concurrently, reload and review the current state. Do not repeatedly submit an older decision. When a response is uncertain, settle the original action before another command.
Use proof and activation for configuration review and history and exports to retain both the earlier result and its later annotation.