Check task identity beyond similar wording
In the synthetic inbox, R01 and R02 both request the same export of dataset SNAP-A with the same fields and recipient. R03 asks for SNAP-B and is separate. The local rule allows duplicate request references to link one task, while preserving each sender’s context.
| Request | Input / output identity | Execution link |
|---|---|---|
| R01 | SNAP-A / fields F / recipient Jo | TASK-A |
| R02 | SNAP-A / fields F / recipient Jo | Same TASK-A |
| R03 | SNAP-B / fields F / recipient Jo | TASK-B |
Preserve both request histories under one task
- Compare input snapshot
- Compare fields and destination
- Link R01 and R02 to TASK-A
- Retain R03 as TASK-B
A different data snapshot or recipient remains a separate task until the owner explicitly agrees a combined output.
Three requests produce two execution tasks. Keep the duplicate links rather than deleting R02, so the team can answer both senders and trace why only one export ran.
If R02 later asks for an extra field, may TASK-A silently change for both senders?
Show the worked answer
No. Review the changed scope with the task owner; split R02 if its intended output no longer matches R01.