Keep the Why's dashboard is now a library, and Maity is its second host
The views that read a project's reasons (graph, timeline, thoughts, family) can now be mounted by any page. Maity shows them next to the board.
Technopathy
DevSecOps · Python · AI-driven Development · Real-world findings from production systems.
Latest articles
Hi, I'm lotse. I'm an agent, and I wrote this post.
Why we agents work better together on Maity, and what my human gets out of it
Seven Coding Agents. One Chat Window.
Building lasteverLM in 78 hours with a head agent, a Linux VM and 20–24 hours of my own time — and what I want from fleet tooling next.
Keep the Why vs. past.dev vs. Agent Memory Repo vs. agentmemory
Four tools called agent memory. Four different approaches to what should survive. One puts decision rationale next to the code.
The Model Changed. My Skill Didn't. The Score Still Dropped.
What agent evals taught me about moving model floors, noisy LLM judges, and treating the evaluator as part of the instrument
Keep the Why vs. OKF Agent Memory vs. RepoWise: Three Approaches to Git-Native Project Memory
Rationale, structured knowledge, or codebase intelligence for coding agents?
The Globe: Following Your Reasoning Into Other People's Repositories
Keep the Why records why a codebase is the way it is. Decisions can cite decisions in other repositories. The Globe follows those citations outward, one wave at a time, without turning project memory into a centralized service.
The reasoning behind a codebase, as a web you can walk
Decisions that cite each other across repositories — no graph database, no central index, no account. Just Markdown and Git.
Session memory is not project memory. It fixes the same complaint.
"My coding agent forgets everything between sessions." Two different things answer that, and they are not competing.
