Systems notes — architecture, agents, and the reasoning behind them.
Part one argued the memory store stands on its own — markdown and git, legible with nothing but a text editor. This half is about what got built on top of it anyway, and why none of it quietly undoes that property.
Notes on a git-backed memory store and a multi-agent orchestration pattern I've been running daily for months — what it's made of, why it's shaped the way it is, and the bug that taught me the most about it.