Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.

Most ICM setups I see here are single-operator: one person, one agent, one context tree that's basically externalized working memory. We're running it differently — as the shared know-how of a small engineering firm (~15 people: industrial automation, control-panel building, light EPC). That one shift, from personal to organizational, changes the whole problem. In a company, the context isn't just my memory — it's the procedures everyone has to follow, and procedures have to be governed, auditable, and improvable by people who will never open a terminal. Here's the core of what we've landed on. One markdown source, three readers. The ICM KB — plain markdown in GitHub — is at the same time: - the agent's operating context (what it reads to act: load costs into the ERP, build quotes, enforce the process); - the company's procedure manual, rendered into a navigable wiki — search, cross-links, the graph of how procedures interconnect — which is what employees actually read; - the ISO 9001 controlled-document system, because Git already is change control: versioned, attributed, diffed, immutable — stronger than the Word-on-a-shared-drive most small firms limp along with. No parallel copies, so nothing drifts. Git is the evidence vault; the wiki is the auditor's reading room. (Worth stating for this crowd: ISO 9001 mandates control — identification, approval, versioning, availability of the current version — it mandates no specific format. A git-backed static site clears that bar cleanly.) The agent is the abstraction layer — this is what makes it survive in a company of non-technical people. Nobody learns markdown, Git, or pull requests. They talk. The agent enforces the current procedure while they work; and when someone says "step 3 is wrong, we do Z now," it turns that into a proposed change to the controlled document. The quality lead gets a plain-language summary and approves or rejects. Proposing is frictionless and open to everyone; approving is a controlled human gate. The Git/PR machinery stays invisible underneath.

This post is not about ICM, it's about learning the AI systems you are using in the ICM space. If you are new to ICM and you are looking to learn the structure and how to apply it, please see the posts below: (They will serve you well) 1️⃣Jakes Van Clief's Welcome: https://www.skool.com/cliefnotes/welcome-to-clief-notes-heres-where-to-start-2?p=f8f85a09 2️⃣Mira Bradsaw's collection of getting started: https://www.skool.com/cliefnotes/clief-notes-gems-for-starting-in-icm?p=0385cbf9 |---------------------------------Let's Begin---------------------------------------| 👇 📝Note: This post is not for people already working in the space, it's not for people who understand AI, it's for the people who are sitting in silence, watching the rest of us do those things. 🚦So, let's get started with real talk about what AI is here. A lot of smart people are quietly carrying around one perceived embarrassing question, what actually IS this "AI" thing everyone keeps talking about? If that is you, drop the embarrassment right now. You are not behind; we are all on the frontier of this thing called AI. The word AI has been stretched to mean everything and nothing, and there are many reasons for it, I will name the three reasons I see that create the most fog: 1️⃣People rushing to break into AI before they get it. 2️⃣People holding one piece of the puzzle like it is the whole thing, then screaming "I'm right!". 3️⃣People who just want to sell you something. If you notice a pattern, so did I and it's not the AI, it's the people pushing it! None of them are trying to make YOU capable. And that is why I love @Jake Van Clief and his team for creating a community which actually is! Today I start a journey to help remove the fog. 👇 The one-sentence version: AI is software that "LEARNED" to spot patterns from a huge pile of examples and uses them to make a good guess about something new. 💡