Empirical Validation

Empirical validation enforces demonstrable evidence for task completion by requiring concrete proof like UI screenshots, command outputs, or build success logs before changes are marked complete. This prevents unverified modifications from passing execution workflows.

Validation methods require running commands to show correct JSON responses for API changes, and capturing screenshots from browser tools for UI changes. These empirical proofs verify successful execution before task completion is accepted.

Verifying code quality requires integrating empirical validation into execution workflows to mandate concrete evidence for all changes. This prevents unverified modifications by blocking task completion until build logs, command outputs, or data query results are provided.

Command outputs and build success logs are supported empirical validation methods used as demonstrable evidence for task completion. Providing these logs verifies changes and prevents unverified modifications from passing execution workflows.

Empirical validation limitations include requiring external execution tools like run command or browser agents to generate evidence, meaning it cannot verify changes without supporting infrastructure to produce screenshots, logs, or query results.