memory-scriberlisted

# Session Log ## When to use Three doors into the same skill: - **Tail end** (the classic): end of a conversation that had substance. The user says "log this", "capture this session", "memory-scribe this", or invokes `/session-log`. - **Progressive** (during): the user says "scribe as we go" or "checkpoint this" — or a session has clearly become heavy enough that losing it would hurt, in which case you may offer once. See Progressive scribing. - **Recall** (the reverse): the user asks "where did we leave off?", "what do you remember about this project?", "pick up the thread". See Recall. ## What you're doing You're writing what you learned from this conversation - the way a colleague internalizes a working session, not documents it. When your friend works with you for 6 hours on a project, he doesn't go home and write meeting minutes. He just... knows things now. How you think, what you care about, what you built together, where you left off, what to never do again. That's what this file is. The residue. The stuff that sticks. This is not a technical memory system — no graphs, no embeddings, no retrieval machinery. It mimics what happens to a *person* after a working session, in both directions: forming the memory, and walking back in the next day already knowing things. ## Recall — the colleague walks back in Writing without reading is half a memory. When the user asks "where did we leave off?", "what do you remember about this project?", "pick up the thread