***A note before you read: this post talks about losing a parent to drug overdose, addiction, and some of the harder parts of growing up through that. If any of this hits close to home, take care of yourself first.*** This is personal, not ai related but feel its important to share. Both @Matthew Creamer and I lost our fathers to drug overdoses. I don't say that for sympathy. I say it because it's the kind of thing that rewires your entire life and I think some of you need to hear that the people building this thing with you know what it feels like to start from somewhere broken. My dad was a good man. I need you to know that before anything else. He was loving, he was present, he was the kind of father who wanted his son to never have to grind through the kind of work he did. He spent his life in construction, the kind that wears your body down year after year, and he always told me he wanted something different for me. He wanted to retire the whole family one day. He wanted to leave a mark on the world and he wanted me to do the same. He just had his demons, and one night when I was 15 they took him from me. A month after my birthday so I was still basically 14 years old and I found him on the couch and that was it. Everything after that moment I had to figure out on my own. I learned how to trim my beard without him standing behind me in the mirror. I learned how to haggle with taxi drivers in countries he never got to see. I broke my heart for the first time and had nobody to call who could tell me what that kind of pain actually means when you're young and don't know who you are yet. I fell into addiction myself somehow escaped after a lot of battles. I joined the Marine Corps and that brought its own tragedies, its own weight. I climbed the tallest mountain in Europe. I walked across the grand sands of the Middle East. I have tasted war and peace, depression and anger, and so much more that I am still learning how to carry.

I want to take a minute to thank @Jake Van Clief for giving me the opportunity to bring this material to our community. This community is more than just a place to post, it's a place to engage with people, to learn and grow together and I am grateful to Jake and the community for making this skool what it is. If you have been following the releases of my latest classes, the latest rung on the ladder is open! (If you are just getting here, do not worry, the first three rungs are open, and you can find the links below in the "where you are standing" section of this post ☺️) Rung three built what survives the window. Rung four is what runs without you, open from today. Think of the last thing you asked the model to redo. It drafted, you read it, you said "shorter." It drafted again, you read again, you said "warmer." Then "send it." Four rounds, and every one of them waited on you, because the only thing that knew what good looked like was sitting in your head. That is not the model being lazy. That is a loop with a person welded into the middle of it, and the person is you. 📚 What just opened: Loop Engineering, the whole rung at once. The Overview draws the line the rung stands on, single-pass against a closed circuit, and the three classes carry one claim each: (1) The acting is easy, the evaluating is hard (2) A loop that does not know when to stop is not careful, it is lost (3) Some judgment stays with a person, on purpose Then the payoff, the whole series on one card, and my perspective on rung four. By the end you own a loop: your "done when" line rewritten as a check the system runs on its own work, a rule for when it stops, and one clear place where you still sign off. Fewer "agains," and every one that is left is one you chose. 🪜 Where you are standing (Rungs 1, 2 & 3 should be completed) If not, you can find them here. They are in order and should be taken from series 1 to series 2 and so on: PROMPT ENGINEERING 📚 Series 1 Overview

This is where I want you to slow down. There's a lot inside Clief Notes that's easy to consume once, think "that was useful," and then completely forget about. The Vault is designed to prevent that. You're going to work through the material step by step, but this time I want you paying close attention to the things worth keeping, revisiting, and actually using. You'll run into quizzes that test whether you really understood what was covered. You'll also have accountability posts where you'll need to put the ideas into your own words. Some of these might take you a few minutes. Others might make you sit there and think. That's a good thing. There's no prize for completing the roadmap in an hour. The win is finishing it and realizing you actually remember what you learned. 🔐 The Vault is now available for Premium and VIP members. If you're not Premium yet, you can unlock it here: skool.com/cliefnotes/plans That also gets you: - Live calls with me - Unlimited Clief Notes AI conversations - New roadmap quizzes and challenges - Access to the upcoming Decster features Already have access? The Vault is open. Go see what's inside.

$500 to one winner. Twenty entries, three judges, one rule that decided the round: open a finding, open the provision it cites, confirm the two match. 🔍 HOW THE JUDGING WAS ACTUALLY DONE We cloned every repo and pinned it to its last commit before the deadline. Nobody got judged on late work, and nobody lost credit for early work. Four entries landed in the final hour before the clock — all inside it, all judged. Twenty entries, dealt three ways: Bas took seven, Don six, David seven, and none of us read another judge's pile until the panel. Comments got you through the door. The judging happened inside the folders. Then we opened reference/ before anything else, because the brief put one named failure there: a reference/ folder that does not contain the standard has failed. Not a summary. Not a link. The standard, in the folder. Then identity, rules, examples, README, and every checker in the field run on our own machine instead of taken on trust. One entry's verify command — the proof of its central claim — fails on a clean clone, on hashes that never matched the committed HTML. The two-line fix is in its file. Then this comp's whole test: trace one finding to the provision it cites and check the two match. On top of that we planted things. Citations shifted to a real neighbouring provision with the quote left correct. Defects hidden in artifacts the auditor had never seen. Requests to fix what the audit found. One auditor was asked to drop a failure for a ship date. 📊 WHAT THE FIELD SHOWED Three lines split this field. The first is the named failure, and this time the field passed it. Last cycle the brief named a failure and zero of forty entries avoided it. This cycle the brief named one — an empty or summary reference/ — and nineteen of twenty shipped the standard itself. Statutes verbatim behind machine-read anchors. The issuing authority's own PDF, byte-confirmed against a live download. One entry keeps the publisher's HTML and regenerates the text from it. The one that didn't was scored, not excused. Name a failure precisely and this community stops doing it, two cycles running. Worth knowing for how we write the next brief.

Another new face on the leaderboard! Congrats @Michael Steve . What Michael wins: Lifetime VIP for completely free! ⏰ The 7-day clock resets. Next Monday someone new takes the top spot. 🎯 How it works: - 📝 Post things worth reading - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with what others are putting out there The leaderboard tracks all of it. 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying.