handoverlisted

# Handover Goal: Record task/topic progress in a structured format that allows resuming work across multiple sessions and contexts. The primary reader is the **AI in the next session**, not a human. Optimize for action: classify information by role (constraint / decision / state / task / reference), not by narrative. Markdown body with XML tags for section boundaries — tags make scope explicit; md keeps tables/code/lists cheap. ## Output path Save to the **project root** as `HANDOVER.md`: ``` HANDOVER.md ``` - Single file at the project root (no subdirectory, no slug) - One file per project; overwrite/update in place ## File format ```markdown --- title: <task/topic title> updated: YYYY-MM-DD status: <one-line: where we are + what remains> sot: <paths to canonical sources this handover points at> --- <constraints> Rules that hold regardless of the task. Violating one breaks the system or the SoT. State each as an imperative with the failure mode. </constraints> <decisions> Settled. Do not relitigate. Record the rationale with each decision so the next session does not reopen it. </decisions> <state> What is done and verified (committed, tested, deployed). Facts only. </state> <tasks> Each task is independently actionable and includes its completion check. <task id="<slug>" priority="1"> What to do, with enough context to start without rereading the file. constraint: <pointer into constraints, if the task is near a landmine> verify: <observable condition th