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.

This is for people who are not technical. Someone with a normal job who saw something on YouTube and wants to be able to make something similar for practical use. Live with Danney Trieu · Four months ago I had never made a single AI video. I'm not a deeply technical person and never done any film in my life before, I'm just very passionate about this space. I figured out where the decisions live — which ones you hand to the machine, and which ones you take back. Then I found Jake & ICM just like many of you. Once I saw his method, everything got easier. More valuable than that, I found this awesome community that keep motivating me and supporting me. I like to give it back.. Every Saturday, I'm hosting a Skool webinar here: 🚩*UPDATE (09/22): Class cancel on 26th. I have to fly out to prepare for a visual staging concert in Vegas. I hope to learn a lot from this experience and bring back what some knowledge for you guys. Until then, keep on vibe filming ! Session records: https://drive.google.com/drive/folders/1TNk-42gZajrTWw-2tD3Fbn760UE-BeM_ Reelix explainer: https://danneytrieu.github.io/vibe-film-sessions/index.html Higgsfield affiliated link: https://higgsfield.ai/?fpr=nguyen61 My discord channel: https://discord.gg/EKab83ZGB Youtube: https://youtu.be/dryW_H54Rss ━━━━━━━━━━━━━━━━━━━━ Here's what I'm covering -> 🪜THE SIX LEVELS OF AI FILMMAKING 1 · PROMPT — you type it, the model decides everything else 2 · REFERENCE — you stop describing the look and start showing it 3 · MEMORY — your world lives in folders, so you stop re-explaining it 4 · BLOCKING — you decide where the camera goes, not the model 5 · DNA — your taste, written down, applied automatically 6 · AUTOPILOT — you point it at your work and it hands you the shot list

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!