EDIT: WE HAD OVER 100 PEOPLE SIGN UP IN TEN MINUTES....GOING TO BE ROLLING OUT ACCESS ON SLOWER BASIS NOW SO I DONT RUIN MY BANK ACCOUNT WITH TOKEN SPEND FOR YALL (im covering ai costs for everyone) but keep applying we are keeping track and will be letting more people in and reaching out about getting you all access one by one especially VIP. Our Platform is here, the thing a lot of you have been asking for and I have been teasing Take your ICM folders and second brains, put them in the cloud, and work on them together in real time. You upload your folders and files. One strong model with a good harness reads the map and becomes the agent you need. No new agents to build, no zip files to pass around. Each workspace runs in its own container. It renders your markdown, edits your files, installs packages, runs Python and Playwright, and multiple people can work in the same space at once. No Mac Mini needed to keep your data separate either. We're opening it to VIP and alpha testers first, and I'm covering the AI cost while we test so cant do a full role out yet. Free AI use which is great for those users, not great for my bank account haha. ✍️ Sign up for access: https://docs.google.com/forms/d/e/1FAIpQLSdSnToxclxt8EgoB2GizrEvHP7gzOedVcRXdCkpi1SZwR8ZfA/viewform 🔗 Questions, or want to work heavier with this? Email info@eduba.io

Jake, I've been sharing ICM with folks in another AI community... we agreed there's something overwhelming about creating an AI that knows what files to read and when. (Over the last 90ish days I've worked from ONE single workspace aka folder for my entire business (divided into 10 departments) with 7.59GB and 98,537 items inside.. apparently "spring cleaning" is overdue) Not only that but the jargon in that group is that we build "agents" for nearly every single thing... workflow = agent skill = agent task = agent deliverable = agent I find the idea of "agents" more and more ridiculous the more I listen to you. To me, they seem more synonymous with a specific AI model than anything else. So, as I realize my own incompetence gap, despite attending your calls and nodding in agreement that ICM makes sense... I'm not sure how I close the gap. If I can't explain it - do I really understand it? Sincerely, An eager life-long-learner :)

Here's the problem, close to word for word from a client (they help with healthcare claim denials, so they handle very sensitive data): "We need to use AI smarter at our company. But we have real security concerns about linking Claude and ChatGPT to our Microsoft Suite. Without linking it, it feels like we can't really do much. And we pretty much cannot let it read or write any file on our computers, for security reasons." So two questions for anyone who's been near this: 1. What would you actually call this problem? 2. Who's the right kind of person to diagnose it AND solve it, and roughly how would they solve it?

Okay so it's 12am and I'm building Rooty, the app that's literally about helping stylists stop burning themselves out. And I'm sitting here reworking the same landing page for the hundredth time, slowly starting to hate every word of it. So my AI, the thing I'm building this with, tells me to go to bed. Basically: "you don't hate the work, you're just out of gas. Go rest, it'll look fine in the morning." Then my husband walks by and says the exact same thing. 🙃 So to recap: I'm making an app to help you stop grinding yourself into the ground, and it took my laptop and my husband ganging up on me to close it. The irony is noted. Goodnight, for real. 🌱

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