My Obsidian Vault in 2026 - What I Actually Open Every Day

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

Source video:
- Title: My Obsidian Vault in 2026 - What I Actually Open Every Day
- URL: https://www.youtube.com/watch?v=nNvQMDbzdBg
- Topic: Agent Architecture
- My current learning frame: Pick the three kinds of work you do most (e.g. writing, capturing links, journaling), create and save a dedicated Obsidian workspace for each, wire them to a Commander status-bar switcher, and route new notes through a single Quick Add command so you can move between modes without ever deciding where a note belongs.
- Why this matters: New playlist item from Paul's Obsidian Systems; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "This is my Obsidian Vault. >> >> A while back I made a video about every Obsidian Vault I'd ever built. The question people kept asking me was the obvious one, what do you actually use now? So,..."
- 5:53 / Evidence 2: "jump from RSS over to discoveries, and here I have my content discovery system. So, you can see that I've got Nate's video here. So, open up this one. So, this one is something I need to review."
- 8:25 / Evidence 3: "So, if I want to create a new note, I can select this one here. It prompts me for the note name, so I'll call this one quick add demo. And it's just going to load my template..."
- 11:12 / Evidence 4: "and then I have all my notes created for May, and I could either find it in my little local graph view here, or find it on the left-hand side, and you can sort by months here. So,..."
- 17:13 / Evidence 5: "daily there because it is actually on the calendar. So, what I do is I attend to select the calendar date here, then it grabs my New Delhi note, I hit create, and then it prompts me with..."
- 19:15 / Evidence 6: "monthly, quarterly reviews automatically with AI tools. So, I'm going to use a cloud command in order to do that. So, you will show you that in the next video. All right, let's flush out some more things..."
- 24:11 / Evidence 7: "my local graph view. And I can go explore those notes about mindset. So, having a nice foundation like this allows me to just explore through particular topics that I need to brush up on or explore further."

Video-aware target:
- Prompt lane: AI interface control
- Mechanism to extract: Extract how the interface gives the user control over context, visual quality, generated artifacts, and handoff.
- Artifact to produce: A UI control-surface critique sheet with context inputs, artifact visibility, review criteria, and implementation handoff.
- Artifact must include: context input; visual target; preview/review step; implementation handoff; quality rubric

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 the interface gives the user control over context, visual quality, generated artifacts, and handoff. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A UI control-surface critique sheet with context inputs, artifact visibility, review criteria, and implementation handoff.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Context -> Generation surface -> Preview -> Critique -> Implementation handoff
   - answers to these source questions: What does the interface let the user control? | What artifact becomes visible? | What critique or handoff step closes the loop?
   - 3 concrete examples that apply the video idea to real agentic work, such as design.md handoff; Figma-to-code review; UI reference library translation
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: generic UI inspiration; visual output with no critique; handoff that lacks implementation criteria
   - a checklist for the next real workflow, focused on: context, preview, artifact visibility, critique, handoff
   - one practical exercise with a clear done signal: Turn one UI demo into a design-review checklist for a real product screen.
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 "My Obsidian Vault in 2026 - What I Actually Open Every Day", not a generic Agent Architecture essay.
- Cite transcript anchors for every claim about design context, UI generation, preview, critique, or handoff.
- 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 design tips; visual hype without inspection; screenshots without implementation criteria.
- 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.