Separate file subject and receipt actor
Synthetic file F7 is S2’s desk request, but index row links S1. Receipt A7 was actually made by S1. Local policy permits correcting the subject index after source F7 is checked, but acknowledgements remain with their actual actor. S2 has not acknowledged.
| Record | Observed | Corrected disposition |
|---|---|---|
| F7 subject | S2 in source, S1 in index | Index→S2 |
| A7 actor | S1 | Retain S1 history |
| S2 acknowledgement | Absent | Request separately |
Correct the association with a trail
- Verify F7 source subject
- Correct index with old/new IDs
- Retain A7’s actual actor
- Request S2 acknowledgement
If the source subject is uncertain, hold the association correction.
After index correction, how many S2 acknowledgements are established?
Show the worked answer
Zero. A7 remains S1’s event; correcting a subject field does not create an S2 action.
Request the right person’s acknowledgement
| Case | Action or result | Evidence boundary |
|---|---|---|
| Relabel A7 actor as S2 | Reject | Would rewrite actual actor |
| Correct F7 index only | Proceed with source evidence | S2 acknowledgement remains open |
Link the correction event, original source and new S2 request. Keep the mistakenly received item visible for follow-up rather than hiding the mistake.