Private Tools Don't Export
Three years of private notes are harder to explain than I expected. What writing the README taught me about whether the compression was real.
Someone asked me to summarize KnowledgeForge in an email. My reply was better than the README.
That’s the problem. KnowledgeForge is a reasoning harness for AI coding assistants. It started in 2023 as a stack of instruction files I kept for myself: patterns I noticed, things I wanted the model to carry between sessions. By late 2025 it had 43 modules.
Forty-three modules is not a framework. It’s a documentation project.
I ran a Pareto pass: which modules produced measurable results in daily work, which were overhead for edge cases that never happened twice. Nine survived. The other 34 existed because I was anxious about coverage, not because they paid for themselves.
Nine modes: Builder, Critic, Debugger, Strategist, Expert, Synthesizer, Calibrator, Coordinator, Navigator. Each one is for a different type of failure. Debugging routes differently than reviewing. Reviewing routes differently than deciding between options. The compression was real.
The README wasn’t.
I open-sourced KnowledgeForge two weeks ago. First real test: write a README for someone who doesn’t already know what it is. Someone smart read the old one and couldn’t make sense of it. She asked me to summarize it in an email. I wrote three paragraphs. They were better than anything in the file.
That’s the thing with tools you build for yourself. They’re calibrated to the context in your head. Going public doesn’t mean publishing the files. It means explaining what you already know.
The best explanation I’ve written of KnowledgeForge is the email I sent her. Not the README. I rewrote it today.
Repo: github.com/internexio/knowledgeforge. Read it cold and tell me exactly where you got lost. That’s the test I’m still trying to pass.