Record repair version and customer version
Synthetic repair is verified for v6. Customer C-411 still runs v5; C-412 is confirmed on v6 and passes the original task; C-413 has unknown active version. A repair in v6 supports neither recovery on v5 nor deployment to the unknown customer. The fixture closes only the supported C-412 outcome. Customer version evidence is collected through the actual agreed support process; no automatic upgrade capability is assumed.
| Customer | Active version | Original-task check | Resolution decision |
|---|---|---|---|
| C-411 | v5 | No v5 repair evidence | Not established |
| C-412 | v6 confirmed | Pass | Supported recovery |
| C-413 | Unknown | Not matched | Version and outcome review |
Apply repair evidence to a matched customer baseline
- Read verified repair build
- Confirm customer active build
- Check original task on that build
- Set individual supported resolution
A planned upgrade date is not proof that the customer now runs the repaired version.
How many customer outcomes have supported recovery?
Show the worked answer
One: C-412. C-411’s v5 and C-413’s unknown build cannot inherit the v6 verification.
Retain active-build evidence with the customer's task check. A planned deployment cannot replace confirmation of the version actually in use.