In this analysis
Reuse preview fixtures rather than preview approval when additional post-training produces a new downloadable artifact.
Mistral Large4’s published weights followed additional post-training, so an earlier preview evaluation cannot be treated as direct acceptance of the later artifact.
A new artifact after a preview
The weight announcement states that further reinforcement learning followed the preview. The release is therefore not merely a transport change from API calls to local files. Its model state is a relevant part of the new event, and behavioural conclusions should remain attached to the state actually tested.
The preceding timeline
The earlier Mistral3 publication establishes family context, while the Large4 preview supplies the immediate prior stage. The chronological relationship explains why preview fixtures are useful for comparison. It does not establish that the later checkpoint returns the same outputs or exposes identical defaults through every runtime.
A revised artifact can improve broad performance while changing a narrow application contract. That is not a contradiction. Aggregate improvements and field-level compatibility answer different questions, so both deserve evidence rather than having one silently stand in for the other.
A structured-client example
Imagine a preview-based application that accepts a concise object and ignores explanatory text. The later checkpoint may still solve the task correctly while expressing its answer differently. If the client fails, the diagnosis could concern representation rather than task understanding.
Retain raw responses and the semantic expected result separately. Compare whether the artifact answered correctly and whether the client interpreted it correctly. This prevents a parser assumption from being misreported as a model regression, while still recognizing that client breakage is a real migration issue.
Control the execution route
Moving from hosted preview to local weights changes more than one variable unless the relevant settings are aligned. Templates, sampling, preprocessing and runtime can contribute to observed differences. The new checkpoint’s post-training should not automatically receive all credit or blame for a comparison that also changed these conditions.
If only an end-to-end configuration comparison is possible, label it that way. Such a result can be operationally useful without isolating the causal contribution of additional training. Precision about the experiment makes the conclusion stronger, not less practical.
The retrospective lesson
The October weight event combines artifact access with a revised model state. Those are two reasons to revisit acceptance rather than merely changing the endpoint in an existing client.
The conclusion is to reuse the preview’s questions, not its unqualified approval. A later trained artifact earns its own task and integration evidence. That preserves the value of early testing while recognizing the substantive difference introduced before the published weights became available.
Further analysis: Reproducible inference stacks: preserving a GPU pilot’s result; GPU hosting for multimodal models: count more than text.