Hey y'all, not a sympathy post. This isn't me saying I'm taking time off for anything. In fact it's the opposite. My grandma passed away last week and I was cleaning out her apartment with my mother and talking to my aunt (both of them it was their mother). I can tell they're struggling. It's why I work so hard honestly on the software community on everything else. Almost none of the money goes to me. I give it to my family, my wife my friends. It's what makes me happy. I'm building a company specifically so my family doesn't have to struggle. Been helping out where I can but obviously been focusing a lot on the business. My uncle also has cancer and so my aunt has been taking care of him and also at the same time dealing with a death of her mother . Best way I can contribute has been through cash and some love here are there. With that though means I don't always have the time to do what I need to do. So honestly, I'm asking for your help if you're willing to donate to my aunt's GoFundMe on top of the help that I'm giving. I've just donated a bit and would love other people to help out. To me, if I work hard I can make sure that my whole family is taken care of. But in the small ways I can help where I can I will do my best too And that goes with asking for help from others. So if you all could help me out help them out. That would be amazing https://gofund.me/45b6655ba

I just recorded a walkthrough of this but I want to lay it out here too. I've been building an instructor kit. A full folder architecture (yes, the same method I teach) designed to help people in this community create real courses. Not loose tutorials. Not "here's a tip" posts. Structured, formatted courses that fit into what we're building here and actually teach someone something useful. The kit has my writing rules, my lesson templates, a course outline system, sample lessons, and a prompt you can hand to Claude or any AI to help you write content that matches the community format. You can use it with Claude Code and a full folder setup, or you can just copy and paste a single file into any AI chat and start building. Both paths work. 🎯 Why I'm doing this. This community has grown fast. 12,500+ members. The courses I've built so far cover the foundation: folder architecture, the abstraction series, Claude Code, prompting frameworks. But I'm one person. There are people in this community who know things I don't. Who have built things I haven't. Who could teach topics I can't cover with the depth they deserve. The way I see it, Clief Notes should operate more like a university than a course platform. Sections and departments, each run by someone who actually has depth in that subject. Your course, your name on it, your expertise. I provide the structure, the audience, the format, and the quality control. You bring the knowledge. 💰 What's in it for you right now. I want to be straight about this. Early on, the main thing I can offer instructors is free VIP access for as long as your course is live and maintained. That gets you into every tier of the community, the live sessions, the recordings, the Discord, everything. As this grows and I can see what kind of attention and value the instructor courses bring in, I want to move toward profit sharing or payouts for instructors whose courses are driving real engagement. I'm still working out exactly how that looks. I'd rather figure it out with real data than promise something I can't deliver yet. What I can promise is that this will not stay volunteer-only forever. The goal is for this to be worth your time in every sense.

A question for those using ICM to provide software or consulting services: When you work with multiple customers, does one ICM system support all of them, with separate customer configurations, requirements, data, and outputs? Or do you create and maintain a separate ICM structure for each customer or software product? I’ve been thinking about this through the way I create my own products. I reuse many of the same standards, checks, scripts, and production methods, but different product types may still need different schemas and workflows. A devotional is not built exactly like a prayer card set, even though they share part of the same underlying system. I’m curious whether software providers (or consultants) approach this similarly. Do you maintain a common core and adapt it for each customer, keep every customer implementation completely separate, or use some combination of the two? I’m still learning how others structure this, so I would genuinely appreciate hearing what has worked for you—and where separation becomes important.

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

I explain the details about it on today's high tea . I built a Claude skill that turns a process, an idea, or a messy folder into an ICM workspace. The folder structure does the orchestration. Numbered folders carry the order, the hierarchy scopes context, and plain markdown files hold state. One agent walks the right files at the right time and does the work a multi-agent setup would. Repo: github.com/RinDig/icm-architect 📦 What it does Two modes. 🔨 Build. You describe your work and it pulls out the structure already sitting in how you talk about it. The stages, the points where you stop and check, what stays the same every run versus what is new. Then it picks one of five proven forms and scaffolds the smallest workspace that carries the job. ♻️ Restructure. Point it at a folder, repo, or vault you already have. It reads every file, sorts each one by role, shows you a migration map, waits for your yes, then moves and checks the result. 🧩 The five forms Pipeline, umbrella, record library, knowledge bundle, context map. They mix and nest, so most real workspaces use more than one. ✅ The walk test Every result gets checked cold. An agent with no memory has to open the root, find its way, act, and report status from the files alone. If it can't, the structure gets fixed until it can. ⚙️ How to use it You can honestly just tell claude to download it from the link, but if you're using codex or something else it will just have to restructure the claude.md to agents.md Or if you want to do more Hands-On install Claude Code: drop the folder in ~/.claude/skills/icm-architect/, then say "ICM this" or "build me a workspace for X." Claude apps: zip the folder and upload it under Settings, then Capabilities. Fork it, break it, tell me what you built. 👇