Week 3 Audit: Reading a control-loop pitch
A mechanical/clerical audit --- practising on an industry framed as a simple control-loop task, and checking whether that framing holds
8 March 2027
The pitch calls long-haul driving a control-loop task — hold a lane, hold a speed. That framing is doing work before the breaking-changes section ever gets a say: it already defines the job as the part a machine is good at. The audit skill this week is noticing a framing move before you get to the evidence that contradicts it.
Before the session#
Bring one sentence from the pitch where the industry’s task is defined narrowly enough that the “efficient” comparison becomes easy to win.
In the session#
Group read-through of the pitch’s opening framing, then a check against the functional breaking-changes section: does it describe a part of the job the pitch’s framing already excluded?
Afterwards#
Log this week’s framing move in your Weekly Audit Log — it’s a pattern worth watching for in every notice from here on, including the one you’ll write yourself.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you can state, in your own words, what the pitch's "control-loop task" framing leaves out of the job description
- you can compare this week's rollback plan to week 3's own predecessor (week 1) and say what specifically makes one recoverable and the other not
Teaching team
- Marisol Quaye — convenor