If you've been working through the roadmaps every week, you've probably noticed something. They're getting harder. That's intentional. - We started by helping you navigate the material. - Then we started testing your understanding. - Then we started asking you to explain it, apply it, and prove that you actually grasp what you're learning. Now we're taking another step. The Drawing Room roadmap is officially open. And this one is exclusively for VIP members. Expect this roadmap to ask more from you. - More thinking. - More application. - More accountability. And fewer opportunities to just passively consume something and move on. You'll have quizzes throughout the experience and accountability posts designed to make you stop and articulate exactly what you're taking away. Take your time. - Use the AI when you need help. - Revisit lessons when something isn't clicking. - Bring questions to the calls. The point isn't to finish first. The point is to come out the other side actually understanding the material. If you're VIP, head to your Roadmap tab. 🚪 The Drawing Room is waiting. If you want access to The Drawing Room and everything else available at VIP, you can upgrade here: skool.com/cliefnotes/plans

You've had the weekend with The Drawing Room. I deliberately wanted this roadmap to push you a little harder than the previous ones. So I want some honest feedback. How difficult has it been? 🟢 Easier than expected 🟡 Challenging, but manageable 🔴 Making me question everything 😂 And tell me which step has made you think the most so far. Remember, getting stuck isn't necessarily a bad thing here. If a quiz exposes something you don't fully understand, or an accountability question takes you longer than expected... That's the roadmap doing its job. - Go back. - Find the gap. - Ask the AI. - Bring it to the next call if you need to. Then keep moving. Drop your 🟢 🟡 or 🔴 below and tell me where you're at. 👇

A while back @Carla Bosteder was talking about ideas... This one stuck with me as I am constantly thinking about how I handle my ideas. I created an animation for fun, but kept thinking about what could be done with ideas while chatting in Claude. Unfortunately, most die in the chat they came up in. I'd been working on this for a while when I read @Bas Rosario on how he handles memory. There's some crossover with his idea, and it's a great one. It got me thinking more about how ideas connect to each other, and when an old one should come back. It's called the Idea Engine, and it plugs into Claude. The video is the 80 second version. The short version of what it does: 1. You float an idea while you're working on something else. Claude saves it in your words, with what you were doing and the date, and you keep going. 2. A small model checks that it really is an idea and not a task or a question before it's kept. 3. Later, when you're working on something new, an old idea that fits can come back with one line on why. Or you just ask, "what have I thought about pricing?" It's in testing on my own machine right now, with 148 of my ideas loaded. The testing is doing its job. Yesterday it missed every idea I had across a full day of chats, so the part that notices an idea is getting fixed before anyone else gets it. It goes out to a small group very soon. If you lose ideas the way I do and want to try it, let me know below. How do you keep track of your ideas now?

📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline. Seventeen of eighteen had nothing after it. Then we did what the rubric asked, for every entry. We read the schema in reference/ first. We found the rule for a field with no source. We ran your folder three times: on the input you shipped, on that input with something the schema needs cut out, and on that input with irrelevant material stapled on. Then we picked five claims from your own output and found where each one came from in the input. That trace table is in your file. Five claims, five locations. You can see exactly where we looked and what we found. Every entrant shipped an input. That alone made this the most checkable field we have judged. 📚 WHAT THE FIELD TAUGHT Three lines split eighteen builds: ✅ The degraded test broke almost nobody. The rubric expected most entries to fail here, handing back a shorter document when the input ran short. Seventeen of eighteen kept the full shape and marked the gap. Name the hard case precisely and this community builds for it. ✅ The one way to lose held for seventeen of eighteen. The brief named it: put something in the output that was not in the input. We traced five claims in every entrant's own committed output. One entry had it. The near misses all had the same shape. The quote was real, and the value, the link or the sentence written next to it was not checked. Sixteen entries ship a checker, and we planted a fault in every one. Fourteen caught it by name. The two that missed had that same blind spot. ✅ Drop nothing turned into keep everything. Seven builds have a contract that cannot ignore anything, so a stapled email became a compliance row, a speaker, or an allergen. Every leaked line was quoted and cited, so nothing was invented. It was still noise on the page. Coverage and noise rejection pull in opposite directions, and only a few builds wrote down which one wins.

🎁 $1,000 IN EDUBAWARE CREDITS 🎁 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI translator that takes one kind of work and turns it into another kind of work. Same shape in, same shape out, every time. Not a summarizer. Not a writer. A converter with a contract. This week's deliverable is one translator folder that someone could drop into a Claude project, feed it the input it expects, and get back the output it promises. Every time. Without surprises. 🎯 PICK YOUR CONVERSION The conversion is yours. Pick one you do by hand right now and hate. A few sparks to get you thinking: - 📞 Sales call transcript → CRM notes in your team's exact fields - 📝 Long-form essay → LinkedIn carousel, slide by slide - 🎙️ Meeting recording → product requirements doc - 🔬 Research paper → investor one-pager - 🐛 Bug report thread → Jira ticket with repro steps - 📧 Customer email → support ticket with severity and category - 📊 Spreadsheet export → weekly status update - 📖 Interview transcript → case study draft - 🧾 Receipt photos described in text → expense report line items - 📋 Discovery call notes → SOW first draft The more locked-down the output, the better. "Turns notes into a doc" is not a contract. "Turns discovery call notes into a five-section SOW where section 3 is always scope exclusions" is. 🔥 THE ANGLE THIS WEEK Last comp was The Auditor. Every finding cited a provision so a reader could open the standard and check. The comp before that was The Cartographer. Every card cited a file and a line so a reader could open the source and check. The Translator is the same discipline, one more time. Every line in the output traces to a line in the input. ↔️ A translator has three properties that a summarizer does not: 1. The output has a fixed shape. Same fields, same order, same format, regardless of what the input looked like. If the input was messy, the output is still clean. If the input was short, the output still has every field, marked empty where there was nothing to fill it.