Step 1
Revise the URS with a diff
Update the requirements and Eventt AI shows a side-by-side diff of what changed against the approved baseline. You review and approve the revised requirement set before any re-testing begins.
Step 2
Regenerate only the affected scripts
Lumen identifies the test scripts tied to the changed requirements and regenerates only those, leaving unaffected scripts and their signed evidence untouched. Each regenerated step keeps its citation to the revised requirement.
Step 3
Re-execute the delta
The AI agent re-executes the affected scripts against the changed system and captures fresh time-stamped evidence. Defects raised during re-execution follow the same structured lifecycle as the original campaign.
Step 4
Update traceability, tagged to the ticket
The traceability matrix updates to reflect the re-validated scope, and every activity is tagged to your external change management ticket. The record shows what changed, what was re-tested, and why the remainder was unaffected.
