empirical-validation

To require proof for task completion, you need an empirical validation workflow that captures concrete evidence like screenshots, command outputs, or test results before allowing a task to close.

Empirical validation is the process of verifying task completion using concrete evidence such as screenshots, command outputs, or test results, preventing assumptions and guaranteeing changes meet intended outcomes.

You can verify UI changes and API endpoints by enforcing structured validation methods that capture screenshots or command outputs, ensuring you document demonstrable proof of correctness for every modification.

Yes, you can enforce validation across build processes and file operations without external dependencies by applying an evidence-driven workflow that requires command outputs or test results for every operational task.

Development workflows assume completion without proof when they lack empirical validation, which mandates concrete evidence like command outputs or test results to guarantee changes truly meet their intended outcomes.

You should avoid empirical validation only if your task cannot generate concrete evidence like screenshots, command outputs, or test results, as the workflow requires integration with execution and verification workflows to capture proof.