handoff
Handoff
Handoff preserves enough exact state for work to continue safely across a boundary. It owns one revision-bound Handoff result and its acceptance evidence. It does not perform the continued work or Review the result.
Join the active 'Workflow' context when one exists. The outgoing owner remains responsible until an identifiable successor accepts the exact transfer. A session or operating-context change may preserve the same owner without transferring Responsibility.
Process
1. Bind the work that must survive
Identify the exact Outcome or Ticket, current canonical state and revision, outgoing owner, parent owner, accepted Responsibility, scoped Authority, rationale, Evidence references, uncertainty, dependencies, Continuation, next frontier, and Workflow/caller return route. Read authoritative records before the conversation summary; preserve original wording where later correction may depend on it. Mark facts, accepted decisions, assumptions, and unknowns distinctly.
Bind mutable evidence, approvals, claims, Specifications, results, and records to their exact revisions. Treat a delivered artifact, stale prompt, summary, schedule, service acknowledgment, or claim as evidence only for its own seam. None proves acceptance, ownership transfer, or parent completion.
When no active Workflow context exists, bind only the supplied canonical sources and name the caller as the Workflow/caller return route. If a material identity, Responsibility, Authority, or source revision is missing, preserve the available state and return the smallest owned gap instead of inventing it.
Done when: every field named in this step is either bound and classified or recorded as a material gap. Preserve the available state; for each gap, name its owner, unblock condition, and resumption action.