That would make a lot of sense from an inference optimisation perspective. The same prefill and decode machines can hold one set of weights, and serve both Astra and Sol requests.
At (multi-)terabyte-scale model weights, and when you have to offer not just the latest like Fable 5.2 but still serve 5.1, 5.0, etc; heck I think Opus 4.6 is still around; you really care about overall compute utilisation.
Idle GPUs are wasted GPUs; and even over the fastest interlinks you’re not hotswapping multi terabytes of weights.
With MoEs, there’s probably stuff you can play around with varying the number of active experts; or other clever optimisations.
Maybe Sonnet 5.5 could be just Opus 5.5 with a different router and less active params? Who knows; I’m just theorycrafting now :)
This doesn't really make sense given how the models released.
OpenAI released Astra long before latent-space looping was a thing at the frontier space.
Then they released Sol 6, which was fast, clearly not looped. Then they release Sol 6.1 which was nearly as good as Astra, but way cheaper, and WAY slower -> this would follow it just being a looped version of Sol 6.
It doesn't seem likely that Astra 6.2 is just a looped Astra 6... It's too fast, and they'd go bankrupt if they're charging the same price... It may be a further looped version of Sol than Sol 6.2 - which would explain why it's not as much better as we would've hoped.
It may also explain why their release is not going as well as they hoped. It's hard to predict how your first looped models are going to fare.
If you look at how long it took Google to recover from their failed 3.5 Pro, it would be surprising if GPT recovered from their rumored failed run on Astra in under a month. That would give them reason to release a looped Sol and call it Astra.
Even in the open weight Chinese models as small as DeepSeek V4.1 Flash - nothing is looped.
I think the rumor-mill consensus is that Google's models are significantly smaller while attempting to swing at the same level - but the ratios AFAIK are thought to be around the same - i.e. Neon is somewhere around half as big as Carbon, big enough that a newer checkpoint can make it temporarily a little bit better.
A GB300 rack has 72x288GB=20TB VRAM. Do the math and 10T parameter models are just about the max size you can easily train and serve (at 1M context) without doing a lot of custom hardware development or limiting your scale.