I have a client in Australia who's looking for someone who understands ICM and can help him work on his software. Obviously he would prefer someone a bit more technical, but he's happy to have some people who are trying to learn as well. It's a pretty large software, but he's created a pretty good automated system and obviously he's using my methods so it's very well organized. Anyone out here looking for a project to take on the practice or learn more? Or is there anyone in the morning to get a little bit more work done at a higher level? He's looking for multiple skill levels.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!

Rebuilt my ICM setup again, mostly because of Opus 5. This time the rules do not sit in documents. Wrote here twice before about this. It started with Opus 5. That one was by far the worst, it barely did what I asked and it ignored my own rule files completely. The other 5 models changed too, but Opus 5 is where it fell apart for me. First post I asked if others saw the same. Second post I said I had it fixed by rewriting all my rules in calmer language. That second post was too early. It ran well for a few sessions and then it was skipping rules again that it had read back to me two messages before. So I stopped rewriting rules and went looking for why it happens at all. What I learned is that a rule in a document is not a setting. It comes in like a message, and the model decides for itself whether it applies to the job in front of it. Getting the job done usually wins. And there is a limit to how much of it sticks, so every rule I added made the other ones weaker. That is why the same mistake kept coming back even though I had written a rule against it. On top of that, the one script I had that was supposed to block anything before my start steps were done turned out to have never run at all. After that I took the whole setup apart and sorted every rule by one question. Can a script check this or not. If a script can check it, it is not a sentence anymore, it is a script that blocks. If it only matters for one kind of work, it moved to its own folder and only comes in when I open that kind of file, so my script rules show up when I open a script and stay away the rest of the day. If it is a way of working I only need now and then, it became a skill that sits there as a name and one line of text until the task actually asks for it. Nothing was deleted, everything moved. The reading changed too. My big list files are not read from top to bottom anymore, they get searched. Two or three words, and only the matching line comes back. And every place where a document pointed at another document got rewritten. It used to say see file X. These models read that as a note about where something lives, not as go and read it. The older models filled that in by themselves, the new ones do not. Now it says what to do first and why.

most of my work is done in Claude Cowork sessions. I almost never use Claude code (CLI) and the challenge I have is that regardless of what I’d like to do unrelated to my work, Claude always defaults to my work profile. So if I use a Claude code, create a folder just for the specific unrelated search or idea, my .md file should be delivering all that knowledge about me separately with a proper context! Am I thinking correctly?!