Claude Opus 4.8 Built an Agentic OS in 15 Minutes! (ultracode)

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

Source video:
- Title: Claude Opus 4.8 Built an Agentic OS in 15 Minutes! (ultracode)
- URL: https://www.youtube.com/watch?v=bqYj6OaTuVs
- Topic: Agent Architecture
- My current learning frame: Use Claude plan mode to draft and save a plan.md for a small personal dashboard with a brand design.md attached, run it once with Opus 4.8 plus Ultra Code, then critique the first pass and ship a single refining prompt while tracking the cost.
- Why this matters: New playlist item from Duncan Rogoff | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:47 / Evidence 1: "your own AIOS using Opus 4.8, Ultra Code, and dynamic workflows. So, focus in, close all your open tabs, and let's build. And if you want to get access to a prompt that will build your own AIOS..."
- 3:47 / Evidence 2: "trust because it's my own folder and now we are ready to start building our operating system. I'm going to close down the built-in agent. I'm just going to come up here and click a new terminal and..."
- 5:23 / Evidence 3: "branded carousels, just check out the video up top. And so, I have these files on my desktop right here. It's just this HTML file as well as this design.md file which has all of the rules in..."
- 7:21 / Evidence 4: "did notice this, too, which is pretty cool. I recommend everybody just like read what Claude is saying. It's the best way to learn how to use Claude code, and this just says, "Let me check what's in..."
- 9:01 / Evidence 5: "I can turn on Ultra Code to get access to dynamic workflows. And what's also cool is you can just type in the word workflows and you can see it gets this nice rainbow color to let you..."
- 10:31 / Evidence 6: "clients and personal projects that I'm working on. And then the bottom all the way down here is actually the skills that I most commonly run. If I click on any one of these, it's going to open..."
- 14:40 / Evidence 7: "Agentic OS, my operating system right here all ready to go. If you want to get access to a prompt that you can use to build your own AI OS automatically, along with an entire classroom of training..."

Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule

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, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
   - answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
   - 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
   - a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
   - one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
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 "Claude Opus 4.8 Built an Agentic OS in 15 Minutes! (ultracode)", not a generic Agent Architecture essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.