Detecting Silent Failure and Gating Changes

Two habits that keep an automated pipeline honest: proving a run actually did useful work rather than merely exiting cleanly, and gating a prompt or model change on a frozen eval set instead of a demo. Covers gray failures, progress invariants, post-run assertions, and a fixed-threshold eval gate with a warm fallback.

Lessons(4)