Handovers

Record scope, version, sources, unknowns and the next responsible role. Preparing a packet is not proof it was received. A message that left the sender is not the same as work the next role has accepted.

What a compact packet holds

• An identifier and a version
• The objective, in one or two sentences
• The scope a person actually approved, with a reference to that decision
• Sources, and how fresh they are
• What is already done
• What is unknown
• The next responsible role
• The acknowledgement that is needed
• The condition that must stop the work

Four states that are not interchangeable

• Prepared

  The packet has been written. The sender still holds it.

• Delivered

  It was passed on. That shows transport, not understanding or acceptance.

• Received

  The next role names the version, restates the permitted next step, and flags missing context.

• Accepted

  The next role takes responsibility for the approved scope only. Unclear authority goes back to the owner.

Close only the part the record supports. A missing receipt, a changed version, or unclear authority stays blocked for the owner. Keep the failed attempt visible. This lesson does not claim a handover was tested in operation.