session-handofflisted

# Session handoff Most of the state already survives. The spec says what is being built, the ledger says what was decided, `gates.md` says what passed, the commits say what landed, and `git status` says what is half-written. A handoff that restates any of that is a copy that will disagree with the original within a day. So the note holds one thing: **what is only in your head right now.** ## When to write it **At a green commit, not mid-red.** A handoff pointing at a broken working tree forces the next session to reconstruct what was in flight before it can do anything, which is the situation the note was supposed to prevent. Where stopping green is impossible, say so explicitly and in the first line. **Before the context is exhausted, not after.** Once compaction has happened, the details worth recording are the ones already gone. Write it while the run is still holding what it knows. ## What goes in ```markdown # Handoff — <spec or epic id> Written: <ISO> · Branch: <name> · Last commit: <sha> · Tree: clean | dirty ## Wo ich stehe <Which step of the spec, and what state it is in. One paragraph.> ## Was ich zuletzt versucht habe <The last change and what it showed — especially if it did not work. This is the single most valuable line in the document.> ## Aktuelle Hypothese <What you currently believe is true about the problem, and how confident you are.> ## Schon ausgeschlossen <What you tested and ruled out, with what showed it. Without this, the next session repe