Wrap Up Session

Step 1: Decide whether anything is worth writing down

Review the conversation for learnings that will still matter next month. The default is to write nothing. Documentation that restates the code is worse than no documentation: nobody reads it, and it goes stale the moment the code changes.

Skip it if any of these is true:

• It's discoverable by reading the code, the schema, git history, or config
• A manifest or lockfile already pins it — versions above all
• A linter, type, or test already enforces it
• It's a narrative of what happened this session — what broke, what you tried, which ticket it was
• It's a file or method inventory
• It only mattered to this task

What survives that bar is usually one of two things: a rule this project has settled on, or a fact about the outside world the code can't reveal on sight — how a library actually behaves, an API that contradicts its own docs, a database rule with a surprising edge.

Step 2: Route it