Content plan
Learners can set up a pipeline where nothing reaches production unverified.
Part 2 — The delivery harness: continuous delivery & the production loop
This part is taught before the seam. It builds Module 3’s ladder into real, always-on infrastructure — the safety net that makes agent-speed development survivable.
Outcome
Learners can set up a pipeline where nothing reaches production unverified — and can articulate why continuous delivery becomes non-negotiable once agents generate the changes.
Planned coverage
- Why continuous delivery matters more with agents: volume.
- Trunk-based development: small, frequent integrations; no long-lived branches where agent output drifts, rots, and conflicts.
- The sensor gate: the pipeline runs the full ladder automatically on every change; red gate means no merge and no deploy.
- Decoupling deploy from release through feature flags, progressive delivery, and instant rollback.
Agent payoff
Green-or-nothing is what lets you accept agent volume. The agent iterates until the gate is green, and only green merges.
Seeds
- The sensor gate is a checkpoint the delivery plan schedules in the seam.
- The sensor gate is the boundary agentic execution runs against in Part 4.
Open editorial question
Confirm whether deploy/release decoupling belongs here or in Module 8.