The Next Build Is Already Inside This One

KnowledgeForge could route a reasoning task to the right mode. What it couldn't do was tell me if the output worked for a specific reader.

That gap showed up the first time I tried to use it to evaluate outreach copy. I had a cold email. KF could tell me whether the argument was structured well. It had no mechanism for whether the framing matched the buyer's trait profile. A high-conscientiousness VP of Marketing responds to different signals than a high-openness founder. KF had no model of that.

So I built one. That became COS.

COS ran overnight jobs. Which meant I needed to know what it did while I slept. KF and COS had no shared logging layer, no monitoring, no way to surface failures by morning. That gap became Nightwatch.

Nightwatch coordinated across a single repo. When COS and KF needed to hand work between repos, Nightwatch had no cross-project task model. That gap became Orchestra.

The sequence: KnowledgeForge → COS → Nightwatch → Orchestra. Four builds. Each one was sitting inside the previous one before I started it.

I didn't find any of these by looking at the market. I didn't brainstorm them. I used what I built and ran into the edge where it stopped working. The next problem was always right there.

This is obvious in retrospect, and it's why "what should I build next" is usually the wrong question. The right question is: what does this thing do badly that I need it to do? If you can't answer that, you're not using it enough.

The catch: it only works if you use what you ship. Most side projects get posted to GitHub and left. They never get used hard enough to expose anything. The gap stays invisible. You keep asking what to build next instead of using what you built last.

I'm still inside Orchestra right now. I don't know what it's showing me yet.