If AI Writes Your Code, Should the Session Be Part of the Commit?

There's a thread on Hacker News right now asking: if AI writes code, should the AI session log be committed alongside the code? The answers reveal something interesting: the developers who are most productive with AI have already solved this. Not by logging sessions — but by building a different kind of artifact before the session even starts. Here's what they do, and why it matters more than you think. The Real Problem: Context Collapse When an AI writes code, it's operating from context: your description, your constraints, your decisions. That context lives in the session. The session ends. The code remains — but the why behind it evaporates. This is context collapse. And it's why: Future you (or a new AI session) re-discovers the same wrong paths Code reviews are harder because the reasoning is gone Bugs get re-introduced because the original tradeoff is invisible The session log would help. But it's the wrong artifact. What Actually Works: The Plan Before the Code The most upvoted