Model-in-the-Loop Engineering · Capstone brief
ENG-12 · Refuse the autonomy
Pick a use case where the correct engineering answer is not to deploy the model — and defend that refusal with evidence, not vibes.
The question
Pick a use case where the correct engineering answer is not to deploy the model — and defend that refusal with evidence, not vibes.
System / materials
Student selects from teacher-approved options (including “our own ENG-04 scope, but the answer is no”).
Expected failure modes
Refusal without analysis. Analysis that secretly re-opens deployment.
Done looks like
Evidence memo: hazard, latency, data, or maintenance reasons autonomy fails; alternative (human, interlock, or simpler rule) named.
Five C's
CT: evidence-backed refusal. CR: alternative design. CO: peer red-team of memo. CM: memo a director accepts. CZ: who is protected by saying no.
Mentor role
Engineer reviews evidence at Checkpoint 2. School-supervised.
Rubric calibration
R1: named use case. R2: evidence cited. R3: attempted baseline or rule. R4: counterarguments addressed. R5: memo stands alone. R6: refusal holds under red-team.
Two ways this goes wrong
(a) “AI is bad” essay. (b) Refuse in prose, demo full autonomy anyway.
Credit lane fit
Lane A immediately. No verified credit claim.