Why apps built with AI look a little... OFF

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

Source video:
- Title: Why apps built with AI look a little... OFF
- URL: https://www.youtube.com/watch?v=zR93TuQt0gc
- Topic: Agent Architecture
- My current learning frame: Use Why apps built with AI look a little... OFF as a transcript-backed agent architecture walkthrough: at 0:47, it frames with AI, the way that I set this up looks a little different than it used to.
- Why this matters: New playlist item from Brian Casel; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:47 / Evidence 1: "with AI, the way that I set this up looks a little different than it used to. So, I'll walk you through exactly how I do it using a free agent skill that I released and you can..."
- 2:21 / Evidence 2: "show you is available as a free agent skill. You can go to the resources section on builder methods and go to tools. That's where I'm releasing all of my free tools. and you'll find one called design..."
- 4:20 / Evidence 3: "have to-dos for my agent to to to run. I did a separate video a couple weeks back on the night shift. And that's sort of like the system or the mental model, if you will, for building..."
- 8:40 / Evidence 4: "this or specify it, then agents just start to build things in different ways and and you know, the the HTML DOM, if you will, starts to, you know, get get built out in different ways. Let's see..."
- 12:52 / Evidence 5: "ensure that your coding agent actually uses your design system. Now, dropping in the design system skill and using it on your application, it will add this design system page to your site and you can decide exactly..."
- 17:21 / Evidence 6: "instruct because that's something that agents do all the time. instead of using predefined color classes, they'll just go in and and say like, "Yeah, let's call this one, you know, some some specific hex code." And then..."
- 21:52 / Evidence 7: "the Builder. So you can grab this free agent skill that drops this whole design system into your codebase. That link is in the description. But a design system is just one piece of a much bigger shift."

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 one-page agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 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 "Why apps built with AI look a little... OFF", not a generic Agent Architecture 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.