Coordinating everyone around a technique this brittle is about as bad a safety or strategy posture I could imagine. It’s not just “it will break eventually,” it’s “this is a fundamentally unsound basis for safety.”
I haven’t made up my mind on this, but I think it’s an important point. It’s not 100% clear to me that feeling like we have somewhat of an understanding of a model’s reasoning and alignment because we can read the chain of thought actually puts us in a better position. As Anthropic has stated, they think that Claude demonstrated motivated reasoning in its chain of thought when hacking into external services.
It’s been demonstrated that there is clear current usefulness in monitoring chain of thought, and I think it can help explain some model behaviors currently. If our alternative to using CoT monitoring is to continue scaling as we would otherwise, but with no monitoring, that’s a clearly worse situation. But I think that not having this crutch would give people more accurate understanding of risks that we’re taking.
They could also be counting the looping as an optimization, and basically be saying, “we could’ve just added twice as many layers and would’ve seen the same CoT controllability”. So maybe they had a serial depth in mind that they considered acceptable, and chose a more cost efficient architecture that has that depth. I think you can justifiably make the claim in that scenario that it’s not the architectural changes. But it would be a bit dishonest or misleading if they could only afford that serial depth because of the looping.