In this analysis
Keep a promised publication in future tense until the actual artifact release has its own verified evidence.
Kimi’s commitment to publish K3.1Pro weights by November 4 remained a future statement at the November 3 review cutoff, so it cannot be recorded as completed availability.
The review has a time boundary
A retrospective written before a promised date must distinguish an announced plan from an artifact already verified. Later fulfillment may become another historical event, but it cannot be assumed in the earlier record. The rule is especially important when a headline uses a family name that already has hosted access.
What the sources establish
The dated product changelog establishes the rollout stage. The launch blog states the future weight commitment. The earlier KimiK2 paper and KimiK2.5 paper provide dated research context, not substitutes for a new downloadable artifact.
As of November 3, 2026, the November 4 commitment is still prospective. This article therefore does not claim that the promised files, exact license or local implementation were already independently obtained. A future publication needs its own primary evidence when it actually occurs.
A self-hosting-plan example
Imagine a team evaluating the available product while preparing a future local deployment. It can define task fixtures and identify expected dependencies now. It cannot truthfully mark a checkpoint as received merely because the publisher announced when it intends to release one.
| Status | What can be recorded |
|---|---|
| Hosted rollout verified | The observed interface and its current contract. |
| Weight publication promised | The publisher’s dated commitment, attributed as a plan. |
| Artifact independently obtained | A later verified source and the actual artifact identity. |
Do not borrow identity from metadata
A model-card page or repository can exist before the intended files are available. Its creation or modification timestamp does not automatically establish the release event. The record needs evidence that the artifact in question was actually published, rather than merely that a location for it existed.
Likewise, an earlier family checkpoint is not a replacement for the promised one. Similar branding cannot settle its license, architecture or supported execution path. Marking those fields pending is more useful than filling them with expectations that later readers may mistake for verified facts.
The retrospective conclusion
The product rollout and the publication commitment are both meaningful, but they change different parts of the evidence available. Preserving that difference makes the history accurate at its review date.
The conclusion is to retain future tense until completion is verified. This recognizes the announcement without inventing availability, and leaves a clear place for a later artifact event to add evidence rather than rewrite what was known earlier.
Further analysis: Reproducible inference stacks: preserving a GPU pilot’s result; GPU hosting for multimodal models: count more than text.