Trust

There’s a question every solo builder answers eventually, usually by getting it wrong once: Which answers am I allowed to act on without checking? Not “which tasks can AI do” — that’s a capability question and the answers change every few months. This is a sorting question, and it doesn’t change with the model. It changes with the task. The framework — and why it isn’t the article Let me be honest up front, because we do this on every post: the grading framework itself is not new, and it is not ours. Regulators, enterprise security teams, and academic groups have all published versions of it. Microsoft’s agentic-risk guidance says require approval for high-risk or irreversible actions. A recent DeepMind paper on delegation names reversibility as the axis that decides how much authority you can hand over. Practitioners publish permission matrices grading actions by blast radius × reversibility × stakes. If you want the general framework, those sources will serve you better than a solo-builder blog, and I’ll list them at the bottom so you can check them. ...

Everyone building on AI now is asking the same question: which model? And it’s the wrong question, because the model is the one part of your stack you don’t own, can’t keep, and will be forced to swap the moment a cheaper one ships. What you can own is everything that wraps around it. The memory. The rules. The decision boundaries. The list of things you’ve already verified and never have to verify again. ...

The agent said the tests pass. The commit is pushed. The deploy finished. As far as the summary in your chat window is concerned, the feature is done. Then you actually click the link and the page is a blank white screen. This is the most expensive sentence a solo builder learns the hard way: “done” is a claim, not a fact. And when your team is a handful of AI agents working through a chat interface, the gap between “claims done” and “is done” stops being an edge case and becomes the whole game. ...