User
Write something
High Tea is happening in 40 hours
Pinned
Welcome to Clief Notes. Here's where to start.
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?
Pinned
🤯 Something in here has been broken for a while
Alright, here’s what we’ve been sitting on. We’re past 2,700 posts and 40+ lessons now. The number one thing we hear on Wednesday onboarding calls is some version of: “Where do I start?” “What should I do next?” “Did someone already answer this?” Fair. There’s a lot in here. So we’re bringing in an AI trained on the Clief Notes library. Every lesson. Every Afternoon Tea. Every High Tea drop. It actually knows what’s in here. 🧭 Tell it what you’re stuck on, and it points you toward the right lesson or drop. 🗺️ Tell it where you’re at, and it can help you figure out what to focus on instead of just telling everyone to “start at The Foundation.” 🔍 Ask it about something we’ve covered before, and it helps you find it without scrolling through months of content. And when we launch it, everyone gets access. More on that very soon.
Something is coming 👀
Been heads down on something the past month plus. Not a lesson, nor a Tea round but more like the layer under all of it. Kept seeing the same thing in comments and onboarding calls: People not knowing where to even start or if something’s already been covered somewhere in here. We're working on fixing that. Not ready to put it in your hands yet.
I'm new here - Ya'll are literal wizards and no one is talking about it.
My background is working in quality assurance in medical device companies, and I've always worked with software teams. I remember always walking past the software department and seeing their big black screens with all this code. It gave me a little bit of anxiety, but it also looked so cool because they looked like these hackers, just like in the movies. They were all sitting there so nonchalantly, but they're literal geniuses. One day I was sitting in a meeting with one of my colleagues, and I had to deal with an Excel spreadsheet that had like a thousand lines of information in it that I had to parse. I was doing this manually because the data hadn't been entered uniformly. One of our engineers was like, "Give me 30 minutes. I'll write a script." I paused, looked him dead in the eye, and said, "Hey man, I need to know how you do that. I want to watch you," and so I did. That was the day that I found out you can literally just control your own machine with scripts. The moment I found that out, paired with GPT-3 at the time, I started making scripts for everything. I even made a little desktop pet that, if you clicked it, would spawn a motivational message in the command prompt. I've also recently learned about bit flips (video in the classroom course) literal cosmic rays from SPACE can hit your RAM and make pretty big changes?????? Anyway, the thing is, I think you all are magicians. ˙⋆✮⋆˚࿔ Every single person who works with software and code and tech ...just makes things, you are all creators, and everyone's being so nonchalant about it. It's crazy. ✧˖°.
ICM is directing our marketing video. Without it, the whole thing falls apart.
@Jake Van Clief We are producing a sales video for one of our Kelowna projects (Siren St. Paul). Generated in Higgsfield, finished in Canva, directed from an ICM workspace. I want to show what the structure did, because the structure did the heavy lifting. The setup. Five numbered stages: source, spec, boards, scenes, assembly. A _shared folder holds the brand facts and the method. Every stage has a CONTEXT.md contract (inputs, process, outputs, what I check before anything moves). Status is just what files exist. Nothing advances until I have read the last output. The core problem with AI video is drift. Same prompt in, different look out. The fix is a three board system (component board, frame library, motion board). The boards are the factory. Stage 3 builds them once, stage 4 references them in every scene. Nothing gets re-explained to the model, ever. Here is the part worth posting. Every stage boundary in the workspace is a gate. Cheap, boring, just a human reading the output before the next stage is allowed to touch it. Those gates caught three real failures before they could reach the film: 1. The curation gate caught a style hijack. One phrase in a shared suffix ("layered mountain haze") turned close up tiles into wilderness scenes. The prompt asked for an urban window glow and the model delivered a rustic mountain chalet. Four tiles rejected, regenerated, and the fix written into the run book (two suffix variants, one for landscapes, one for details). 2. The QA gate caught name contamination. The word "Siren" in the style preset description made the model paint a literal mermaid statue into a test image of a coffee cup. The gate exists precisely for this (five test generations on subjects the boards never contained). New rule: the project name never appears in generation side text. It is composite layer vocabulary only. 3. The review gate caught invented geography. The map in our "center of it all" scene had streets that do not exist. The gate put that frame in front of a human before anything downstream could use it, and the human happened to know Kelowna. The fix came from our own asset library (the amenities map from our showroom signs, used as an image reference). New rule: anything showing real geography generates from a real reference. Same rule that already protected the building (the hero shots are image to image from the actual rendering, so the architecture in the film is our architecture).
1-30 of 3,053
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by