The Ultimate Solopreneur Agent Harness for AI Builders (Claude Code Harness)

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

Source video:
- Title: The Ultimate Solopreneur Agent Harness for AI Builders (Claude Code Harness)
- URL: https://www.youtube.com/watch?v=eKbdk0MUhsU
- Topic: Agent Architecture
- My current learning frame: Fork the freelance-developer harness repo, read the README and the .claude agents, then talk to the product-manager agent on a small feature to watch it spawn model-specific sub-agents with isolated context windows.
- Why this matters: This turns the harness idea into a concrete small-business operating model with roles, constraints, and recoverable sessions.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "I could just vibe code this myself. I don't even have to pay 40 or 50 bucks, right? >> It gives you the power to have a full development team at your beck and call. >> Everything is..."
- 8:19 / Evidence 2: "that's what's in here somewhere. So like here's your front end and your back end. So this is all of the code that's being executed. And then there's also a series of commands that that that you can..."
- 15:29 / Evidence 3: "basically leveraged the harness to build a uh a whisper transcription um software that that runs natively on Mac OS. And what's amazing is that and this uses all local models. So local open- source uh Whisper models..."
- 19:31 / Evidence 4: "anyway, the point is is this gives you the ability to just take any any GitHub repo that has in this case probably fine has a uh you know, has just static HTML. Oh no. What's going on?"
- 31:53 / Evidence 5: "go away. Okay. So if you look right, we're actually this is our context window. We're using sonnet. And if I just speak to claude, then I'm basically talking to this model and whatever the context is that..."
- 34:00 / Evidence 6: "the product manager is the one that basically does that. So for each of these agents, a different model might get uh called. But what's what's important that as the product manager calls each one of these agents,..."
- 36:45 / Evidence 7: "working on some of these projects or clients. So one of the first things that I did is implement this uh session context locking and this basically says I give it I I have a command use client..."

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 "The Ultimate Solopreneur Agent Harness for AI Builders (Claude Code Harness)", 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.