In this analysis
Date the specific publication event, because a model-card refresh and a release announcement establish different historical facts.
LFM2.5-2.6B’s release history should follow the dated primary announcement, rather than treating later model-card changes or secondary coverage as a new launch.
Different dates answer different questions
A launch announcement, repository update and news article can legitimately carry different dates. The first records a publisher’s release claim, the second records an artifact or documentation change, and the third records outside coverage. Choosing among them requires identifying the historical event being described.
The primary anchor
The company announcement supplies the event anchor for this retrospective. The earlier hybrid release and compact release establish dated precursors. Their sequence is useful precisely because each reference is attached to a specific publication rather than inferred from the latest state of a family page.
Secondary indexes can help discover a release, but disagreement between indexes should not be resolved by selecting whichever date appears most often. Repetition can come from shared aggregation rather than independent confirmation. The dated publisher artifact remains the stronger basis for this particular event claim.
A later-card example
Imagine a model card receiving a formatting correction after a release. Its last-modified date advances even though no new weights were published. A retrospective that interprets this timestamp as a new model launch creates a false event and can make the earlier announcement appear inconsistent.
Conversely, a changed checkpoint can be meaningful even when the marketing page remains untouched. The correct record distinguishes model identity from page identity. A useful chronology can contain both events without pretending that every edit is a new model or that every important change has a separate campaign.
Preserve what was actually verified
Keep the event claim, source URL and dated evidence together. If the publication does not establish when weights became downloadable, do not fill that gap with a card’s current timestamp. A precise uncertainty is more informative than a falsely exact date attached to the wrong milestone.
This also helps interpret later comparisons. An experiment can only be attributed to an artifact available at its actual stage. Moving a release date retrospectively can make an impossible evaluation look plausible or cause a valid early observation to appear chronologically suspect.
The retrospective conclusion
The model’s technical story and its publication history are connected but not identical. A compact agent release can be significant without every later documentation update becoming another breakthrough.
The conclusion is to name the event before assigning its date. Primary announcement, artifact publication and external coverage should remain distinct timeline entries when the evidence supports them. That produces a more useful history than a single timestamp chosen from whichever page changed most recently.
Further analysis: Reproducible inference stacks: preserving a GPU pilot’s result; GPU hosting for multimodal models: count more than text.