This is a devlog from David! A lot of people are saying they want the ability to scale and deploy their ICM and their workflows. We looked at all the possible problems security issues and we have been spending a lot of time building something for all of you! It's almost ready for release, but here's a little developers log to kind of check out some things that David has been doing to build it up. It's far from perfect, but for those technical folks out there you may enjoy it!

🎯 WE READ ALL OF YOUR RESPONSES. HERE'S WHAT'S NEXT (AND A BIG ASK) A couple weeks ago we asked you what you wanted Clief Notes to become. You showed up. You wrote real, thoughtful answers, some of you wrote essays. We read every single one. Twice. So before anything else: thank you. This post is us answering you. 💬 YOU TOLD US. HERE'S WHAT WE'RE BUILDING. You said you want a clearer path from learning ICM to actually getting paid for it. → It's coming. A real learning-to-earning track, plus a talent platform we're building to connect you with people who want to hire what you can do. Heads up: the talent platform will be Premium and VIP only, one more reason to lock in below. You said competitions without feedback don't help you grow. → Fixed. Going forward, every single entrant gets tailored feedback on their build, not just the winner. We're moving to two competitions a month so we can do it right. And both monthly winners get a 30-minute call with me. You said the best builds get buried in the feed. → We're building a tagged library so you can actually find "ICM setups for solo operators" or "small team, non-coder" instead of scrolling for an hour. You said you couldn't map all the pieces, Skool, Discord, the Lyceum, ICM, what each tier unlocks. → A single orientation page is on the way. One place that breaks all of it down so nobody's lost. You said you want to connect with each other. → We hear you. Meetups, pairing, and a recorded "After Tea" hangout are on the table. South Florida alone has over 1,000 of you. Let's use that. You said we've felt spread thin. → The most honest one. You're right. We're bringing on real help to run the day-to-day so the community gets consistency, and so Matt and I can keep building the things above instead of dropping balls. You called it, and we're fixing it. 📍 QUICK NOTE ON ICM: a few of you asked for "ICM with Copilot" or "ICM with n8n, Sheets, GoHighLevel." Good news, ICM already works with any model and feeds straight into the tools you're using. It's the structure underneath all of them, not a separate thing you have to relearn per tool. If that's not landing for you, that's on us to make clearer, and we will.

Three months in this community and I kept losing things. Someone would post a tool in Show Your Work. I'd think "I'll come back to that." Then it was buried under 40 more posts and I couldn't find it again. @David Vogel and others have built some great workarounds to highlight posts and info, but I wanted to put together something that helps me find those tools I'll otherwise flag and forget. So I scanned both categories and built an index. 72 tools. 7 categories. Standalone HTML file: open it in any browser, no login, no server, no account. What it does: - Real-time search by name, author, or keyword - Filter by category (Memory, ICM, Writing, Design, Media, Workflow, External) - Every card links to the original post and the GitHub or site - "Leave Review" generates a formatted reply you paste into the original post - "Submit a Tool" generates a post template for Resources & Finds What's in it: Memory: PMM, Cortex, Session Memory Layer, Codebase Memory MCP, and a non-technical PMM folder template for people without a dev background. ICM: Brofessor, ICM-Builder, Foundations Tutor, CoworkOS, IBE Workflow, Shipyard, Creator Orchestrator Template, PAFA, and more. Writing: Critical Editor, Council of 5, LinkedIn Content Wizard. Design: tastecheck, Weirdness Engine, Open Design, art-direct, Shade_. Media: to-md, TypeWhisper, YouTube Extraction Pipeline, Pushing Talk_. Workflow: ARI-OS, Astrid, SkillOpt, Nightwatch, Porter, The Maintainer, Subscription Auditor, and more. External: Miessler's PAI, Hermes Agent, Zuki, Signal Harmonics, GiTeam, and others. GitHub (open for contributions): https://github.com/FiSimply/clief-notes-index The README has instructions for adding via PR or the Submit button. Anything I missed, drop it in the comments & I'll add it. If there's a better way to accomplish this inside the Skool site, please comment. My way is not "the way" and I'm always open to alternatives.

@Matthew Dave , told you I'd write a post about the thing to watch out for with Claude and going with GitHub. Grab a coffee, I'm gonna grab the Bourbon. This one's got a body count. First thing, so nobody gets the wrong idea. This is not a confession post. Not mine, anyway. The only one confessing here is Claude, and I'm just the guy holding the recorder (and the M16 pointed at my Claude install). This is a rage post. Unfortunately, I'm hot about it again, and by the end you'll know exactly why. Quick refresher. I run my whole company out of a folder system. Not one big repo, a whole pile of them, one per slice of the business, all syncing to the cloud so my team sees it, my machines pull it, and nothing important lives in one fragile spot. The agent that's never lost. You know the gospel, we preach it in here every day. Here's what has me seeing red. My agent has been stubbornly losing things for weeks. In the same spot. And I knew about it. It knew about it! Here's the bug, in plain words. Claude has a private home folder on whatever machine it's running on. That folder is NOT in my repo, or yours. It never syncs, my team never sees it, and if the machine dies it's gone. And the AI's lazy little instinct is to save its work THERE instead of in my actual folders. Every time it can get away with it. I did not just stumble onto this, been dealing with it for weeks. I HATE this bug. A couple weeks ago I blocked out a whole work session just to kill it. Wrote a standing rule into my workspace, added patches, watched it behave, closed the laptop thinking it was handled. It nodded along the whole time. It said sorry, took the blame, said it would never do it again. Said all the right things. Cool. You know what happened today? A contractor I'm working with tells me three of our automations are done. Sweet. I go to open them. They're not in the repo. They're sitting in the AI's private home folder on HIS laptop, invisible to me, running against HIS accounts instead of mine. The exact bug I "fixed" two weeks ago, back from the dead, wearing a new hat.

Search finds. It never reads. Every "AI that knows your stuff" runs the same trick: embed the material, grab the paragraph nearest your question, bluff the rest. For easy questions the bluff holds. For the ones that matter, it doesn't. So I'm building the missing layer. Call it a reading swarm. Instead of paying one expensive model to read a whole mountain, I cut the corpus into slices and send a swarm of cheap workers, one per slice. Each reads its slice properly and hands back a single finding. A deterministic harness merges them into one verdict. The expensive model only steps in if I ask it to sharpen the final call. Not shipped yet. Still smoke-testing the edges, and I read every verdict myself. But the law already holds: finding isn't comprehending, and comprehension doesn't need a bigger brain. It needs more cheap eyes, one slice each. What's the biggest pile of material you wish your AI actually read, not skimmed? //A<3