This stood out to me [0]:

> For example, compaction summaries included instructions to invent missing data without disclosing it and to hide failures. These instructions were often followed.

Before the HF hack became public, I noted some major issues in GPT-5.5 compaction [1] and concerning approaches taken by GPT-5.6 Sol to resolve some git based evals [2]. Now with GPT-6 Astra, while I am still not done getting a proper feel or running all evals, I am not convinced the model adheres to tasks in a way previous OpenAI models managed easily. Some git disaster recovery tasks the model does arrive at the final result, but in a way that deviates greatly from the prompt (which was written to carefully preserve specific checkouts in a specific manner) which can in some cases loose data. Less often than GPT-5.6 Sol and mainly on longer running tasks so far, but again, still testing.

Reading things like these compaction summary findings, all these issues start to click into place more, especially alongside the massive reduction into barely coherent text that OpenAI has driven with reasoning starting with GPT-5.5 [3].

GPT-5 and its subsequent post trained releases were amazing in task adherence, I very much liked using them, but ever since the Spud pretrain, I have seen outright concerning results in personal testing from these. With GPT-5.5, it seemed like a regression in compaction only as if a task didn't require it, task adherence was as good or better than GPT-5.4. But with GPT-5.6 Sol and compaction once again being reliable (on the surface), task deviating behaviour became more frequent and at the same time subtle.

I'll keep using any model in a VM for the time being, but whatever happened post Spud, they really need to clean up that training data. These issues festering for multiple pretrains, them simply not paying attention to what models do, sharing resources and considering that a "sandbox", it's a highly problematic pattern.

That compaction one also was seemingly detected on GPT-5.6 Sols release day. Might have been useful to know it then, or alternatively, in the name of being effective and altruistic, maybe hold back the release for a few days.

I'll admit, it is very much possible that my findings are not in any way connected to the deep seeded issues OpenAI has had lately, but with the sudden switch in task adherence after the Spud pretrain over multiple releases and their repeated incapability to securely test their own models, it feels a bit to fitting.

If I went to a restaurant three times, ordered something different each time, but felt unwell after each, it wouldn't be a massive leap to consider that related to the health code violation they got soon-thereafter. An unfitting analogy I admit, as that'd require consequences for ones actions.

[0] https://alignment.openai.com/misalignment-reports/encouragin...

[1] https://news.ycombinator.com/item?id=48829427

[2] https://news.ycombinator.com/item?id=48967423

[3] https://gist.github.com/aussetg/20747ae00df17992acb4ebdfcd8d...

Our framework for reporting model misalignment