Hey Clief Notes group! 👋 I'm Hoss and I'm stoked to be here. 🙋 A little about me: I'm 20 years deep in IT — mostly platform, infrastructure, compute, and storage. 🎯 My current goal: Learn ICM enough to complete a build without struggling. 💪 What I'm currently building/working on: When I'm not keeping systems alive, I'm building local AI setup and applying ICM workflow to local AI. 🤔 My biggest struggle or question right now: Impatience. I'm getting ahead of myself and getting frustrated.

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.

📣 Update (8/3/26): Comp 10 Rules Added, Submissions Due by 8/8 11:59 PM, Winner Announced 8/15 --- What this thread is: I’ve seen a number of people either not know competitions are going on or know how to find them so here is a quick single source thread where you can get to them all. I’ll keep this updated as new challenges are released. See the current challenge as well as all past challenges below! Format for community challenges: https://www.skool.com/cliefnotes/how-competitions-work-from-now-on?p=84912d60 Weekly leaderboard competition: Alongside the biweekly challenges, there is a weekly leaderboard challenge where the member at the top of the 7 day rolling leaderboard wins a free upgrade to their membership. This winner is announced on Mondays typically. @Joshua Hubbard has gone another step further and created a thread linking to all competition entries. Link here: https://www.skool.com/cliefnotes/the-competition-archive-every-entry-every-week-every-link?p=bd752987 --- Current Challenge: Competition 10 The Challenge 💪 - Build a full folder-based diagnostic auditor that tells you why something is broken. Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/weekly-comp-10-the-diagnostician?p=367505f3 Good luck everyone! --- Past Challenges Competition 1 The Challenge 💪 - Build a brand voice document for a pet grooming business Rules & submissions 🗒️ - https://www.skool.com/cliefnotes/first-ever-weekly-competition-is-live?p=90f50bf9 Results🏆 - https://www.skool.com/cliefnotes/weekly-comp-1-winner-ian-barriopedro?p=0501b57e

This community is large and it moves fast. That's the good part and it's also the problem: valuable posts get buried, the same questions get re-asked instead of found, and spammers show up wherever there's an audience. These guidelines are what keeps the room worth showing up to. Read them once. You won't need them again, because most of this is what you'd do anyway. New here? Start with Jake's welcome post and the Foundation course. This post is about how we behave, not where to begin. 1. Build in public. Post the thing while it's half working. A half-finished build is more useful to everyone else than the polished writeup you'll never get around to, and you'll get corrected before you've spent a week going the wrong way. 2. Teach what you learn. The day you figure something out is the day you're best at explaining it, because you still remember exactly what confused you. A month later you've forgotten the hard part and your explanation gets worse. If you cracked something this week, that's a post. Nobody has to earn the right to ask a question here, but this place only works because people come back and answer them once they can. 3. Ask good questions. Specific beats polite. "How should I structure this?" gets three vague answers. "I have a 40 file client folder, the model keeps loading the wrong context file, here's my CLAUDE.md" gets a real one. Say what you tried, what happened, and what you expected instead. A more in depth guide: https://dontasktoask.com The flip side of this: "Anyone here?", "Help please", and one line questions with no context may get removed. Not to be harsh, but because nobody can answer them. 4. Give credit. If you built on someone's skill, template, folder structure or comment, tag them. It costs you nothing and it's the reason people keep publishing their work here instead of keeping it. A lot of the best material in this community started as somebody's reply on somebody else's post.

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.