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. š«¶