Model Status Guide
KTransformers docs separate code presence from validated support. A model can have code entry points before it has completed smoke or throughput tests on the current hardware, backend, and package versions.
Status Labels
| Status | Meaning |
|---|---|
| Current | Code entry exists and the documented interface matches the current package path. |
| Current, narrow | Supported only under explicit model, package, hardware, or backend constraints. |
| Needs smoke | Code or docs exist, but the target combination should be revalidated before use in the current environment. |
| Legacy | Depends on old entry points or obsolete package structure. |
| Internal / historical | Internal, incomplete, or enum-level feature that is not a user-facing path. |
Support Scope Comes From the Tuple
Model pages and the support matrix only cover the recorded combination:
model family + checkpoint + KT method/backend + hardware class + serving/training entry + package/version caveat
Why You May See Needs Smoke or Legacy
Pages show Needs smoke or Legacy when:
- the page depends on
local_chat.py,ktransformers/server/main.py,balance_serve, or old optimize-rule flows; - registry defaults and tutorial commands disagree;
- required package versions are special or pinned;
- the model path requires non-default conversion steps that have not been rerun;
- the hardware backend changed since the last test.