acceptance-validation

Verify acceptance criteria by mapping each story requirement to specific file:line references using git diff and staging-doc scoping. The validator runs read-only commands to produce evidence-backed validation reports with COMPLETE or INCOMPLETE verdicts.

Evidence verification confirms every acceptance criterion was actually implemented with fresh, checkable outputs. It records verification command exit codes and maps criteria to specific code references, preventing incomplete or incorrect story implementations from passing the quality gate.

Trace acceptance criteria by using git diff and staging-doc references for layered scoping to narrow the search area. This maps each criterion to exact file:line locations, falling back to a full codebase scan if the scoped search lacks sufficient evidence.

Acceptance validation handles missing evidence by producing actionable failure guidance. When verification commands cannot confirm a criterion, the report provides specific fail and unable-to-verify instructions to resolve the gap before user acceptance.

Run acceptance validation after story integration passes and before user acceptance. It serves as an SDLC quality gate for architects to confirm story completeness, ensuring every acceptance criterion has fresh evidence and correct code implementation.

Validation reports explicitly handle incomplete implementations by detailing which acceptance criteria failed verification. The report maps evidence gaps, records command outputs, and provides actionable guidance to fix missing or unclear implementation evidence.