Model releases from unrelated companies routinely land in the same week after months of quiet. The clustering is not coincidence, and it follows from how these organisations decide when a model is finished.
Readiness is a judgement, not an event
Training completes weeks before release. What follows is evaluation, safety work, documentation and infrastructure preparation, none of which has a natural end point.
A model can always be tested further or tuned further, so the decision to ship is a judgement about diminishing returns.
Judgements of that kind are strongly influenced by what competitors are doing, because the cost of waiting changes when someone else moves.
Being second is worse than being early
Attention around a release is concentrated into a few days, and a comparable model announced two weeks later is reported as a response rather than an advance.
Organisations holding a finished model therefore ship as soon as a rival does, converting a planned launch into a reactive one.
This produces the characteristic pattern of one announcement followed by several within the same week, each of which had been ready for some time.
The industry calendar concentrates the opportunities
Developer conferences, major research meetings and quarterly reporting create a small number of dates that guarantee coverage.
Everyone can see those dates, so everyone targets them, and the clustering is partly just a shared calendar.
The quiet periods between are equally structured, since nobody wants to launch into a week when nothing else is happening and nobody is looking.
Capability improvements arrive on shared inputs
Competing labs draw on the same published research, the same hardware generations and a substantially overlapping pool of researchers.
When a technique is shown to work, several groups adopt it within months, and their results improve on similar timescales.
Genuine simultaneity therefore reinforces the strategic timing, and the two are difficult to separate from outside.
What the pattern means for reading the announcements
A release landing days after a competitor's is weak evidence about which organisation was ahead, since the second may have been holding a finished system.
The more informative signal is what a lab ships when nobody has forced its hand, because that timing reflects its own assessment rather than a response.
Benchmark comparisons published in launch materials are chosen by the party publishing them, and a model that wins on the metrics its own maker selected has demonstrated the selection more than the capability.