Hi, I’m a VIP member, but I recently noticed that I no longer have access to the VIP Skool community and its locked classroom sections. I also joined the Lyceum training program, which includes VIP access, so I’m wondering whether the change may have affected my existing membership. Could you please help restore my VIP access? I’d especially like to review the results from the most recent competition, along with the other content in the locked classroom areas. Thank you for your help.

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

Seven weeks, 155+ entries. Every link that exists. This covers everyone who entered. If you're looking for ideas on what the community has shipped or want to explore what people built in a specific week, this is the place. If your entry is missing or a link is broken, drop it in the comments please and thank you. WEEK 7️⃣ : THE OPERATOR Build a folder-based AI operator that handles one operational workflow end-to-end. The operator must make decisions and route work autonomously, not ask the user what to do. Prize: Free Lyceum seat. Brief: https://www.skool.com/cliefnotes/weekly-comp-7-the-operator 🏆 Winner: TBA (announced Monday June 15) Honorable Mentions: TBA Other entries: Gabriel Azoulay - Nightwatch (on-call alert triage: PAGE / TICKET / SUPPRESS / FLAG scored by business impact, not alert label) - https://github.com/NFTYoginis/nightwatch | Live: https://nftyoginis.github.io/nightwatch Arjen Stet - Porter (inbox operator for project managers: one of seven outcomes per email — card it, update, reply, file, decline, filter, or flag — with confidence shown and the rule that fired) - https://github.com/astetic-dev/porter-intake-operator | Walkthrough: https://youtu.be/V3rkvH7QL6w Toby Iverson - The Maintainer (GitHub issue triage: categorises issues, checks against spec/roadmap/changelog, drafts labeled replies or escalations) - https://github.com/BytesFromToby/The-Maintainer Toby Iverson - RepoRouter (second entry; live on its own repo — go report an issue to test it) - https://github.com/BytesFromToby/RepoRouter Sunny Singh - Subscription Auditor (KEEP / DOWNGRADE / CANCEL / FLAG per subscription line, with savings total and dated action plans for annual-plan traps) - https://github.com/ms-codehorizon/subscription-auditor | Live: https://ms-codehorizon.github.io/subscription-auditor/

Really curious to see what the community thinks about this. Basically all it’s doing is giving you access to run your own agent. So you might as well run your own ICM in Claude code, right? According to their terms, the user takes all of the risk for the platform making errors and hallucinations. What do you think, are you in? Note: this isn’t financial advice and I don’t work for Robinhood