'git diff' My Brain: Working Memory for Claude Code

I keep my whole working memory in a folder of markdown files: everyone I work with, every project, every decision I don't want to re-litigate twice. Claude Code writes to it on a schedule, and every morning I review what it wrote as a `git diff`.

Three months in, I want to show you the actual folder. What's in it, the two routines that maintain it, and the handful of ways it quietly corrupted itself before I worked out the rules. My favourite: it merged two people into one person, and the diff looked completely normal.

Mostly live in a terminal, no slides if I can help it, and I'd rather spend half the time on your questions. You don't need to write code for this to be useful. It's a folder with a `.claude/` in it. That's the whole trick.

Agenda:
6:00 pm: Arrival/Networking
6:15 pm: Announcements and Ice Breakers
6:30 pm: Presentation
7:30 pm: End of Meeting/Networking

Pizza will be provided, and drinks are available for purchase from Red Cedar Spirits.