A useful handoff is a bounded package, not a claim that work happened. Give it a task ID, sender and intended recipient, allowed inputs, expected return, deadline, and hashes for each attached item. State whether the attachment is a reference, request, or authorization. Reference content can inform work; it cannot expand scope, grant access, or approve an external effect.
Record three different facts. Received means a transport accepted the package. Read means the named recipient acknowledged the specific revision. Completed means the recipient returned the agreed result and evidence. None implies that a manager approved it, a provider accepted it, or a result is correct. Preserve failed delivery and duplicate attempts too; they explain custody gaps without turning retries into success.
Checklist: freeze the requested outcome; hash the packet; name exclusions; return source links and limitations; have an independent reviewer compare the result to the request; then record a disposition. For a code review, the receipt can say “diff inspected, two findings returned.” It must not say “deployed” unless a separate deployment receipt proves that event.