The Folder Is the Memory

Anyone building with AI hits the same wall: the session ends, and everything it knew ends with it. Next week you’re scrolling through old conversations trying to remember what was decided, what was deployed, what was still open. The work is on disk; the understanding is gone.

The fix is old-fashioned. Make the project folder the memory, not the chat.

Every project I run carries one file — call it STATUS — with three parts:

• Current state. What’s live, where it runs, what works. One paragraph, always current.
• A dated log. What each session did, newest first. Not prose — facts. Built X, deployed Y, verified Z.
• Open threads. What’s unfinished, what’s deferred, and why.

Then one rule, enforced every session: read it first, update it before ending. The session starts by catching up from the file, and finishes by writing back what changed. Decisions get recorded as they happen, not saved up for the end — so a session that dies mid-way loses nothing.

This sounds like bureaucracy. It’s the opposite. The brief takes two minutes to read and replaces the twenty minutes of archaeology you’d otherwise do — or worse, the rework from getting it wrong.

And it future-proofs you. Chats are locked to a tool. A plain text file in the project folder works with any AI, any assistant, any colleague, any future you.

The chat is the workspace. The folder is the memory. Don’t confuse the two.