What Happens When AI Coding Gets a Delivery Pipeline (Routa)

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

Source video:
- Title: What Happens When AI Coding Gets a Delivery Pipeline (Routa)
- URL: https://www.youtube.com/watch?v=_16PhraFYjQ
- Topic: Agent Architecture
- My current learning frame: Set up Routa on a throwaway repo, define one realistic development task, and document the evidence and traces it produces at each Kanban stage to judge whether the pipeline model actually beats a single chat thread for that task.
- Why this matters: New playlist item from Better Stack; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "This is Ruda, an open-source AI coding tool that turns your agents into something closer to a delivery system. Not another paste your repo contacts and pray it works. A delivery system with backlogs, dev, review, evidence, and..."
- 2:00 / Evidence 2: "give it one or two small tasks. Nothing dramatic, guys. Just I don't want to build the whole app. Just the kind of task you would actually hand to an AI tool during normal development. Normally, this is..."
- 3:55 / Evidence 3: "define a task. The agents work inside of that structure. It also uses agent protocols like MCP and ACP, so you can add those in or use those where you need. It's more like infrastructure for coordinating software..."
- 5:31 / Evidence 4: "But the center of gravity is still the conversation, the prompts we're giving it. Ruta's center is a bit different. It's the task moving through a delivery system, backlog, to do, testing, review. Now, compare that to agent..."
- 7:13 / Evidence 5: "kind of why I like the direction. It's not pretending the hard parts of software delivery disappeared, it's just trying to organize them. AI is not going away, but the chat-first workflow is starting to show its limits."

Video-aware target:
- Prompt lane: Hermes operations
- Mechanism to extract: Identify the operations control that makes long-running agent work visible, recoverable, or safer.
- Artifact to produce: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
- Artifact must include: health check; state model; permission boundary; log source; recovery action

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 the operations control that makes long-running agent work visible, recoverable, or safer. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A Hermes-style agent-ops runbook with health checks, state transitions, logs, recovery steps, and review criteria.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Project state -> Session -> Queue/Kanban -> Tools -> Logs -> Recovery -> Post-run review
   - answers to these source questions: What operational failure is prevented? | What state is visible? | What can be recovered or redirected?
   - 3 concrete examples that apply the video idea to real agentic work, such as Hermes Kanban triage; local model endpoint check; agent swarm recovery review
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: treating UI features as reliability; missing logs; no stop/recover path
   - a checklist for the next real workflow, focused on: status, model/backend, tools, logs, recovery
   - one practical exercise with a clear done signal: Write a runbook for restarting one stuck Hermes-style agent session.
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 "What Happens When AI Coding Gets a Delivery Pipeline (Routa)", not a generic Agent Architecture essay.
- Ground each ops recommendation in transcript evidence about state, queues, models, tools, security, logs, or recovery.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: feature cheerleading; ops advice without logs/state; assuming reliability from a demo alone.
- 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.