verification

Pre-commit checks enforce verification-before-done discipline by requiring tests, lint, build, and type checks to pass before closing a task. This ensures no development task is marked complete without concrete proof like test logs or diffs.

Evidence-backed completion is a verification process requiring concrete output like logs, diffs, or behavioral checks to justify task closure. It works by enforcing proof documentation and review before any development task is marked complete.

Run a verification pass before closing a task to collect review-ready artifacts for staff engineering sign-off. This process collates concrete evidence such as test logs, build outputs, and behavioral diffs to support the review process.

Yes, evidence-driven completion explicitly applies to pre-commit workflows by running build and type checks before closing a task. It ensures the outputs from these checks are documented as concrete proof for review.

You need concrete output like logs or diffs before finishing a coding task to satisfy verification-before-done discipline. This mechanism enforces evidence-backed completion by ensuring proof is documented and reviewed, preventing unverified task closure.