Welcome to Day 2

Yesterday we caught design problems after the code was generated. Today we stop them before generation. Then, in the afternoon, we tackle a harder question: what does testing even mean when the system’s correct behavior is a distribution?

Day 2 at a glance

Day 2 Morning schedule

Including a 10 minute break, this session should take about 3 hours and 45 minutes. It contains:

Optional morning alternative: own Project A

If Project A produced working code that the class does not yet feel able to explain or safely change, use From Generated Code to Owned Code instead of starting Project B that morning. Project B remains part of the course and can be delivered later; the optional session does not replace or shorten its material.

The bridge session is 2 hours 40 minutes including a break. Students trace, test, change, and defend their own Project A implementations, then carry a claim/evidence method into Project C.

Day 2 Afternoon schedule

Including a 10 minute break, this session should take about 3 hours and 45 minutes. It contains:

Compressed three-hour Project C route

When the whole afternoon, including break and debrief, is limited to three hours, use the three-hour route on the Project C welcome page. It preserves the functional-safety frame, arbiter design, replayable evidence, property tests, measurement, and a full 30-minute debrief. Statistical confidence tooling and protocol extensions become after-workshop work.