Hey, When does this lyceum start? So confused about it

💰 $500 CASH 💰 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI auditor that checks something against a specific standard and reports where it falls short. Not your opinion of what's good. An actual standard that exists in the world. This week's deliverable is one auditor folder that someone could drop into a Claude project and use to check their work against the rules of their industry. 🎯 PICK YOUR STANDARD The standard is yours. Pick one that actually exists. Pick one you could point someone to. A few sparks to get you thinking: - ♿ WCAG 2.1 AA accessibility audit of a web page - 🔒 GDPR audit of a privacy policy or data flow - 📋 SOC 2 readiness audit of a security policy doc - 📄 Contract audit against standard SaaS data-handling clauses - 🏗️ Code audit against a specific style guide (PEP 8, Airbnb JS, Google Java) - 🏥 HIPAA audit of a patient intake process - ♻️ Brand compliance audit against a published brand guideline - 📊 Financial model audit against FAST modeling standards - 🎓 Grant proposal audit against a specific foundation's published criteria - 📱 App Store submission audit against Apple's review guidelines - 🧾 Invoice audit against a client's stated payment terms The more specific the standard, the better. "Audits for quality" is not a standard. "Audits a React component against the WCAG 2.1 AA success criteria" is. 🔥 THE ANGLE THIS WEEK Last comp was The Cartographer. Forty of you built maps where every card cited a file and a line, and we cloned the territory to check the cards against source. The ones that held up were the ones a stranger could verify. The Auditor is that same discipline pointed at a rulebook instead of a codebase. ⚖️ Every finding cites a provision the way every card cited a line. The standard is the territory. The audit is the map of where the artifact sits against it. Three things separate a real audit from an opinion: 1. The standard is external and citable. Your auditor should be able to say "this fails WCAG 2.1 success criterion 1.4.3" not "this contrast looks low to me."

📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline, so nobody got judged on late work. Only two repos had any post-deadline commits at all. Cleanest field this competition has had. Then we read file by file. Identity, rules, examples, the reference layer, the code. We ran every checker in the field on our own machine. Three would not run. For eleven entries we went further. We cloned the territory, or the entrant shipped it, and checked the cards against the source. Eleven is all the field allowed. Everyone else pointed at something private, unpinned, or gone. Two of those eleven were public codebases nobody in this community controls. On one gate we planted a bad citation to see if it would fire. Comments got you through the door. The judging happened inside the folders. 📚 WHAT THE FIELD TAUGHT Three lines split forty builds: ✅ The one rule held. The brief was blunt: a README that tells people to add every file has failed. Not one entry made that mistake. Every search hit was either a rule against it or a fixture broken on purpose. Name a failure precisely and this community stops doing it. ✅ Enforcement is now the baseline. Sixteen entries ship a checker that runs offline with no API key. Last cycle that was the headline. This cycle the checkers got better. One broken fixture per gate is now normal, and the best gate also ships a clean fixture to prove it stays quiet on honest prose. ✅ The cold walk decided the round. About half the field shipped a receipt of a reader entering a catalog, opening one card, and stopping. The top of the field is almost exactly that set. A map can be accurate and still hard to walk. This week we scored the walk. 🥇 THE WINNER @Adam James The Cartographer, a map of a live GoHighLevel account, built so a VA can change one message without guessing which of a dozen lookalike workflows owns it. He wrote down his test method before any test ran. Then he did what almost nobody does. He handed his work to people who could make him look bad, and let them.

*UPDATE: Our 2nd session is scheduled for Sept 12 https://www.skool.com/cliefnotes/calendar 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 🙏 So this Saturday, I'm hosting a Skool webinar here (Approved by Jake & Sonija) https://youtu.be/dryW_H54Rss 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. ━━━━━━━━━━━━━━━━━━━━ 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 Most people are stuck somewhere between 1 and 2 — and have no idea there's a 3. ━━━━━━━━━━━━━━━━━━━━ 🙌 WHO THIS IS FOR If you've never done ai video or never gotten one great shot and then couldn't get a second one that matched — this is for you. ━━━━━━━━━━━━━━━━━━━━ 💬 ONE ASK BEFORE SATURDAY Drop a comment below: which level are you on right now, and what are you trying to make? I'm building the second half of the session around your answers — so the more of you who answer, the better this gets. And if there's appetite, this could becomes a regular thing 😉.

Hello, can anyone let the administrator that I cant test the eduba alpha? @Jake Van Clief ?