Why Everyone Is OBSESSED With Obsidian

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Why Everyone Is OBSESSED With Obsidian
- URL: https://www.youtube.com/watch?v=UuX4zk9jTAg
- Topic: Interfaces + Open Design
- My current learning frame: Build a small Obsidian vault with separate human and machine folders, a tagged daily-note template, and a top-level map file, then open that same vault as a project in two different AI tools to confirm both can navigate it identically.
- Why this matters: New playlist item from Eric Michaud; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:29 / Evidence 1: "Obsidian lets you take your prompts, your workflows, your research, your context in general into any different AI platform of your choice, okay? So, instead of your memories and projects being trapped behind ChatGPT or Claude, you take..."
- 3:15 / Evidence 2: "my skills, workflows, and whatnot and bring it into the Codex app, for example, or Claude Code or Grok or Gemini, Antigravity, whatever. It's all the same experience and it's all ready to go, no matter what platform..."
- 5:15 / Evidence 3: "CLI, Claude code, Grok build. I built out my own custom Harness with the Pi agent and I use that in here and they can all talk to each other. The how they talk to each other is..."
- 7:39 / Evidence 4: "window, which is nice. I don't really have to leave this screen, right? I've got my Hermes agent here, I've got my calendar, I can pop open a web browser or like different apps and things like that..."

Video-aware target:
- Prompt lane: Context/search
- Mechanism to extract: Extract how context is found, filtered, refreshed, and handed to the agent before it acts.
- Artifact to produce: A context retrieval map with source inventory, indexing/search path, query rules, freshness checks, and agent handoff.
- Artifact must include: source inventory; index/search layer; query rule; freshness check; agent handoff; proof behavior

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Extract how context is found, filtered, refreshed, and handed to the agent before it acts. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A context retrieval map with source inventory, indexing/search path, query rules, freshness checks, and agent handoff.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Work question -> Source inventory -> Index/search layer -> Retrieval rule -> Agent context -> Answer/proof -> Maintenance
   - answers to these source questions: What source is searched or indexed? | What query/retrieval rule is demonstrated? | How does the agent use the retrieved context?
   - 3 concrete examples that apply the video idea to real agentic work, such as codebase memory; personal wiki retrieval; Elastic search context engineering
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: dumping all context; stale memory; retrieval with no proof trail
   - a checklist for the next real workflow, focused on: sources, query, freshness, handoff, citation/proof
   - one practical exercise with a clear done signal: Write three retrieval queries for one real project and define what each must return.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "Why Everyone Is OBSESSED With Obsidian", not a generic Interfaces + Open Design essay.
- Cite the transcript wherever the prompt names a task boundary, review habit, context move, or verification standard.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic context-window advice; memory hype without retrieval rules; source claims without freshness checks.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.