The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory

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

Source video:
- Title: The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory
- URL: https://www.youtube.com/watch?v=ow1we5PzK-o
- Topic: Agentic Engineering
- My current learning frame: Use this agentic engineering video to extract the core workflow, identify the useful mechanism, and turn the demo into a reusable operating artifact.
- Why this matters: New playlist item from AI Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:30 / Evidence 1: "I come from a background in dev tools. About 2 and 1/2 years ago I started a project at Block which is where I was working at the time. And that project evolved into Goose. Goose is now..."
- 2:21 / Evidence 2: "implement first. You have you know sub agents and coding tools are the most common example. The other one is creator verifier. Right? Where one agent builds something and then you have another agent that checks that work."
- 4:16 / Evidence 3: "You scope that through a conversation. You approve a plan and then the system handles execution for hours or days and that enables you to focus on something else. Notably a mission is not a single agent session."
- 5:56 / Evidence 4: "lets missions run for many hours, many days in a row without drifting. And making it work had to involve sort of rethinking validation entirely. So when you've worked with coding agents before you've probably seen this pattern..."
- 8:01 / Evidence 5: "the code before. They're not invested in the implementation and so validation is adversarial by design. Okay. So then validation catches bugs. Right? But for a system that runs for many days you also need to make sure..."
- 14:56 / Evidence 6: "This means that almost all of the orchestration logic is defined in prompts and skills, um instead of like a hard-coded state machine. How it decomposes failures and um or decomposes features and handles failures is all in..."
- 17:13 / Evidence 7: "the connective tissue. You need uh these structured handoffs so that agents don't lose context, you need the right model in each role, and you need an architecture that will improve with each model improvement. So, what I..."

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 task packet that a coding agent could execute without wandering.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Task Packet -> Agent Run -> Evidence -> Review -> Standard
   - 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 "The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory", not a generic Agentic Engineering 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.