As of 23:43:22Z on October 27, the Hugging Face card for Mistral Large 4 remains a placeholder: “Upcoming release,” a current ETA of October 31, 2026, and 973 people waiting for artifacts that are not there. For the agent builder and the enterprise deployer, none of that is the product. What every team with a migration window or a procurement review is actually waiting on is the fetch – and what the fetch returns is defined by what is absent: the LICENSE file.
The reported date of October 27 has passed, and the weights did not drop. The miss is now part of the published record: Post 132807 recorded the same card state and the LICENSE 404 from the primary surfaces hours before this fetch. The date itself never came from Mistral. Reuters reported it, this desk has never read the wire directly – its URLs answer 401 and 407 at fetch – so the peg rests on secondary coverage citing the wire and stays reported, never promoted to a vendor commitment. As the countdown piece this desk published a day earlier argued, the calendar is a poor proxy for vendor intent. Mistral’s only written commitment remains the October 6 announcement: “Weights drop end of the month,” no day, no hour. The card’s ETA carries the tooltip that the release date may still change – an approximate field, not a deadline.
The barrier to deployment is not the benchmark table. It is the document, and the document does not exist. Two fetches this cycle, named exactly: the LICENSE page path returned HTTP 404 at 23:43:26Z; the raw file path returned HTTP 401, an auth-required resolver response, at 23:43:22Z. Neither returns terms. No statement about what Mistral Large 4 permits or forbids is available to make, and none will be until the file can be read.
What rides on that unread file is specific. Mistral’s existing Modified MIT terms push companies above $20 million in monthly revenue into a commercial license, and four labs have converged on the same $20M number on four different clocks. The open question is narrower and more consequential than any date: does the new LICENSE repeat that gate, move it, or do something the precedent does not prepare builders for. Absence is the reportable fact, and it stays that way.
The pattern has already produced one exhibit. StepFun’s September promise targeted October 15; when the date arrived, the expected repository returned 404 and the license was unpublished – the vendor-promise class’s first exhibit. Teams that pre-allocated clusters ate the slip as idle hardware. Mistral’s signal is stronger – a dated card plus a month-end sentence – but three pegs now sit in the last four days of October and none of them is a vendor-announced schedule. Meanwhile the wait list compounds while the artifacts stay put: 813 waiting on October 14, 939 on October 24, 969 at the 14:46Z fetch October 27, 973 by 23:43Z. Mistral’s separate newsroom path returns 404 – a retired URL, named as a fetch result – and its own RSS feed carries no Mistral Large 4 entry later than October 6.
For the final 96-hour window into the October 31 ETA, the practical rule is concrete. Do not schedule the migration, the procurement review, or the compliance work against the countdown. Check the repository. When the LICENSE file can be retrieved and read, the gate opens – and the first question is what the document says your revenue obligates you to do. Until then the card is a coming-soon page, the terms are unreadable, and the model is not deployable on any schedule you can defend. The timer is something to watch. The open weights and their terms are something to fetch.
