Skip to main content
If you’ve never been exposed to software development, you may not be familiar with the concept of a change log. It’s simply a running record of what changed in a product, when, and why. Every update gets documented. Users always know what’s new, what’s different, and what to revisit. I treat this documentation site the same way a product manager treats an app. The pages are the product. They get built incrementally, iterated on over time, and improved based on feedback and clearer thinking. That framing comes directly from my background in knowledge management and product development, and it shapes how this entire site is structured – the organization, the navigation, the use of living documents, and yes, the change log. The articles here are designed to be evergreen – useful years from now, not just today. But evergreen doesn’t mean fixed. Ideas develop. Arguments sharpen. Connections surface that weren’t visible the first time through. Conversations with readers reveal gaps in how I’m communicating something. And the thinking tools this system is built around – Notion, Obsidian, AI – are themselves evolving rapidly, which means the practical implementations documented here will evolve too. The theoretical foundations of each collection – the what and the why – will remain consistent. The how may change as the tools do. This site is also simply a work in progress. I am my own bottleneck – there is significantly more inside my head than is currently on these pages, and getting it out takes time. This change log tracks what changed, when, and why – and serves as a record of the site taking shape over time. If any of this way of thinking is new to you – treating knowledge like a product, building in public, iterating openly – that’s intentional. One of the goals of this site is to expose readers to ways of thinking they may not have encountered before. You don’t need a background in tech or philosophy to follow along. You just need to be willing to think broadly. The change log is a small but concrete example of what that looks like in practice.
Last update: 2026.03.05