Sometimes when I'm on the go, I don't want to spin up Cursor or Claude on mobile because I don't have the time to think through the prompt or my workspace, and I don't want to waste the tokens on my mobile device. But something I'm constantly doing is telling Gemini (in Google search), or Haiku (in duck.ai) to not: - Lie - Ground its answer 100% on facts - No abbreviations - No Jargon ... and so on. You get the point, and I started thinking it would be really nice if I could use a workspace in the browser, but then I hit two road blocks: 1. The browser only accepts files, not folders. ICM is files and folders, so there's nothing to upload. 2. Even if I get it in there, how do I get the chatbot to actually walk the workspace instead of just reading it? Both are solvable: Roadblock 1: one file, not a folder. I was hoping the browser agents would accept a markdown file, but that didn't work and the ai model would respond with a timeout. Then I tried a text file, same problem. Then I noticed that models would accept PDF as a format. So then, I flatten the whole workspace into a single file, stamping each file's path at the top of its contents so the model can still tell the stages apart. Nothing is lost. The router, the stage contracts, the references are all there, in order, in one upload. Roadblock 2: getting the chatbot to run the workspace. I put one instruction at the very top of the flattened file: when my message starts with >, treat everything after it as the request and walk the workspace on it. Then I upload the file, type > and whatever I need, and the chatbot runs the pipeline instead of describing it. So now, on my phone, from a plain browser tab: > how far is the moon from earth comes back ground-in-facts, no jargon, no abbreviations, every rule I wrote once, applied automatically. No Cursor, no app, no wasted tokens. So, at first I wrote a workspace that prevents drift and I don't have to repeat myself. Then I got to thinking, this would be nice for typing in a city, and getting the latest news, city stats, real estate postings etc by using this, and this idea would really stress test if this concept works on ai search.

I have been living inside ICM for a while now, and it changed how I build. Recently I started pairing it with one more idea, and the combination clicked hard enough that I wanted to share it here and see what you all think. Quick version: ICM 2.0 = ICM (the interpretable filesystem) + Colibri style routing (a router that only wakes the experts a task actually needs). One gives you a system you can read. The other gives you a system that stays light. Together they run local and sovereign (this system build ACTUALLY helped me move the needle, i.e. KPI, creating content, closing deals, etc) --- 🗂️ First, why ICM already wins For anyone newer to it, the core of ICM as I understand it: 1. The filesystem is the operating system. Plain-text steps, one job per folder. No black box. 2. It documents itself. Every folder says where you are and what is next, so you never lose the thread. 3. It is resumable. Close the laptop, come back next week, pick up exactly where you were. 4. It is portable. What runs in your head, in an agent, or on a local model is the same folder of plain steps. The magic is interpretability. You can always open the box and see the reasoning. 🐦 The piece I added: Colibri (the router) The problem with a big system is that it gets heavy. You do not want every folder, every expert, every context loaded for every task. A hummingbird does not flap every muscle to hover, it uses only what the moment needs. Colibri is a mixture-of-experts idea applied to a whole life or business: 1. Only a sliver is ever active. Roughly 5 percent at a time, not the whole library. 2. A router picks the ~8 experts the task needs** and wakes only those folders. 3. Core stays pinned, the rest streams in** on demand and caches while it is hot. 4. It learns to predict which experts you will reach for next, so the right context is already warm. 🧬 Put them together and you get ICM 2.0 1. The ICM filesystem becomes the DNA / schema** — the canonical map of every expert the system can call.