Hi, anyone building a "second brain" / LLM wiki using ICM? I understand ICM is very good for defined tasks and workflows but what about using AI for researching and keeping general information? Currently I run a second brain with the following folder structure: - Inbox / | | Convert to markdown file with MarkItDown (deleted afterwards) V - Sources/ | | Using custom Wiki-ingest skill to extract important content and group by relevant topic | according to Google's OKF system | V - Wiki/ - Flat directory with derived knowledge from Sources/ An AI agent can navigate Wiki/ easily and efficiently using a separate Routing/ folder containing a INDEX.md file, which described which topics exists and a brief description. Each existing topic gets a <topic>.md file in Routing/ with links to actual pages in Wiki/ with a brief description. Anybody who has a similar or different system? I am curious to learn from all of you!

This is the only place I can talk local ai without getting blank stares, so let's actually see what everyone is running. I'll go first. here's the whole stack: HARDWARE ▸ Alita - personal dual-3090 rig at home. 48gb total vram, 128gb ram. kept totally separate from anything work related. MODELS ▸ primary: qwen3.6-35b-a3b on gpu0, served by llama.cpp. mixture-of-experts, ~3b params fire per token. q8 kv cache, 256k context. ▸ router: a ~9b qwen on ollama out front, deciding what's actually worth waking the big model for. ▸ embeddings: qwen3-embedding 0.6b and nomic-embed-text, same ollama instance. AGENT LAYER ▸ hermes, running as Alita here. three daily jobs: morning brief, work email summary, personal email summary. all land in discord. ▸ weekly maintenance runs on a different scheduler with hermes as the watchdog, on purpose. runner dies, watcher yells. watcher dies, the daily jobs go quiet and I notice. two failure domains instead of one. MEMORY ▸ obsidian vault as the source of truth. ▸ hybrid search over it - bm25 plus local embeddings, running in-process. no extra service to babysit. ▸ qdrant for the vector-store work that actually needs one. INTERFACE ▸ the observatory - a front end I built over the vault. not a dashboard. a command center I actually work from: projects as boards, sessions as a timeline, drafts moving through a publishing pipeline, all of it reading and writing the same markdown files. The one piece I would not give up is the vault. the models change every few months. the notes are forever. The thing that taught me the most had nothing to do with hardware. I did kill a pile of containers nothing was consuming - n8n, a web ui, a couple databases - but that was housekeeping. the real one was giving up on folders. I spent a long time sorting notes into the right directory and it was wrong again six months later. Now every note carries its own frontmatter and the folders are just a cache I regenerate from it. Type isn't a folder. Status isn't a folder. The structure lives in the file.

Been heads down on something the past month plus. Not a lesson, nor a Tea round but more like the layer under all of it. Kept seeing the same thing in comments and onboarding calls: People not knowing where to even start or if something’s already been covered somewhere in here. We're working on fixing that. Not ready to put it in your hands yet.

The 60/30/10 Applied series is up. Three lessons. The 60/30/10 Applied — Lesson 0: Overview - The Vault · Clief Notes I want to explain why this one's behind the paywall because most of my stuff isn't. The free course teaches the framework. These lessons open up my actual consulting business out side of skool, Less about AI Fundamentals and more a deep dive into my past and current Enterprise Projects. Real contracts. Real pricing. Real revenue share clauses. The engagements I run through Eduba, my technical consultancy. I'm showing you how I scope, price, and protect builds that generate six figures from single partnerships. That's not something I put on YouTube or else where. You being here as a premium or VIP member is what keeps the free stuff free. This is me giving back to you specifically with the things I'd normally only share across a table with a client. Three lessons, each one a different angle on the same ratio. Lesson 1: The Build. A compliance platform in the DRC. Five agents, 160 hours to 5 minutes, and how the ratio determined every contract decision. Lesson 2: The Partnership. A $31M ARR consulting firm. Cold LinkedIn DM to $300K+ partnership. The ratio applied to the deal, not the code. Lesson 3: The System. The training funnel underneath both. 95% adoption. The flywheel. My own business broken down layer by layer. Each lesson has a course companion with exercises you run in Claude on your own work. Start wherever fits you. More coming. Edits rolling out over the next couple months. Tell me what landed and what needs to go deeper.

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?