Loop engineering for beginners

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

Source video:
- Title: Loop engineering for beginners
- URL: https://www.youtube.com/watch?v=JoXbk2fm7jM
- Topic: Creative Automation
- My current learning frame: Design your first loop like you're onboarding an employee: write the job description (e.g. 'daily at 10:15, find PRs open more than 12 hours, babysit them until checks are green, otherwise Slack the team'), create it as a Claude Code routine or Codex automation, and run it once manually to verify both success criteria fire.
- Why this matters: New playlist item from How I AI; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:13 / Evidence 1: "it's useful, and some pitfalls to watch out for. We will be doing this in Codex and in Claude code, and at the end of this episode, you'll be one of the cool kids whose agents prompt itself."
- 2:46 / Evidence 2: "explaining that there are many ways you can prompt an AI agent. And often, we only think about one way to prompt an agent, but actually, there are many ways an agent like Claude Code, like Codex, like..."
- 5:29 / Evidence 3: "Claude Code and Codex, which is a goal. A goal is a type of loop that sets an outcome and runs an agent against that outcome until the outcome can be measured and validated or the agent is..."
- 8:01 / Evidence 4: "And so, this can be like GitHub connectors, connectors to Google Docs and Google Calendar, and plus plugins, which are some instructions on how to use those tools. Sub agents, both Codex and Claude Code allow you to..."
- 11:46 / Evidence 5: "have your agent prompt other loops. So again, you can think about a human with a team of agents who all have their own team of agents and you can start to get really creative about what these..."
- 20:04 / Evidence 6: "code we shipped, look at all the code commits and comments, and then come up with skills that our coding team, including agents, could use to deepen the work. And so, I'm going to select that one. It's..."
- 23:11 / Evidence 7: "What one of the things that Codex does that's kind of interesting is it sets up its own memory. So you can see here a little bit of the scaffolding of what an automation looks like, and then..."

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 creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 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 "Loop engineering for beginners", not a generic Creative Automation 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.