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

Everyone gets something wrong the first time. Vote below, then drop your mistake in the comments so others can learn from it.

Step-by-step interactive guide from idea to output. Design an ICM workflow alongside Maya, one decision at a time, and watch a messy process become something an AI can run again and again. Right now, Maya has to try to remember what needs to be done and where each piece of information is kept. She needs a better solution. https://claude.ai/public/artifacts/7c9618f4-8324-4048-902c-cbcf77c9c102 Let’s build one with her. 😀