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. 🫶