3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)

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

Source video:
- Title: 3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)
- URL: https://www.youtube.com/watch?v=PiKCyu7WQLo
- Topic: Creative Automation
- My current learning frame: Pick one small business, sync two of its platforms into BigQuery with a scheduled GitHub Action, build a simple correlation dashboard on top, and add one voice-or-photo input flow — a miniature version of both systems clients paid $10K and $3.1K for.
- Why this matters: New playlist item from Eric Michaud; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "If you don't know what to do with your new found cloud code or code x skills, I'm going to save you some trouble. I've been making full time income in the AI space for the last 2..."
- 2:42 / Evidence 2: "serverless functions or something else, but like Claude Code Codex, they can figure that out. The biggest thing is messy, disjointed platforms go in, responsible intelligence comes out. And like I said, this isn't theoretical. The most recent..."
- 4:13 / Evidence 3: "my lunch on the road or whatever. I could give you commands, right? Like {slash} invoice. Four movers, seven hours. Boom. Invoice four movers, seven hours. No problem, right? Something else I'm doing really frequently now, too, with..."
- 6:21 / Evidence 4: "yourself and that's the thing. People have bought access to blueprints, workflows, apps, systems from me in the past and the same thing I've been approached by businesses and paid to set up systems for them. These all..."

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 "3 EXACT Systems I Get Paid $13.1K to Build (COPY ME)", not a generic Creative Automation 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.