1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

We just broke 40k Members, in less then 4 months... To say I am honored and blown away is an understatement. I feel like yesterday @Matthew Creamer quit his job to sleep on my floor and bust out 15 hour days to build out content, structure and anything else I thought you all would need to make this community worth it. But at the end of the day there is only one thing for me to say. THANKYOU None of this, and I mean NONE of this would be remotely worth it if it wasn't for you all. To list and tag everyone that have contributed so much valuable not just to this community but to me would be nearly impossible. Thank you to every single one of you. Thank you for commenting and helping out on posts Thank you for sharing the wins you have gotten both at home and professionally. Thank you for believing in me and what I am building septically those of you who have been around since the beginning (you know who you are). I cannot tell you how happy my heart is to get in front of you all and teach, talk, ask questions and even learn a lot myself. It is a dream come true to become someone that people can learn from; to share my thoughts and have those very thoughts change the way people live their lives and do their work. It's only the beginning too, I can't wait to see what the rest of the year has in store, and I promise to keep building, working and recording for you all. From the very very very bottom of my heart.....Thankyou! Thankyou to every single one of you reading this and for being part of such an amazing community.

I’ve managed to convince one of my closest friends @David Chalk to come join us and learn stuff. I’m saying he’s player 2, because I was totally here first, but in real life where we’re pretty similar he keeps reminding me he is the original… Some of you may remember him as my friend who gives me “frank facts”. 🤣 I have promised to help build an ICM system to help him with some things and encouraged him to get some information directly from the source… because he’s totally going to want this built in a way that works for him. So, short version, please be kind to him and help me say hi. I am willing to open predictions on how long it takes for him to come up with good sim racing use cases for ICM while hanging out with this community… I don’t think it will take very long. Also… are we actually some kind of AI cult? Asking for a friend.

@Jake Van Clief Is anyone else working on this? I already had my 11Labs agent plugged into an n8n workflow, with a Supabase DB being utilized for memory and context, and I'm now wanting those interactions to initiate the local Claude ICM architecture to actually get the work done. That way I can call Natasha from anywhere and just make things happen. Is this a novel idea or are other people here working on something similar? Why are we typing nonsense into Claude, I want to just talk to it when asking for production elements and I can still the interface for more complex development. But I'm trying to build a production powerhouse. Once setup the requests for workflow should be simple asks. Claude is giving me a way forward by running a local server. Thoughts?

Recording's up, and I packaged the whole thing so you can drop it straight into your second brain or hand it to your AI. 🍵 Here's what we got into this session: 🧠 Map your work, don't just store it. A second brain holds notes. A map holds your work plus the people and data around it — teams, processes, and the links between them. You can't improve what you can't see, and neither can your AI. 🔗 Every workflow is a node. One markdown file = one process. The references between them are the edges. That's the whole graph. 🟢 Build workflows, not outputs. Store the outputs inside the workflow. Then when Opus 4.8 or Fable ships, the right feeling is "cool, my system just got better" — not scrambling. 🔍 Google basically proved the method. Their new Open Knowledge Framework (dropped June 12) is markdown + files + front matter to document and query big datasets. One of the biggest players outside Anthropic is doing the markdown-and-files approach we've been practicing here. 👀 🏛️ Plus: mapping a real company's teams in Obsidian, the platform coming so you can own and license your workflows, and a sneak peek at my new paper — Human in the Compute Layer — built on Engelbart's 1962 work. 📎 What's attached (and what each file is for): 📝 session-notes.md — The opinionated version. All the ideas from the call, written so you can act on them. Start here if you want the short version. 📚 term-sheet.md — Plain-English definitions for every term: node, edge, semantic layer, OKF, ICM, "the data becomes the agent," and more. Perfect if you're new to the room. 📄 vault-page.md — The index for the whole package. 🗂️ Package.zip — Everything zipped, ready to add to your AI's memory (Claude, Hermes, OpenAI — whatever you run). 💬 Watch it, grab the files, and drop your questions below — the best ones seed the next Afternoon Tea. So much love. 🫶