Empirical Validation

To require empirical proof, enforce a validation protocol that mandates documented evidence before task completion. You must capture screenshots, command outputs, or query results and append them to a state journal file to verify changes.

Validation evidence varies by change type: UI changes require screenshots, API endpoints require command responses, build updates require successful test output, data edits require query results, and file operations require listing or content verification.

Document verification evidence by running the validation workflow and appending captured outputs directly to a state journal file. This establishes a chronological record of empirical proof, satisfying quality assurance requirements for task completion.

Empirical validation works for both frontend and backend updates. It enforces screenshots showing expected visual states for UI changes and commands showing correct responses for API endpoints, ensuring comprehensive coverage across your stack.

Use enforced validation protocols when completing changes across UI, API, build, data, or file operations to mitigate risk. It prevents marking tasks complete without empirical proof, ensuring every modification has documented evidence.