Curious how others are handling file links in ICM-style workspaces, especially if you’re also using Obsidian for visual navigation. I’ve been trying to keep links functional instead of decorative. My current pattern is: - Index = where this file primarily belongs - Links = closely related files worth navigating with it - Source Of Truth / Pointer / Route To = operational links, not just visual links - Avoid inter-linking every mentioned file, because the graph gets noisy fast - Only add links when they help with routing, ownership, review, or resume context So the goal is not “maximum backlinks.” We want a graph that shows how the workspace actually operates. As I see it: Obsidian rewards dense linking visually, but ICM rewards narrow context loading. Too many links can make the graph pretty but semantically weak. How are you all deciding what deserves a link vs what should stay plain text?

Recently a lot of excellent community discussion around how to ICM. Having experienced rapid growth in my past, one of the hardest things to do is keep language and definitions aligned. If I say the Agent did this, where does your brain go? Lines get crossed because you have so many levels of understanding and perspective. Some people are coming from non-technical backgrounds and have learned through corporate ai marketing. Others coming from corporate environments where language is defined for them by the management and designers building their infrastructure. Mini cultures with their own language. One of the brilliant aspects of ICM is it's commonality with almost anyone on a computer. It's just a folder, from that foundation we can all get on board. What's difficult is what happens next. I had this conversation with claude during a planning session. Claude asked me did I want agents or roles? I responded back by did he mean an agent like claude or codex, which is really an LLM, a purpose built agentic piece of software that the market tells me is an agent that does stuff? Or a folder acting as an agent with a specific role. I didn't know what the underlying meaning implied, how to answer? So I asked here was the response. 1. Engine — the LLM brand (Claude, Codex, Kimi, Minimax). Raw cognition, rented capacity, the electrons. Interchangeable. 2. Agent — the ICM folder. Persistent shaped context: identity + rules + reference + memory + boundaries. A standing operator that exists on disk and endures across sessions. This is your "folders hold attention" — an agent is where attention lives. 1. Role — a lens/hat: a function performed at one step of a process. It exists only in the doing. Where attention points right now.