Track request and acceptance as separate events
Synthetic task T-E has three hours remaining. Ren asks Sol to take it under request HO-E, but Sol has not accepted. The supplied team rule keeps Ren accountable until an explicit acceptance names the remaining task and slot. Sol’s receipt of a message is not acceptance.
| Event | Evidence | Owner state |
|---|---|---|
| HO-E sent | T-E; 3 hours; proposed tomorrow | Ren remains owner |
| Message received | Sol read receipt | No ownership change |
| Required acceptance AC-E; not yet recorded | Must name T-E / 3 hours tomorrow | Ren remains owner until acceptance |
Complete the handover on acceptance
- List three hours and current checkpoint
- Send proposed HO-E
- Keep Ren’s task visible
- Record Sol’s explicit AC-E
- Move ownership with the accepted slot
If acceptance omits the task identity or remaining scope, clarify it before moving ownership.
Before AC-E, Ren owns T-E. After AC-E, Sol owns the same task with three hours remaining. Do not create another three-hour task and leave the original active, which would duplicate demand.
Sol has read HO-E but AC-E is absent. Who must track T-E?
Show the worked answer
Ren remains the current owner until the explicit acceptance exists.