High tea at 3am is kinda rough. Are there a lot of us in my timezone? Anything we could do for our region or best to just watch the recordings?

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?

My mum works in corporate America and is stretched thin. Spreadsheet analysis she has to run manually, a constant pile of emails to draft, life admin on top. She also maps out her processes with mind maps and flowcharts already - the raw material for a second brain is there. The use cases are obvious. She just needs the cognitive load cut. The plan is to wrap her an ICM system she can actually use - one interface on her Claude Enterprise subscription, so she doesn't have to think about what's underneath. I'm 18, built this for myself, and I'm starting to look at consulting for local businesses. This is the first test of translating what I know into something that works for someone else. The scoping process I'll sit with Claude and design the approach. What I'm after is the specific stuff: what would you actually tell someone [me] doing this for the first time with a non-technical user who's already process-minded?