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: Pick one small multi-feature project and draft its mission plan—write a validation contract of explicit assertions, assign assertions to features, define a structured handoff schema for workers, and specify which model role fills orchestrator, worker, and validator seats.
- 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..."

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 "The Multi-Agent Architecture That Actually Ships — Luke Alvoeiro, Factory", not a generic Agentic Engineering 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.