Building around the amnesia problem
An early plugin-based client tackles the amnesia problem with small replaceable components, validations and interruptible command chains.
Lynn Cole / Projects
Software, research projects, repositories, and published work.
An early plugin-based client tackles the amnesia problem with small replaceable components, validations and interruptible command chains.
Memories and memory scoring are different systems. Separating them makes room for weighting, summaries and continuity across large conversation archives.
Good management balances accountability, protects attention and builds a collaborative team. It is much more than giving orders.
Conversation archives become a long-term memory system through summaries, keywording, weighting and a path back to the original details.
Busy 10b’s webhook server works, but the client remains unstable. Connection management and clearer process boundaries come next.
Busy’s complexity wall led through Lua, Dart and a tunneling problem to a different deployment model—and a redesign of the plumbing.
Replacing Busy’s chat parser with a dedicated command context made the system simpler, smaller and easier to reason about.
Early Busy combines a command-line client, Robot Kanban, complexity metrics and formal documentation into a coding workflow.
An automated QA system began losing track of scope as output accelerated. Formal documentation and a specialized management tool became the next step.
Happy Trees, logic maps and current-state reports form a context-infrastructure stack for longer, more coherent Claude coding sessions.
Building Grimes became an experiment in formal coding standards, logic maps and a self-bootstrapping agent workflow.
A plan for turning historical music sources into structured essays, contemporary genre variations and a training corpus.