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. ๐ซถ