🔍 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? ───

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

Quick note for those of you in here just starting out and chasing your first clients: it ain't all roses and rainbows on the other side. Most of what gets posted in this community are the wins. Tonight you get one of the harder nights. Take it however you take it. Last night a client sent me a "you didn't deliver" email at 11pm. Hard read. The kind where your stomach drops and you start rereading every contract clause you signed three months ago. Spent the next 9 hours running an audit of every deliverable across two Fractional CMO contracts and a brand + website project. By 2am I had numbers on it. They paid us a bit under $20K combined. The audit showed I'd scoped out closer to $60K of work for that price. That number is the painful one. Four mistakes got me here. Maybe one of them is sitting in your shop too. ------------------------------------ 1. I ignored the human flags. ------------------------------------ (EDIT: My team encouraged me to remove details from this first point out of an extreme abundance of caution. I don't think I'm whitewashing this point, but if you disagree, letm know in the comments. PS. Update incoming.) Early on I saw how this person treated people who weren't in the room. How they talked about the people closest to them. How they described their own team when those folks couldn't hear it. That's a personality profile in a handful of data points. I noted it. Then I told myself "everyone has their style" and kept building. And I still think there are real human reasons they operate this way. Doesn't make it right. Just explains it, instead of a throwaway "they're a narcissist." I've dealt with actual narcissists. This person doesn't fit the box. Regardless, bad call. The way someone treats the people closest to them is the way they'll eventually treat you. The clock just hadn't started. ------------------------------------ 2. I handed my thinking to AI. ------------------------------------ I let AI draft proposals without putting the same eyes on them I would've put on a 2019 proposal. Three different proposals from the same business in the same month, with three different ways of describing the same deliverable. Vague names. Duplicate items. One column literally called "SEO Content Alignment" that nobody on my team could actually explain to a client.

Quick follow-up to the email post from the other day — and a thank-you, because a comment I wrote spun in my head until something cracked open. I wrote something equivalent to "what Tony Stark's Jarvis is really about." It's been rattling around my head ever since, so I sat down and wrote out why. Short version: Jarvis was never an app. He wasn't even "an AI" the way we toss the word around. He was a brain that used tools — and that distinction is the whole game. The models and agents are tools. A pile of tools isn't intelligence. The intelligence is the operating system you build on top: how you structure your thinking, your context, your folders, so the system grows instead of resetting every morning. A lot of you here already know this in your bones — it's the ICM way of working, and this community runs on it. I just took it somewhere specific and wrote up what I found: Commodore 64s, why you can't sell a folder, and the questions worth asking before you save one more prompt to the pile. Full piece 👇 https://medium.com/@gabeyoga/you-dont-have-an-ai-problem-you-have-an-operating-system-problem-f281afd4fadd?sk=f2c32d59132ee83f0d92db44d5cb8c0c And the real question I'd love answered, not a rhetorical one: how are you each building your own operating system? What's the first folder you'd open, the first path you'd lay down? Tell me what you'd start with. I'll read every one.