Model lifecycle
Kimi K3
Released 2026-07-16 · Back to Kimi
Exact-version signals observed 2026-07-16–2026-07-20 · n=754
Lifecycle updated daily · latest complete UTC day 2026-07-20
- Fixed 14-day baseline
- – –
- Latest 28 days
- – n=751
- Change vs baseline
- –
- 90-day slope
- – pts / 30 days
14-day rolling experience
Each daily point summarizes the previous 14 complete UTC days. The dashed line is the fixed release baseline; the verdict still uses independent non-overlapping 14-day segments.
4 of 14 calendar days collected · first possible point 2026-07-30 · current signals n=754
What explains the change
Experience change and discussion-mix change are separated. These are observational contributions, not proof of cause.
No category has enough samples in both windows for a contribution conclusion.
| Category | Baseline → current | Category change | Weight share | Experience contribution | Discussion-mix contribution |
|---|---|---|---|---|---|
| Coding | not enough datan=0 → 101 | – | – | – | – |
| Image / vision | not enough datan=0 → 5 | – | – | – | – |
| Local deploy | not enough datan=0 → 23 | – | – | – | – |
| Reasoning | not enough datan=0 → 188 | – | – | – | – |
| Roleplay / creative | not enough datan=0 → 11 | – | – | – | – |
| Safety & refusals | not enough datan=0 → 15 | – | – | – | – |
| Speed & latency | not enough datan=0 → 102 | – | – | – | – |
| General text | not enough datan=0 → 307 | – | – | – | – |
Lifecycle scores use the same experience-signal weights as the main index, without sample shrinkage after n=30. They measure public user perception, not model capability or backend causes.