Highly opinionated, based on my personal experience dogfooding my own setup.
Not a prescription. I'm scratching the surface, with a lot left to learn.
In Part 0 I agreed that coding is solved, and that it took four things to get there. None of them guarantees the architecture is right. This post is about that gap. Code quality is a convergent problem now — you can push it toward "good" mechanically. Whether the design is right is a different kind of problem, and I have no gate for it. That's the part nothing gates, the part you find by use rather than by spec. And I'll get to how even that is sliding away from me.
The convergence mechanism
A deterministic gate is a check that gives the same verdict every time, no matter which model ran or what context was loaded. Run it on every commit and the output can only move one way: toward whatever the gate calls "good." That's convergence. Tech debt piles up when nothing pushes back. A gate pushes back every single time.
