“We don't have any formal mechanism for this. No member of the team has a full mental model of Claude Code in their head, nor do we think anyone needs to. Rather, when anyone wants to learn about a piece of the codebase, they ask Claude to generate an explainer about that exact slice.”

A different memory answer from decision logs: don't persist the why, regenerate the what on demand. The tradeoff is that an explainer describes the code as it is now, not why it became so. Pairs with the same post's 'Changing course' point, where prior decisions are surfaced by people in open Slack threads rather than by any store.