Here I go again - realizing that @Bas Rosario post today, about pointing an AI model at his own setup and asking it to make itself cheaper, unveiled insights I thought would be of value to those who read both (original post https://www.skool.com/cliefnotes/i-just-spent-the-last-few-hours-asking-fable-to-make-itself-cheaper?p=cc666986). Bss wrote "It found a file that reported its own size as 450 tokens. The file was 7,000." I ran the same thing on my own system and found my version of it. A status file that declares a 10KB limit in its own header while sitting at 39KB. I'd read past that number a hundred times. That's not the part I want to talk about, though. What his post really did was make me look at where verification lives in a system, and I think most people keep it in the wrong place. The common setup is to build something first. A workflow, a stack of tools, an integration. Then you add checking at the end. You generate, then you verify. Verification becomes the last step, the thing you bolt on when you're worried the output might be wrong. I built mine the other way around, and not on purpose. I had nothing to start with. No existing architecture, no integrations. I built through the method itself, one worker at a time, and the first thing each worker learned was when to refuse. Verification wasn't a step I added later. It was the floor everything else got built on. Here's why that ordering matters more than it sounds. When verification is the base, the model stops being the important part. The AI gives you access to skill. Think of it as a set of clubs. A professional golfer can put the ball where they want with a lesser club, because the skill is in the swing, not the gear. Enforced verification is the swing. It's what lets you reach for the cheap, fast model when the job is grunt work, and the expensive one only when the job actually needs it. The right club for the setting, instead of swinging your driver at every shot because it's the fanciest thing in the bag.

1. completed the implementation playbook 2. Levelled up to 3 3. Created my first sample folder structure for a solution