A lead has three named forms on the table: data-pipeline testing, adversarial testing, and a review of algorithm or model suitability. How should those attach to risk lanes without teaching later-chapter methods?

Those three named forms already have home lanes: data-pipeline testing sits with input data, adversarial testing sits with the model, and algorithm or model suitability review sits with development. Parking all three in one lane, or dumping them into Chapter 6 derivation or Chapter 7 canary work, skips that map and starts teaching later methods the item never asked for.