Systems That Teach Themselves

There's a thread running between building a personal knowledge system and adopting a compound engineering workflow — both are bets on the same idea: that the real value of doing something isn't the output, it's the residue it leaves behind for next time.

In the Obsidian system, every brain dump gets processed, connected, and surfaced later in ways you didn't plan for. In the compound engineering workflow, every build session ends with a deliberate capture step — structured documents that make the next session smarter. The mechanism is different, but the orientation is identical: stop treating work as disposable. Start treating it as material.

What makes both feel different from typical productivity advice is that neither relies on discipline to maintain itself. The Obsidian pipeline offloads the organizational burden to Claude Code. The compound engineering plugin gives the capture step a name and a place in the workflow. In both cases, the system does the remembering — you just have to show up and do the work.