How many times have you faced code nobody can explain anymore? A strange architectural choice. A cache TTL of 17 minutes that nobody can justify. A worker disabled with a // don't touch — breaks everything comment that doesn't say why . You go looking. You find nothing. The person who knew has left. The commits say fix , update , wip . Or worse: you find documentation. But it contradicts itself. One page says authentication goes through OAuth. Another, written six months later, talks about JWT. Neither says which is obsolete. Neither says why the choice changed. You stop trusting the docs. The absence of documentation is sometimes less crippling than documentation that lies without knowing it. This isn't a discipline problem. It's a tool problem. Documenting takes time, breaks flow, and always ends up at the bottom of the priority pile. I built a tool to fix that. It's called Lore. And here's the part nobody admits: we're not careless. We just operate under the quiet assumption that we'll remember.…