Repository navigation
Support public K2-Horizon base models in SGLang #49
Description
Public source requirements
Use the public Hugging Face artifacts below for all K2-Horizon work in this issue.
These identities define the model consumer. They do not add model bytes, runtime execution, or another owner to a source-only issue.
These requirements supersede earlier internal checkpoints, source revisions, private locators, model aliases, and conversion requirements for this campaign.
| Public source | Immutable revision | Qualification owner |
|---|---|---|
| IFM/K2-Horizon-375B-A23B | 496ca1ba08bdd1d9023bc1fc587a0bc9525eec0e |
#855 |
| IFM/K2-Horizon-MoVA-36B-A4B | de2d2efb32ed7639b7140bccbefe131a0063a982 |
#856 |
| IFM/K2-Horizon-32B | 99ffbe5147448a3d223d031dce6895b52e1c0163 |
#857 |
| IFM/K2-Horizon-7B | ff325e226270e05ea081a97fd0c9c62652472fe8 |
#858 |
| IFM/K2-Horizon-3.7B | 4b8d3fd26f676212186e02b1c2c4c82139438538 |
#859 |
| IFM/K2-Horizon-0.9B | 598e76ceef4ce5dae777842ea89858b8712b53f4 |
#860 |
The source catalog and artifact cookbooks bind the accepted 2026-09-13 source epoch.
Use their exact content identities, manifests, input roles, and loader requirements.
A changed upstream head requires a separately reviewed source epoch.
A local cache or storage path is a physical input. It does not identify the model.
Earlier internal checkpoint tests, image runs, and qualification results do not qualify these public bytes.
Repeat the applicable source, engine, topology, request, and cleanup checks for each selected public identity.
Keep model bytes unchanged and outside Git. Keep admitted model inputs read-only.
Keep remote checkpoint code disabled. Use reviewed installed runtime support.
Keep native-8192 and yarn-131072 as separate checked runtime identities.
They can use the same pinned source configuration bytes. #860 owns native qualification, and #871 owns YaRN qualification.
Problem and scope
SGLang needs a complete native loading and serving contract for the six public K2-Horizon base artifacts.
Use the pinned public inputs above and synthetic fixtures derived from their documented configuration and tensor shapes.
No private validation package is required for the public source contract.
Required behavior and acceptance
- Provide one native
K2HorizonForCausalLMmodel entry point and installed K2 configuration support. - Derive dense, routed-expert, shared-expert, and MoVA behavior from typed source fields.
- Support grouped normalization and partial rotary embeddings where the accepted public configuration requires them.
- Keep MoVA value routing distinct from MLP expert routing.
- Test dense, routed-expert, shared-expert, and pipeline-partition weight loading.
- Test the applicable normalization and rotary forward behavior.
- Support and test tensor parallelism, expert parallelism, and DeepEP selection for the selected topology.
- Preserve ordinary text, reasoning content, and structured tool calls in streaming and non-streaming responses.
- Test malformed calls and streaming boundaries without inventing calls or losing visible content.
- Reject contradictory or unsupported configurations before weight loading and GPU allocation.
- Load configuration with remote checkpoint code disabled and network access disabled after staging.
- Run fresh H200 qualification for every required public architecture variant.
- Bind results to the public source revision, runtime revision, immutable image, topology, probe set, and cleanup evidence.
- Publish sanitized receipt identities and outcomes. Public model names, revisions, and documented architecture facts can appear in tests and reports.
- Keep credentials, private storage paths, hosts, endpoints, and private runtime data out of public records.
Dependencies and boundaries
LLM360/comet#812 supplies Comet's immutable compatibility inputs.
LLM360/comet#811 owns Comet image admission and full service qualification.
LLM360/sglang#50 owns published FP8 formats.
Uno remains under pairing and diffusion decoding.
Do not change model bytes, publish a Comet route, or claim Comet qualification from a standalone engine test.
Activity
mvillmow commentedon Sep 1, 2026
Bring-up found that IFM trusted configuration expects a different Transformers and Hugging Face Hub API set from the current candidate image. Compatibility aliases only exposed additional configuration-contract failures. Native IFM configuration support should not depend on checkpoint-side compatibility shims. This result is another acceptance case for this issue.
[-]Support IFM model variants in SGLang[/-][+]Support public K2-Horizon base models in SGLang[/+]