1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

This week's roadmap is officially open: Building Your Stack. And I want you to approach this one differently. As you go through it, don't just ask yourself: "Do I understand this?" "What does this look like for me?" You'll be working through lessons, quizzes, and accountability posts designed to make you stop and actually think through what you're building. Some of the accountability steps will ask you to summarize what you've learned. Others will force you to make decisions about how you're going to apply it. By the time you reach the end, I don't want you to just know more. I want you to have something clearer than what you started with. Take your time with this one. If you get stuck, ask the Clief Notes AI questions along the way. It knows the material and can help you find the right lesson or work through something you don't fully understand. Building Your Stack is available now for Premium and VIP members. Premium and VIP also unlock: - Live calls with me - Unlimited conversations with the Clief Notes AI - All of our new roadmap quizzes and accountability challenges - Early access to the new Decster features we're building If you haven't upgraded yet, you can do that here: https://www.skool.com/cliefnotes/plans If you're already Premium or VIP... Your stack isn't going to build itself. 🧱 Head to the Roadmap tab and get started.

$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.