Your OS Changes Everything for Local AI

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

Source video:
- Title: Your OS Changes Everything for Local AI
- URL: https://www.youtube.com/watch?v=QeAHC1jGxck
- Topic: Interfaces + Open Design
- My current learning frame: Use the transcript anchors for Your OS Changes Everything for Local AI: it opens with VEO Wan and Sora for video. All built in. You also get Abacus AI deep agent to pretty much do anything.
- Why this matters: New playlist item from Alex Ziskind; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:42 / Evidence 1: "VEO Wan and Sora for video. All built in. You also get Abacus AI deep agent to pretty much do anything. Build full-stack apps, websites, reports with just text prompts, and deploy them on the spot. They have..."
- 4:27 / Evidence 2: "lemonade come in tied with Llama.cpp Vulcan, about a percent apart at 3 billion parameters. And the NPU shows up the moment you push long prompts, which we'll get into more when we're doing Linux. So, on Windows,..."
- 6:15 / Evidence 3: "in the stock Ubuntu 26.04 package that ships with, you know, the installation here. So, first we need to add the proper repository, the package there. And then, once that's done, we install Mesa Vulcan drivers and Vulcan..."
- 8:16 / Evidence 4: "agents, coding assistance. You saw me typing write a story before. Well, this is the opposite of that. This is like a really long prompt, and that takes time to process. It's like pasting in your entire code..."
- 9:40 / Evidence 5: "the calculations. The decode is much slower though. And that's a clue right there. That's a clue because decode happens in memory. Memory bandwidth is what determines slower or faster decode speed. So, I cracked it open. Two..."
- 11:49 / Evidence 6: "2.5 thing cuz I know some of you are going to complain, "Oh, it's an old model." I did Gemma 4 12 billion landed last week. Also, it's a totally different model architecture. So, yeah, it's it's a..."
- 13:47 / Evidence 7: "the fact that with the 370 you do get the two dims in there for your memory. Uh if you want to watch my review of the dev tests on the this year 10 from last week right..."

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, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A UI critique sheet for judging whether an AI interface improves control.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
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 "Your OS Changes Everything for Local AI", not a generic Interfaces + Open Design essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.