🔍 Three things to notice. 👇 1️⃣ Numbered folders set the execution order, so 01- always runs before 02-. 2️⃣ Each stage carries its own CONTEXT.MD, references/, and output/. 3️⃣ The handoff between stages is dead simple. Stage 1's output/ is what stage 2 reads as input. ================== 📂 The folder structure workspace/ -------------------------------------------# the whole operation CLAUDE.md ------------------------------------------# L0: orientation, "where am I?" (always loaded) CONTEXT.md --------------------------------------- # L1: the map, "where do I go next?" stages/ ------------------------------------------------ # all the steps in order 01-research/ ---------------------------------------- # step 1: gather the source material CONTEXT.md ---------------------------------------# today's job description references/ ------------------------------------------# rules for this step output/ -------------------------------------------------# what this step produced 02-script/ -------------------------------------------- # step 2: turn research into a draft CONTEXT.md -------------------------------------- # today's job description references/ ----------------------------------------- # voice rules, examples output/ ----------------------------------------------- # the draft lives here 03-production/ ------------------------------------# step 3: ship the final artifact CONTEXT.md ------------------------------------- # today's job description references/ -----------------------------------------# design system, build conventions output/ ----------------------------------------------- # the finished product _config/ -----------------------------------------------# L3: brand, voice, design (configured during setup) shared/ ----------------------------------------------- # L3: assets every stage might use skills/ -------------------------------------------------- # L3: bundled skills the agent can call setup/ --------------------------------------------------# first-time configuration

That's the leap most people never take. Roughly 90% of our members are still on the other side: scrolling, saving, getting value, never saying a word. Not a knock. Just the math. Lurking isn't failure. It's the default. But you showed up. And that shift compounds fast. The classroom teaches you the tools. The community teaches you how to think with them. When you participate, you get compression — months of grinding folded into a thread someone else already broke so you don't have to. Less friction. Faster outcomes. Personal growth and business growth in the same lane. You don't need a hot take. You need a real question. Give before you extract. Your lurker era wasn't wasted — you were loading context. Welcome to Level 2. A few of you just made the jump, and I want to call it out: • @Vamsi Acharya • @Stacey Lubowa • @Martin Brion • @Mark Benjamin • @Keith Langskov • @Patti Wilcox • @Novus Vella • @Tony Rhodes @Cain Gray If you're still lurking — go check out what they're posting. Real builds. Real questions. No fluff. That's the energy we want in here. And if I missed you — my bad. Drop your name below. We'll get you in the next round. The reward for showing up isn't points. It's speed. You stop duct-taping alone. You stop renting confusion. Your stack starts to click because other people's scars are now in your context. What finally made you break the ice? ───

I just realized something today, Jake's first classroom lesson isn't about Claude Code. It's a history lesson. Titled "A 2,000-Year Overnight Success." The argument: AI is not 70 years old. https://www.skool.com/cliefnotes/classroom/d7ae60cf?md=147b0e486c964ba78a70cdc1d2d40c5d I don't need to rehash it here; if you skipped it, go back to read it. It was the first weekend of April, I had found Jake's videos the week before, then discovered Skool and dove into the classroom. I made a commitment to myself to read each page, not throw them into NotebookLM for the summary. To my disappointment, I see a super long history lesson. I sink into my chair. Eventually, I get to the end. AlphaGo. I had never heard of AlphaGo before; somehow, that story had slipped past me. I queued up YouTube on my TV and sat down for a Saturday evening documentary. Fascinating! AlphaZero started tabula rasa. Blank slate, no domain-specific human knowledge. Just the rules and play against yourself. In four hours, it rediscovered centuries of chess openings, endgames, and positional theory - then kept going past what humans ever found. Kasparov called it "like discovering the secret notebooks of some great player from the past." Those moves weren't invented. They were already in the game. The truth was latent in the mathematical structure of chess. AlphaZero excavated it. That's the archaeologist move - applied to a machine. It didn't study the tradition. It played to the pattern. Jake's throughline: "The mistake is thinking these layers replace each other. They don't. They stack." In the classroom, he could have started with how to prompt or an explanation of what a harness is. Instead, he started with the source of the whole thing. Because you can't build conviction on a trend. A pattern that's held for two thousand years isn't a trend. That's proof. I've worked with a family lumber business. 125 years old. Founded 1900, delivering coal by horse and buggy. Today, it's digital marketing, performance ads, algorithms, and closed-loop lead tracking. Every generation rebuilt what the company looked like. But the fourth-generation president still says what his father said: "Young man, we're not in the lumber business. We're in the shelter business." The tools stacked. The belief didn't.

I keep coming back to one thing today: I didn't build any of this alone. Thank you, genuinely, to this community. Winning Week 7 is humbling. But the part I actually want to mark is what it took to get here, and how much of it came from you. Over these weeks I've sat with the repos people shared in here. The pipelines, the auditors, the intake operators, the safety checkers. I opened them, read how they think, and walked away a better builder every time. Honestly, half of what's good in my own work started as something I noticed in someone else's. That's the quiet gift of this room: everyone's work is a lesson, if you're willing to look. To everyone who read my articles and clicked into my repos, and especially anyone who left a comment: thank you. You may not know what it means to put something out and have a person actually see it. After thirty years of teaching, that still lands every single time. And to the team I built that operate behind the scenes who put in the hours so these builds could ship clean: I see you. This one is yours too. I'm not going anywhere. I want to keep sharing what I'm learning, and just as much, keep showing up for your work the way you've shown up for mine. Grateful. Let's keep building. 🙏 — Gabe Oh, and of course @Jake Van Clief and the entire back team that supports us - without you, none of this would have ever been possible in my life. Words do very little to truly honor and express my gratitude for this recoognition. And now...for the virtual champagne bottle opening 🥳🥳🥳🥳🥳🥳🥳

My best friend’s dad is currently going through cancer treatment and there is a go fund me to support his medical costs. I’m not expecting anyone to contribute life is costly enough but if you have it in your heart and are able to help it would be appreciated more than anything. Thanks in advance to anyone who takes the time to read this! https://www.gofundme.com/f/support-mikes-cancer-journey-594gk?attribution_id=sl:15012345-d96b-4d61-8d72-478b304a6fae&lang=en_US&ts=1781827434&utm_campaign=fp_sharesheet&utm_content=amp20_t1&utm_medium=customer&utm_source=facebook&fbclid=IwRlRTSASheIRleHRuA2FlbQIxMQBzcnRjBmFwcF9pZAo2NjI4NTY4Mzc5AAEewEgvL9AJQEZZj4hn-1GjsoRFFucAjFoNIwMfSrKK0H6msk7Hga8rGkqyWWg_aem_sJu0t4KDXFlHZ4Z_eAyFbA