Batch instruction revision handover — working review
WORKING NOTES — review decisions belong in your controlled records.
Guide: https://seal.run/blueprints/guides/batch-instruction-version-handover

Use one instruction transition. Reconcile prepared, running and newly created batches against the implementation plan before relying on the new default.

1. Transition decision and time basis
Name the instruction revisions, changed tasks, implementation-plan revision and transition time with timezone. State the authorized treatment of running, prepared and newly created work.
Your evidence and observations:
[Not recorded]

2. Affected batches and actual references
Record the population query and time. For every batch, identify its current execution state, exact assigned instruction reference and whether generated content was copied from an earlier revision. Include unstarted work.
Your evidence and observations:
[Not recorded]

3. Prepared-work comparison
For each batch requiring reassignment, compare the instruction reference, executable steps, assigned verifiers and prerequisites with the changed requirement. Name every item that must be updated or regenerated and the evidence that can be retained.
Your evidence and observations:
[Not recorded]

4. Fresh readiness check before start
Recheck whether the batch started while the handover was being prepared. Identify work created since the first population extract. Verify reference behavior and copied content together; record any reassessment when execution state changed.
Your evidence and observations:
[Not recorded]

5. Authorized treatment and preserved history
Record the decision for each batch, the responsible owner and remaining actions. Link the prior preparation and any superseding work. For a batch permitted to continue on the older revision, retain the actual instruction and transition decision.
Your evidence and observations:
[Not recorded]

EVIDENCE NEEDED TO FINISH
Each affected batch has a supported treatment, consistent executable content and an identifiable historical instruction basis. Newly created work and batches that changed state during the transition are reconciled. A revision-5 label with revision-4 steps remains unresolved.