-
Notifications
You must be signed in to change notification settings - Fork 0
Track Kimi K3 support #15
Copy link
Copy link
Open
Labels
area: cpu-ai-runtimeCPU-only AI runtime, tokenizer, inference path, AI kernels.CPU-only AI runtime, tokenizer, inference path, AI kernels.area: model-arenaModel arena, shared weights, KV/cache, model format.Model arena, shared weights, KV/cache, model format.needs: designNeeds design decision or scope clarification.Needs design decision or scope clarification.priority: P2-mediumMedium-priority planned work.Medium-priority planned work.risk: hardwareHardware/platform risk area.Hardware/platform risk area.type: featureNew capability or user-visible behavior.New capability or user-visible behavior.
Milestone
Description
Metadata
Metadata
Assignees
Labels
area: cpu-ai-runtimeCPU-only AI runtime, tokenizer, inference path, AI kernels.CPU-only AI runtime, tokenizer, inference path, AI kernels.area: model-arenaModel arena, shared weights, KV/cache, model format.Model arena, shared weights, KV/cache, model format.needs: designNeeds design decision or scope clarification.Needs design decision or scope clarification.priority: P2-mediumMedium-priority planned work.Medium-priority planned work.risk: hardwareHardware/platform risk area.Hardware/platform risk area.type: featureNew capability or user-visible behavior.New capability or user-visible behavior.
Objective
Implement Kimi K3 as a first-class architecture adapter, with text and multimodal acceptance kept as separate gates.
Delivery dependency
This workstream is backlog work. It starts only after the XAIOS platform milestone and the Qwen 3.6 27B correctness milestone are complete, unless the maintainer explicitly reprioritizes it.
Current verified boundary
Kimi K3 text is interface-only and multimodal support is roadmap-only. No K3 checkpoint currently executes in XAIOS.
Progress gates
kimi_k3architecture adapterExactness constraint
Approximate routing must remain opt-in. Authoritative top-16 routing and target-model verification are required by default.
Status source
Execution status is tracked in the XAIOS GitHub Project. Support claims remain governed by
docs/MODEL-SUPPORT.json.