Hi @Jake Van Clief & Mods, I've now reached level 3 but can't access these 2 classrooms. Not sure if I still have to do something.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪

🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.

Browsing on Skool can be a bit overwhelming with it's UI (my eyes need a dark theme) and the great volume of stuff on CliefNotes makes jumping in daunting, especially if you're away for more than a day, so I wanted something that made browsing feel effortless and easier to navigate and see things and keep posts around that I wanted to dig into a bit more. So I built a browser extension that gives me a faster, cleaner view over the same Skool feed, posts, and comments. The catch: I don't know web code. I don't know APIs. But I've learned that knowing what I *don't* know is exactly where AI earns its keep. I know how to troubleshoot — so I can tell it what's happening, what's breaking, what information I need next — and it hands me the technical roadmap I don't have. I wasn't writing this thing so much as steering it. The part that nearly broke me was comments. A post with over 100 replies would render only 50, and I couldn't see why — Claude almost threw in the towel but I persisted because one thing I've learned working Game Dev is that if you can see something on the screen then that data exsists somewhere, you just have to figure out where to look. The takeway I want to flag is to think about pointing AI at your pain points, the best things to come out of using ai for me have been asking "What if?" And a lot of the amazing things people have created in here follow the same pattern. I also want to highlight this post by @Jason Jennings : https://www.skool.com/cliefnotes/sortable-posts-clief-notes-sidebar-easy-copypaste I was in the middle of my build when I came across it and I folded some of the sorting options into the extension because I thought they were great I built it to be shared — open source, free, and I'll keep updating as I go, genuinely open to suggestions. Only caveat is it can only do what Skool's API allows. Also I use Firefox mainly and it's easier to sign a native browser extension for firefox so you can install directly using the .xpi link in my repo, for Chrome you'll have to download the .zip and in Chrome set it to developer mode and you can sideload an unpacked extension (instructions should also be in the zip).

my Live Health Stream is a real-time telemetry dashboard designed to monitor the "cognitive load" and operational stability of autonomous AI agents across different sessions and models (e.g., Gemini 3.1 Pro, Claude Sonnet 4.6). I am using both AntiGravity and Claude Code. They write to my obsidian vault, and my dashboard is a HTML/CSS version of that data along with python scripts that aggregate my json data for metrics I want to measure. Tool Error Rate % (Red Line) - What it is: The frequency at which the agent is failing to execute its tools properly (e.g., syntax errors, bad file paths). - How it’s calculated: (Failed Tool Calls / Total Tool Calls in the session) * 100. Notice on the graph how the red line spikes almost immediately after the green saturation line peaks. Context Saturation % (Green Line) - What it is: A measure of how "full" the agent's brain is getting. - How it’s calculated: (Total Input Tokens / Model's Maximum Context Window) * 100. If this hits 100%, the agent starts forgetting earlier instructions (context eviction). Lessons Learned (Yellow Bars) - What it is: The number of times an agent gets caught in a recursive failure loop (trying the exact same failed action over and over). - How it’s calculated: Programmatically tracked by analyzing the execution log for identical, sequential failed tool calls within a single session. I have a "Lessons Learned" log that I have my agents read on boot, and then if they **** up they have to record a lesson there, and update the .json file for that session where i build this graph from. Input/Output Tokens (Blue/Purple bars) Since this is not exposed I have to do an estimate: "input_tokens": input_bytes // 4, "output_tokens": output_bytes // 4, One of my core philosophies is No Vanity Metrics, and another is Things that are Measured Improve, and Ultimately, The Most Important Things Cannot Be Measured.