paper-pilot-before-batch

Batch processing validation requires running a pilot of 3–5 samples to confirm logic before full execution. This workflow control mechanism prevents cascading errors by requiring explicit user confirmation based on the pilot results.

Sample testing is necessary for batch operations involving 30 or more targets, or when the scope is unknown. It applies to batch tasks across files, paragraphs, or citations to ensure quality assurance before full execution.

If the pilot run produces incorrect results, you can use the fallback to re-run the batch task with adjusted logic. This workflow control requires explicit user confirmation before proceeding to the full batch.

Prevent cascading errors when updating references by running a 3–5 item pilot from the target batch. Present the before/after results for explicit user confirmation before proceeding to the full batch update.

Batch validation applies when the scope is unknown or a user requests processing an entire directory. The workflow triggers a 3–5 sample pilot run to validate logic before full execution across the entire directory.

Pilot sampling requires a sample-run capability and explicit user confirmation, adding a manual checkpoint to the workflow. If the 3–5 samples are not representative, the full batch may still encounter unvalidated edge cases.