The AI monitor was tested. The reported fixes still need a receipt.

A watchdog is reassuring until you ask a simple question: who checked that it could see what mattered? METR's newly published account of a short red-teaming exercise is useful precisely because it treats monitoring as a system that can fail, not as a reassuring label. The exercise examined a historical OpenAI setup during July and August. METR found weaknesses; OpenAI says the identified issues affecting production safeguards were patched. METR has not independently verified that claim. This is not evidence that every reported weakness remains in today's products. It is also not an independently checked clean bill of health. The distinction I want readers to keep is between three different things: activity that is eligible to be monitored, activity that is actually examined and harmful action that is stopped in time. A strong result on one does not automatically establish the others. OpenAI's own monitoring explanation acknowledges difficulty measuring missed detections and describes monitoring as one layer of protection. That creates a procurement question rather than a contest over whose reassurance sounds warmer. Which system version was examined? What changed? Did anyone independent test the repaired version? Who receives an alert, and what authority do they have to intervene? These are not reasons to dismiss the pilot. External access can produce valuable fixes, and a limited study can still reveal important weaknesses. But a public finding and a company's patch statement are different pieces of evidence. Keeping them separate is how scrutiny becomes useful rather than theatrical.