Verification Discipline

Task-class-aware verification enforces specific verification rules during code execution by classifying tasks first, then applying tailored checks. It prevents false positives by ensuring each task type meets its exact requirements before completion.

Task-class-aware verification categorizes tasks into classes like feature, bugfix, build_validation, or lint_cleanup, then applies specific verification rules to each. This targeted approach prevents false positives and improves overall code quality.

Fallback verification rules for refactor or infra tasks apply automatically when a task does not match a primary classification. A verification enforcement system triggers default checks, ensuring unclassified tasks still meet baseline quality standards.

Task classification integrates with codegen context to provide detailed verification specifications. This integration allows the enforcement mechanism to use contextual code generation data to determine the exact verification rules required for each task class.

Execution time verification for feature or bugfix tasks is needed when you want to verify code quality before task completion. This approach checks verification rules at execution time, ensuring the specific requirements of the task class are met before finalizing.

Verification enforcement works for lint cleanup and build validation tasks by applying task-class-specific verification rules. The system verifies these tasks based on their classification, ensuring the specific verification requirements for lint and build checks are enforced.