irwebtools validation
When to use
Use when the task matches: validation, product acceptance, preview review.
Purpose
Record Product acceptance or rejection of demonstrated behavior.
Inputs
- Runnable POC
- Acceptance criteria
- UX flow
Process
- Walk acceptance criteria with Product using the POC.
- Record who reviewed which revision and when.
- Separate Product validation from engineering verification.
- Send rejected behavior back to definition or UX as needed.
Outputs
- Validation record
- Accepted criteria
- Rejected feedback
- Revision requests
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not treat PREVIEW_READY as production release.
- Do not skip Product review by substituting automated tests.
- Do not claim acceptance without named reviewer evidence.