aylee Handoff
The linked WORKSTREAM.md must remain independently resumable. A handoff is optional acceleration for a specific boundary.
- Read
docs/state-protocol.md,library/templates/handoff.md, the canonical workstream, and its referenced artifacts. Reconcile stale facts in the workstream before composing the handoff. - Copy the template exactly. Preserve its required frontmatter names:
schema_version,handoff_id,workstream_id,base_revision,created_at,created_by_runtime, andtarget. - Create a uniquely named file under
state/handoffs/<workstream-id>/using UTC time and ahandoff-<uuid>ID. - Preserve the template's section names and order: Boundary, Base Snapshot, Boundary Delta, Artifact References, Risks and Approvals, Suggested Skills, and Receiver First Action. Base Snapshot must name the workspace-relative workstream path, literal
workstream_id, and exactbase_revision. - Keep Boundary Delta limited to transfer-specific context. Reference durable artifacts instead of copying current truth, open decisions, verification, or the workstream's next action. Exclude transcripts, hidden prompts, credentials, personal integration URLs, hostnames, and absolute paths.
- Never mutate the handoff into a receipt. A receiving agent may create a separate
consume-handoffreceipt.
If there is no real boundary, update the workstream and decline to create handoff theater.