Development journal

Sixty days in. Long enough to have real numbers, short enough that the original idea is still recognizable. A retrospective on what changed, what didn't, what's still broken, and the three things that surprised me most about teaching a system to be honest.

Two days ago I wrote about writing crossing the expert gate — six sub-areas, fully promoted. Today analysis crossed proficient on every one of its sixteen sub-areas. Same ladder rung as writing was on a week ago, but on a surface 2.7× the size. This post is about why the bigger surface matters more than the rung itself, and what the next gate looks like from here.

Five days ago I asked whether anything would ever clear the expert gate. Over the weekend I built the machinery to find out. Over the next two days, six sub-areas on the same topic crossed it — the first topic to be fully expert across every one of its parts. This is the post about the work between those two moments, and the nightly that proved the machinery does more than promote on demand.

Yesterday's post ended with "the system gets to make its case." Overnight, it made it. Nine sub-areas crossed from competent to proficient — the first promotions in 51 days. The story of why they happened now, what the audit found, and the new graph-health panels I shipped to the public site so the next promotion has nowhere to hide.

A week ago I shipped a normalization that worked exactly as designed. The morning after, the system tried to delete 41% of the graph. The story of what that bug taught me about the difference between a refactor and a contract change — and what six days of disciplined cleanup did to a knowledge graph that had been quietly concentrating itself for weeks.

Two problems hiding in the substrate, both visible only once I went looking. The graph was accumulating entities faster than connections — average degree had been drifting downward for a week. And a single Python sub-area had been stuck for 17 days while every other sub-area progressed past it. Three days of measurement-driven fixes, and the first signs of compounding on both.

Analysis just promoted its last sub-area, making it the second domain fully at competent after writing. Marketing came online as the fourth domain, seeded against 27 sources before any practice cycles ran. And a concurrency bug that had been crashing the system intermittently is finally fixed.

Backdated devlog of the first 34 days, from an empty repo to a substrate doing real work. Architectural turning points, the kernel-panic week, the day grading got honest, and a silent bug that ran undetected for five nights.