Harnesses in AI: A Deep Dive — Tejas Kumar, IBM

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

Source video:
- Title: Harnesses in AI: A Deep Dive — Tejas Kumar, IBM
- URL: https://www.youtube.com/watch?v=C_GG5g38vLU
- Topic: Agentic Engineering
- My current learning frame: Use the transcript anchors for Harnesses in AI: it opens with IBM where we we do things with AI, believe or not. We train frontier models, we build harnesses. It's really it's a fun lab, then moves into tools.
- Why this matters: New playlist item from AI Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:43 / Evidence 1: "IBM where we we do things with AI, believe or not. We train frontier models, we build harnesses. It's really it's a fun lab to work in. But that's not what I'm here to talk to you about..."
- 2:36 / Evidence 2: "harness? Because the name of the game with harness is reliability. Um I really hope I'm not supposed to stand in front of this white line and then I'm just not in the camera. Anyway, whatever. It's reliability."
- 4:29 / Evidence 3: "it's a harnessed coding agent. An agent harness has more or less the same typical suspects, moving parts. Number one, it's got a tool registry. Almost like so Claude code, cursor, codex, they have tools to read from..."
- 6:06 / Evidence 4: "harness together so we understand from first principles how this works. We're going to build a computer use agent that has a job. The job is go to Hacker News and upvote the first post, okay? It's a..."
- 7:56 / Evidence 5: "tools. And we create a context and we give the task, meaning the prompt here, to the context. Now, create tools is literally what it sounds like. It's here. There's just some types and create tools is a..."
- 12:07 / Evidence 6: "It index, it's it's all gone. So, the prompt is there. But this is it's like 19 lines of code, and we just have run harness. We've taken all the logic from here and hidden it in a..."
- 15:42 / Evidence 7: "blind. Uh but here, create login handler. This is This is all it does. It runs every agent loop just before we push to the traces, and it This is what it do It checks the browser session's..."

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 task packet that a coding agent could execute without wandering.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Task Packet -> Agent Run -> Evidence -> Review -> Standard
   - 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 "Harnesses in AI: A Deep Dive — Tejas Kumar, IBM", not a generic Agentic Engineering 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.