Building-in-Public

Weekend 2: when Plan A fails, Plan B works in ten minutes, and things get recursive. In the previous article, I got the foundations working: site live, domains sorted, corpus structure in place. (If you’re new here, Article 1 explains why I’m building this.) Weekend 2 was supposed to be the payoff: make the corpus queryable, connect it to Claude via MCP, and finally stop copy-pasting context into every conversation. The plan was Khoj. The plan didn’t survive contact with reality. ...

Weekend 1 of building a personal knowledge corpus: what worked, what didn’t, and what I learned about AI-proofing a website. In the previous article, I outlined the problem: context trapped in chat sessions, knowledge scattered across tools, published work invisible to AI agents because it lives in walled gardens. The thesis was files plus semantic search plus MCP integration equals thinking that persists. The plan was three weekends of building. Weekend 1 was about foundations: get a site live, get domains sorted, get email working, create the corpus structure. The unsexy infrastructure that everything else depends on. Here’s what actually happened. ...

Building a corpus that remembers Where does your thinking go to die? Mine dies in several places, and I suspect yours does too. Chat sessions with Claude that end and take context with them. Bookmarked articles I’ll “read later” (I won’t, and we both know it). Screenshots of whiteboards rotting in my camera roll because I told myself I’d transcribe them “when I have time.” Notes emailed to myself, now buried under seventeen newsletters I also meant to read. PDFs downloaded with great intentions, never opened again. The article I know I read about that exact topic, somewhere, unfindable when I actually need it. ...