Alright, I need to run something by you all. Jake and I have been talking about building something bigger. Not just more content. Something structured. Something with real accountability. Something for anyone who wants to actually build with AI, whether you joined this community yesterday or you've been here from the start. Here's what we're considering: The Lyceum — the original Lyceum was started in ancient Greece and known as the first school of Aristotle. Ours is a 12-week program with live instruction from Jake and other AI instructors from Eduba. Small cohorts. Real projects. You'd be building something from week one, not just watching tutorials. We're thinking three different tracks: - Technical — for developers, engineers, people building tools and systems - Business — for ops people, managers, founders, consultants who need to direct AI work without necessarily writing code - Creator — for content creators, marketers, educators, solo operators building their own production systems Same core methodology across all three. Different emphasis based on what you're actually trying to do. And here's where it gets interesting. We're thinking about making it a competition. A grand champion who gets a $100K build from Eduba. First, second, third place for each cohort. Demo day at the end where people present what they built. We'd also be issuing Eduba's first-ever certification. Something backed by the same methodology we've used to train Fortune 500 teams. This is still in the planning phase. We haven't finalized everything yet. But before we lock it in, I want to hear from you. Does this sound like something you'd actually want? Drop a comment. Tell me what excites you. Tell me what concerns you. Ask questions. If there's something you'd want to see included, let me know. More details coming soon! Eduba Case Studies: https://services.eduba.io/#cases

Claude Projects doesn't accept folders, only files. So the usual ICM layout (CLAUDE.md at root, /protocols, /reference, /templates, /examples) won't upload as is. What I did: - Flattened everything into a single folder. Renamed each file with its folder as a prefix, e.g. protocols/guardrails.md became protocols_guardrails.md. Keeps the origin visible in the filename. - Updated every internal reference inside the files so the File Map and cross-links point to the new flat names. - Pasted the body of CLAUDE.md into the Project's Custom Instructions field. CLAUDE.md has no special status in Projects (unlike Claude Code), so the orchestration rules need to live in the instructions box to actually govern behaviour. - Uploaded the other files as Project knowledge. Done. The File Map still works as a routing index. Early days but the structure holds.

I need to walk back this morning's announcement before anything else. @Ariel Ortiz is not a Premium or VIP member. The competition was Premium and VIP only, stated in bold in the original brief. That eligibility check should have happened before judging and it didn't. That's on me. The $325 and the Week 4 title go to @Ruby Sparks. The rest of the writeup stands. Repeating it here so the corrected results live in one place. ➖➖➖ 🏆 WINNER: @Ruby Sparks 🏆 🔗 Repo: https://github.com/sparkles-inc/agency-os 🌐 Live site: https://agency-os-tan-five.vercel.app/ Ruby was within an inch of taking it on the original call. The judging call between her build and Ariel's was the longest I've sat with on any comp. She earned this on the work alone. The Loom video she recorded for this submission is the cleanest voice work I've heard on any community submission. Full-on infomercial quality. Voice acting level. If you haven't watched it yet, go watch it. It's a master class in how to present a build. Beyond the voice: an animated handoff explainer on the companion site, a WRITEUP.md that compresses the entire submission into three paragraphs of clean argument, and a design philosophy made explicit. She refused typed schemas in favor of human-readable Handoff Cards with seven sections including a required Gaps field ("if Gaps is empty, you're not looking hard enough"). One continuous narrative thread runs through all 27 files of her repo. Ruby takes the $325. @Sonija Quinn will reach out to Ruby directly for payment details. Remember: in a world where AI is making it easier to build, it's the unique opinions and styles that become valuable. ➖➖➖ I thought last week was hard to judge. This was the hardest comp to judge so far. Not even close.

Drop your vote everyone! Might be fun to do monthly, like this post if you agree or want more polls like this. Enter your answer below or in the comments 👇

💰 $325 CASH 💰 That's a full year of Premium. Win this and your membership pays for itself. But the real prize this week isn't the cash. Keep reading. 📋 THE CHALLENGE You just got hired again. Meet Diana, owner of a 4-person boutique real estate team in Austin. 60-80 transactions a year, mostly residential, mix of buyers and sellers. 📎 Download the full client brief attached to this post. Short version: She doesn't want software. She wants a system she can teach her team to use in a week. Your job is to build the AI operating system for her team. This isn't one specialist. This is a small team of AI specialists organized into a multi-folder ICM architecture, with a clear handoff protocol between them. 🗂️ WHAT YOU'RE BUILDING Last week was one specialist. This week is a team of them. Required folders: 📍 00_orchestrator/ — The router. Where every request starts. Decides which specialist gets the job. 📍 01_lead_qualifier/ — First contact with new prospects. Captures intent, budget, timeline. 📍 02_property_research/ — Deep research on specific properties or neighborhoods. 📍 03_client_communication/ — Drafts emails, texts, follow-ups in the voice of the agent. 📍 04_transaction_coordinator/ — Handles the deal once it's live. Checklists, deadlines, document tracking. Each folder must include: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 🔗 handoff.md (NEW for Week 4 — how does this folder pass work to another folder?) - Plus a root-level README.md explaining the architecture, the typical flow, and how to onboard a new team member. 🔥 WHY THIS ONE IS DIFFERENT Weeks 1, 2, and 3 were warmups. This is the comp where the work you ship genuinely starts to look like the real thing. The handoff protocol is the test. Anyone can build five folders. The hard part is defining what each one needs from the previous one and what it passes to the next one. That's where multi-agent systems actually live or die.