Hey ppll I may have jumped n deep shit tech wise I'm a bit retareded. So 1 agent can run for say 10 clients. I'm lil confused on how I set it up. Lol simply put I been struggling to connect Claude to discord finally got it after 1day 1/2. Can I please trouble someone for clarification please?

Hey all. You've probably noticed it's been quiet in here the last couple weeks, wanted to explain. We've been building something for the community, and travelling at the same time to meet with investors and a few clients. We've also been busy getting the Lyceum ready. So less posting than usual, but for a good reason!! We're announcing the thing this week, and there'll be more info on the Lyceum coming out this week too. I think a lot of you are going to be happy. We've been grinding nonstop to get this ready. Before we do, we want to hear from you. If you're Premium or VIP, what's missing for you right now and what would you want us to add? If you're not Premium or VIP yet, what would actually make you want to upgrade? Form's here, takes about two minutes: https://forms.gle/MM8PLn2f6An1dfEUA It's open until Sunday June 21. Looking forward to reading everyones answers! Back soon with the news :)

After watching the video and reading the companion: Vote below, then tell us in the comments: what is one task in your work that feels robotic? If AI handled it tomorrow, what would you do with the time?

After watching the Flagler workshop and reading the companion: Vote below, then tell us in the comments: where did you land on the PhD thought experiment?

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)