Anthropic Just Dropped a Masterclass on Building Agent Harnesses (for Large Codebases)

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

Source video:
- Title: Anthropic Just Dropped a Masterclass on Building Agent Harnesses (for Large Codebases)
- URL: https://www.youtube.com/watch?v=efRIrLXoOVA
- Topic: Agent Architecture
- My current learning frame: Take one of your own large repos and stand up the three demoed pieces: split your CLAUDE.md into a lean root plus a scoped subdirectory file, wire a stop hook that proposes rule updates, and add an LSP-backed MCP search tool, then verify each loads or fires in a live Claude session.
- Why this matters: New playlist item from Cole Medin; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:15 / Evidence 1: "already have a complex code base or two or three. You've got the apps and platforms that you're building, your second brain. You have these code bases that are tens or even hundreds of thousands of lines long..."
- 3:44 / Evidence 2: "And so, now with the AI layer, we have a third component of every code base introduced. This is everything like your global rules, your skills, your MCP servers and sub agents. Really every single individual feature of..."
- 15:35 / Evidence 3: "workflows and capabilities. And so, like this is an example of a skill right here for adding API routes in this code base. Really, a skill is some kind of set of steps, some kind of process, reusable..."
- 17:32 / Evidence 4: "claw.md. The distinction that I like to make is that global rules are your conventions. It's the rules that you need to follow. Like every route is registered here for example. Your skills are the workflows. So we..."
- 21:26 / Evidence 5: "kind of harness to give better search capability to Claude code when you're working in a larger code bases. And really they operate like skills. Just use sporadically throughout your session. So, like with skills we're loading in..."
- 23:31 / Evidence 6: "authentication." I don't know, I'm just kind of throwing out something off the cuff here, but you have sub agents built into a lot of these coding agents now, like Claude Code and CodeX. And so, you don't..."
- 27:33 / Evidence 7: "something that I help with. And so, I do offer enterprise trainings where I help you build out the AI layer, understand the core methodologies for AI coding, and create that standard for your adoption of coding agent..."

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 "Anthropic Just Dropped a Masterclass on Building Agent Harnesses (for Large Codebases)", 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.