Course Info

How the release harness works

A short course on the Tutors release harness: the theory behind it, the design of its containers, the philosophy of A/A and A/B testing, the approach it takes from scripted traffic to a verdict, and the A3 that explains every night whether main is ready to become a release.

Root cause, countermeasures and follow-up

The right-hand side of the sheet comes from the kaizen register.

  • Post-deploy reads only the runs since the newest deploy. It names the release production serves, when any red began, and the root cause. A rollback from an earlier release is labelled as such.
  • Countermeasures come from the 5 Whys. Each one says where it is in place and what a release must show to prove it works (check). The tile splits them into built and waiting on a release, not built, overdue and verified.
  • Lean terms on this sheet explains the Lean words the page uses.

Your decision

Using what you wrote down, answer in three sentences, as the A3 would:

  1. This compares … against … .
  2. The Gate is … because … .
  3. Of N differences, … explain …, leaving U unexplained; look first at … .

Remember: the A3 is advisory. It informs the release decision; the Gate alone decides the exit code.