My Cousin @Ryan H. was tasked with making me a new logo for the group (the old fashioned way, not much AI help here) and I think he SMASHED it out of the park. Perfect nuance, what do you all think?

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

📦 AND SOMETHING NEW: EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 WHAT WE DID DIFFERENTLY THIS TIME Every submission was cloned at the exact commit that was public when we read it, and read file by file. The brief. The identity. The rules. The reference layer. The code. Where a repo made a claim we could check, we checked it. Arithmetic recomputed by hand. Sample photos opened and compared against the outputs that cited them. Files diffed. Self-tests traced. Thirty-two repos, read at the code/word level. And one lens over everything, because it's the lens this whole community is built on: does the build keep the human's judgment where it pays and put the deterministic work in code, where it can't hallucinate? 📦 THE FEEDBACK PACKAGE This is the new thing, and it's for everyone not just the podium. 📦 COMP #8: THE WILDCARD - The Vault Every entrant gets a markdown file. Three parts: 1️⃣ The read. What your build actually is, and the strongest thing in it cited to your own files. Rule numbers. Function names. Your own examples. 2️⃣ One push. The single change that most improves your build. Not a list. One. 3️⃣ An idea worth naming something original in YOUR build, credited to you, that the rest of the community is told to take from. Plus links to the builds your feedback points at. Nobody walks out of this comp empty-handed. Thirty-two builds, thirty-two named ideas. The roster alone is worth the download. 📍 The package + the full write-up (what held up, what was missed) live in the new Feedback module: 📦 COMP #8: THE WILDCARD - The Vault 📚 WHAT THE FIELD TAUGHT Three lines split thirty-two repos: ✅ Enforcement. A must in a markdown file is a request. A must in code is a constraint. (That line is from one of your repos. It's in the package. Go find whose.) ✅ Evidence. The builds that shipped receipts of a REAL run transcripts, dated logs, before-and-after fixes read differently every single time.

Just real quick, I’ve been writing something since the end of May in varying fits and starts, and I think I’ve got it to a first rough cut position after some close friends have fed back. And this community felt like a good natural place to get some next step feedback. The title is “AI isn’t the problem, business maturity is…” Have done some media engagements/interviews for security and governance based things, but I’ve never put something like this out in the wild before. And since joining here a few weeks ago, it’s spurred me on. I’m just tarting up the visuals on it, but I had two questions before I do: 1. Posting here is fine yes? 2. I have cited the ICM paper @Jake Van Clief did as one of my supporting/ reference materials. Is that okay? These might be silly questions, I just wanted to observe a level of community etiquette before doing anything 😌 Wasn’t sure which category this should go in, likely general for this question and assuming it’s okay, “Show your work” for the paper?

Good evening all, I’ve been working on a white paper / article over the last few months and wanted to share it here first before I consider putting it anywhere wider, such as LinkedIn. The title is: AI Is Not the Problem. Business Maturity Is. I’ve done some media pieces before, but nothing this substantial, hopefully it lands well, I have reached that point where any more tinkering without external feedback risks bloat or dilution. The core argument is that the next phase of AI adoption will not be won by the organisations with the most tools, licences or model access. It will be won by the organisations mature enough to turn AI usage into measurable, governed value. In amongst the 16 citations used to support this, beyond my lived experience, I’ve cited @Jake Van Clief and David McDermott’s ICM paper in Section 6, specifically around context architecture. That framing was genuinely useful to the way I developed part of the argument, so I’ve attributed it directly and linked back to the source. Joining this community a few weeks ago spurred me on to go back and finish it properly. A fair warning 🙈: it is a proper read. My gut is telling me, too much and that I may need to break it into smaller associated parts; they are all relevant to one another though. The PDF is formatted, but it is still a paper rather than a polished visual article. If I get feedback, I may make some final edits and then will turn it into something more visually engaging, so if you make it through in its current format, you have my thanks 🙏🏻🙂 I’d really value critique from this community, especially on: Does the argument land? Does it feel useful to practitioners rather than just theoretically correct? Are there any claims, citations or sections that feel weak, overstated or unclear? Appreciate anyone who takes the time to read it properly! 🙏🏻👊🫶