beads-trim-memories
Trimming beads memories
bd prime injects every persistent memory into every session. That makes the memory set a
tax that each session pays in context before it has done anything, and prime's caps only make
it worse: when a cap is set, memories are cut alphabetically, so what survives has nothing to
do with what matters. Memories are written in the moment, about the work of that moment, and
nobody comes back to ask whether they earned their place. This skill is that coming back.
The test for a memory that stays in prime is: would a fresh agent, starting on an arbitrary bead in this repo, do something wrong without it? If the honest answer is "only when working on X", the memory belongs with X, not in every session. If the answer is "no, that shipped", it belongs nowhere. If the answer is "only if that bug happens again", the memory is doing a tool's job: a lint rule, test, CI check, type or script should catch it, not an agent reading prime.
What earns a place in prime is the project's norms and direction: conventions and why they hold, architectural decisions and the trade-offs behind them, things deliberately ruled out, contracts between parts of the system that the code doesn't make obvious, and how the user wants sessions run. One-off bugs, gotchas and tool quirks don't, however painful they were.