Use an evidence-backed affected set
Synthetic T-22 concerns report rows A, B and C. A is demonstrably missing from the customer file, B is present and C has not been examined. The affected set contains A; C is unknown, not confirmed healthy or faulty. The fixture permits a targeted repair only for proven affected rows and keeps unknown coverage as a separate investigation item. A complaint saying “everything is wrong” is retained as a report, not converted into three verified failures.
| Row | Observed evidence | Classification | Scope action |
|---|---|---|---|
| A | Absent from supplied file | Affected | Include in repair candidate list |
| B | Present with agreed fields | Tested unaffected | Exclude from this repair |
| C | Not examined | Unknown | Keep coverage check open |
Expand scope only when evidence supports it
- Record the reported scope
- Inspect each available example
- Separate affected from unknown
- Update repair scope after further checks
An unavailable file does not establish that every row failed; record the coverage gap.
Can A and C both be reported as verified affected rows now?
Show the worked answer
No. Only A is verified affected. C still needs inspection, so the verified affected count is one and the unknown count is one.
Keep unknown records in the coverage check. Expand the repair list only when new evidence establishes their affected state.