Two Engineers on Why Your Agent Demo Will Not Survive Production

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

We just shipped the alpha of Ledger 📋 —https://ledger.eduba.io the talent platform we've been building on top of this community. Free for VIP and Premium Members. Here's the idea, plain: every other job board matches on a resume. Ledger matches on ICM. Every candidate in there has been through the methodology you're already using here — that's the whole point. Companies aren't guessing whether someone "gets it." They know it going in. 🎯 It works kind of like a job board, but more anonymous — right? 🕶️ Employers see an anonymized profile: skills, bio, portfolio, a short video intro if you want one. No last name, no email, no current employer. Every conversation runs through the platform's relay instead of real inboxes, so nobody's exposing contact info before they're ready. Two doors in: - 🏢 Company hiring — freelance or full-time — sign up and get access to a pool of people who already speak ICM fluently. - - 🙋 Candidate looking for work — freelance or full-time — list yourself. Takes a few minutes: profile, skills, a short video if you've got one. We're vetting both sides before anyone gets full access — companies and candidates — so the quality holds up on both ends. ✅ That means it's not instant approval; you might wait a beat while we look at it. Bear with us there. It's alpha 🧪, so: things might be rough around the edges, we're watching it closely, and if something breaks or feels off, tell us — that's exactly what this stage is for. Be nice to us and we'll be fast about fixing it. 🙏 Sign up: https://ledger.eduba.io 👇

Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)

I had an philosophical epiphany while thinking about the 60-30-10 Principle. People say we only use 10% of our brain. That's not quite right. We use all of it. But only about 10% is actively engaged in whatever we're doing at any given moment. That detail stuck with me when I started thinking about how we actually 'get things done' in our 'jobs to be done' physical world. In our embodied world, things get done when we coordinate and align our 'head, hands, and heart' / 'our rational, agency, and motivation'. While going through @Jake Van Clief 's training, it hit me. The '60-30-10 Principle' is how we get stuff done in the digital space. - 60%, the infrastructure, is the physical space. The thing that actually has to happen. Most of what we do lives here. - 30%, the orchestration, is the directional motive. The drive to move. The pull of motivation. The direction, the reason we start, the reason we keep going, and where. - 10%, the AI, is intellectual. The processing. The planning. The "how do I think through this" layer. *I know, it's a stretch, but follow me just a little bit more.* Here's the part that surprised me: that 10% — the smallest slice — burns the most energy relative to it's size. Which means if you can get more efficient with how you think, you don't just think better. You perform better across the whole system. The 60 and the 30 move easier when the 10 isn't burning out. This isn't just a productivity idea. It's an embodiment principle. Jake is showing us how to apply this in the digital space. Again, I know it's a stretch, but... it's a relevant take on the 60-30-10 Principle worth sharing.