AI Can Build Your App. It Can't Engineer It. (9 Skills)

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

Source video:
- Title: AI Can Build Your App. It Can't Engineer It. (9 Skills)
- URL: https://www.youtube.com/watch?v=Vok_nReMFaU
- Topic: AI Strategy
- My current learning frame: Take one small feature in an existing project from a written scope and a value-by-value source check—stopping for any missing decision—through repository-aware implementation, real-flow verification, and one-hypothesis-at-a-time debugging.
- Why this matters: New playlist item from JavaScript Mastery; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:30 / Evidence 1: "the project together. No plan the agent remembers, no record of the decisions, nothing making it build with what already exists instead of just piling more. And that was never something that a better prompt was going to..."
- 9:18 / Evidence 2: "new session opens blind and just guesses. And it guesses differently every time. So your codebase quietly drifts into three different styles. So you need one and setting it up well is more work than it sounds. Especially..."
- 11:35 / Evidence 3: "job you actually have most days. Most AI coding tutorials, mine included, build on a brand new project. It gives you a clean slate, nothing to fight, and easy to learn from. But that's not your typical Tuesday..."
- 13:32 / Evidence 4: "design a new feature, it's designed against the constraint the existing system already imposes the data it has, the patterns it follows, not in a vacuum. The workflow works with the code that's there instead of fighting it,..."
- 15:11 / Evidence 5: "screen it was supposed to build is even there. So our agentic engineering workflow doesn't just take the it works as an answer. There are really four jobs here and it keeps them separate on purpose. There's the..."
- 20:32 / Evidence 6: "files. Work on real code. Prove it actually runs. And fix it with discipline when it breaks. That's the workflow that compounds instead of decays with every feature building on the last instead of fighting it. And the..."
- 23:05 / Evidence 7: "model or a smarter prompt. It's this. Decide what to build first. Make the hard calls on purpose. Keep the state in files and never ever let the AI decide something important without telling you. Do that with..."

Video-aware target:
- Prompt lane: Agent harness
- Mechanism to extract: Identify what surrounding harness makes the model more useful than chat alone.
- Artifact to produce: A one-page agent harness map with tool boundaries, state ownership, and proof signals.
- Artifact must include: model role; tools; state/memory; permission boundary; verification proof

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: Identify what surrounding harness makes the model more useful than chat alone. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page agent harness map with tool boundaries, state ownership, and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: User intent -> Model role -> Tool surface -> State and memory -> Verification loop -> Reusable operating rule
   - answers to these source questions: What does the video claim the agent can do? | What surrounding system makes that claim plausible? | What proof is shown instead of merely asserted?
   - 3 concrete examples that apply the video idea to real agentic work, such as a repo-editing harness; a local research assistant; a recurring refresh agent
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: treating model choice as architecture; ignoring tool permissions; missing verification evidence
   - a checklist for the next real workflow, focused on: tool boundaries, state ownership, done signal, recovery path
   - one practical exercise with a clear done signal: Map one current coding workflow as a harness and mark the first missing proof 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 "AI Can Build Your App. It Can't Engineer It. (9 Skills)", not a generic AI Strategy essay.
- Tie each harness element to a transcript anchor that names a tool, state boundary, permission, model behavior, or verification step.
- 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 agent definitions; model leaderboard claims; tool list without operating boundaries.
- 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.