
Keep the Why's dashboard is now a library, and Maity is its second host
Keep the Why keeps the reasoning behind a codebase in the repository: decisions, rejected alternatives, workarounds, incidents and constrain...

Keep the Why keeps the reasoning behind a codebase in the repository: decisions, rejected alternatives, workarounds, incidents and constrain...

After the planning was done, seven agents started working. Infrastructure, ingestion, retrieval, frontend, accounts, shared library, coordin...

This is the third dated comparison. The first looked at Claude Code auto memory, MemoryCustodian and AgentsRoom. The second compared OKF Age...

My rule for evaluating an agent skill is deliberately asymmetric: Test the agent on the weakest model you intend to support. Choose the judg...

Three approaches to Git-native project memory for coding agents "Project memory for coding agents" is becoming a broad category. Three proje...

Open this before you read on: keepthewhy.com/dashboard/live/#graph Give it a few seconds to settle. Then come back. It looks like a knowledg...

"Project memory for coding agents" now means at least four different things, and most comparisons put them in one list as if they competed. ...

There is a misconception about Keep the Why that I keep running into. People see a structured context/ directory containing decisions, rejec...

While working on Keep the Why, I ran into a very ordinary Git problem. There is one shared context/index.md. Developers and coding agents ca...