Been sitting on this for a few weeks and figured it's time to show you. 👀 Over the last month, three companies have reached out asking the same thing. How do we hire people from Clief Notes. They've seen what folks here are building with ICM and they want that on their teams. Not LinkedIn AI experts. Not Coursera grads. People who can actually ship. So we're building it. 🛠️ talent.eduba.io Heads up, that's a demo. No real backend, no signups, no live data. Click around and you'll see what the full thing is going to be. A private platform where you list yourself with a real portfolio, companies browse, and they request an intro through us. We make the intro. You take it from there. Few things worth knowing. 🔍 Every profile gets reviewed by the Eduba team before it goes live. The quality bar is the whole point. 🔒 Companies don't see your last name, your employer, or your contact info until we make a formal intro. You can block your current employer too, plus five more companies if you want. Nobody you don't want seeing you sees you. You can list as actively looking, open to offers, or not looking. Passive welcome. Honestly most of the strongest people we've trained are employed and plan to stay that way until the right thing shows up. That's fine. Sit on the platform, see what comes through. 💰 When a placement happens you get a $500 to $1,000 bonus after 90 days in the role. On top of whatever you negotiate. We pay you for staying. This is why the community matters. Companies aren't asking us for resumes. They're asking us for the people who already get it. ICM, agent architecture, knowing when not to use AI. That's not on a LinkedIn profile. Go click around. Tell me what's missing, what's confusing, what you want to see when the real thing ships. We're already building it. 🚀

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 💻 Code review editor for a specific language and level (junior TypeScript, senior Python) - 📊 Pitch deck editor for pre-seed founders - 🎨 Grant application editor for arts nonprofits - 📄 Resume editor for career switchers into tech - 📰 Op-ed editor for policy publications - 🎙️ Podcast script editor for interview shows - ⚖️ Legal brief editor for civil litigation - 📋 Product spec editor for early-stage PMs - 🎓 Academic paper editor for one specific field The more specific, the better. "Writing editor" is too broad. "Op-ed editor for tech policy publications targeting a policy audience" is right. 🗂️ 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 editor is a folder with five things: - 📄 identity.md (who the editor is, what work they review) - 📐 rules.md (how they critique) - 💬 examples.md (what good critique looks like) - 📚 reference/ (style guides, checklists, frameworks the editor uses) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the editor. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK An editor is NOT a rewriter. An editor doesn't do the work for you. An editor surfaces what's weak and pushes you to fix it. That distinction is the whole assignment this week. When someone hands the editor a draft, the editor shouldn't produce a "fixed" version. The editor should point at the three lines that don't work, explain why, and hand it back to the writer to solve. ✍️ Generic feedback like "consider strengthening your intro" is a fail. Specific feedback like "your intro assumes the reader already knows what a Series A is, but this pub is read by generalists, so lead with the stakes instead of the jargon" is what a real editor does.

If any of you are following the news... Open AI, Anthropic and SpaceX are going public. This rush to IPO has me downright depressed... Investors want the return that they aren't getting. Companies are starting to tell their employees to stop using ai to complete tasks as token usage and API costs are going through the roof without the productivity they were sold. They'll need to cut costs in order to incentivize companies to use their models, but in order for investors to get their money costs have to go way up. Data center investment is crazy. I work for a company that supplies electrical/construction supplies and services to build them. Sparks/Reno is exploding with California investment. Original investors want to get out via actual liquidity supplied by the most unprecedented IPO we've ever seen, otherwise they'll default on years of deals. All the insiders are rushing to the doors while regular people are hoping to get a piece of the pie of these "trillion" dollar companies.. who is going to be left holding the bag if the financial institutions plan on using 401ks and pensions to fund these insane IPO's, and funding the investors ability to cash out? Are we on the precipice of the largest bubble pop in history? Sorry for the doom and gloom, I've had the most fun I've ever had building with these tools, but this forum is all things ai, right? I can't help but think our access to these platforms will change drastically very soon; and the bigger picture is much more bleak.

I developed a software product some time ago with assistance from AI and recognized an opportunity to market it to a local entertainment business. However, this will be a cold approach, as I have not previously engaged with them in a business context. The product is designed for a single use sale. Do you have any advice that might help me enhance my cold email outreach? Additionally, have you evaluated your cold emails using any publicly available AI-enabled service aligned with the principles of the Mom Test? Thank you for your input.

🎟️ 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)