When Microsoft introduced Microsoft-Decision-1 on October 9, the most consequential sentence sat in the middle of the How it works section, not the headline benchmark table:
To build Microsoft-Decision-1, we post trained Qwen3.5-9B for fast, single-pass decision scoring and will soon rebase it on other models, including Microsoft AI (MAI) and OpenAI.
The lineup behind it (Cloudflare Clef, Perplexity pplx-decider, GLM-5.3-Flash System One, firelex Jeff) confirms that the decision-model category is moving from open-source baseline to a tier-one vendor consolidation. Source: https://commandline.microsoft.com/microsoft-decision-1-model-foundry/
What Decision-1 actually is
Decision models take a fixed option set, return a calibrated probability per option, and never generate free text. Routing, guardrails, and AI-as-judge are the three workloads where they save the most latency and cost. Decision-1 ships in Microsoft Foundry and OpenRouter:
- Post-training base: Qwen3.5-9B (Alibaba open-weights 9B)
- Tasks supported: yes/no, multi-choice, rating, rubric-based grading
- Calibration: the probability is the API output, not a ranking
- Robustness check: 8 perturbation variants of the same prompt, average flip rate 1.3%, 0% flips when option order is shuffled, reversed, or paraphrased
- Safety: 5,250 requests across 11 safety benchmarks, refused harmful content while keeping utility high
Microsoft headline is the latency gap: 2.5x faster than H2O-Lightning-4B (runner-up) and 35x faster than GPT-6 Sol. 36-benchmark accuracy tops the table at 83.5% across roughly 150,000 questions blinded from training; calibration score 92.2%, second only to Quyet-1.0-Large. Pricing: input 0.042 USD per million tokens, output free, text-classification cost under one-twentieth of GPT-6 Sol.
Why the rebasing plan matters
Post-training on an open-weight base is the standard playbook for any team entering a narrow task lane without committing to a full base-model training run. What is unusual is that Microsoft chose to publish the rebasing roadmap up front. Three signals to read from that:
- MAI is the long-term base. Microsoft AI s MAI line has been referenced repeatedly over the past year but has not shipped as a flagship. Decision-1 is the first place MAI appears as a successor to an existing public model. The market now has a clearer read on where MAI general-purpose capability is being readied: not in chat, but in narrow inference workloads where calibration matters more than conversational fluency.
- OpenAI is a transitional safety net. The phrase including OpenAI next to MAI is not we will move to OpenAI models for decisioning. GPT-6 Sol has just been outpaced by Decision-1 on the same benchmarks; OpenAI here is the fallback for the period between Qwen3.5-9B and MAI readiness, not the destination.
- Qwen3.5-9B is intentionally the launch base. Microsoft could have waited; it chose not to. Launching with Qwen3.5-9B lets Decision-1 compete on benchmark tables today, where every week of delay is a week Cloudflare, Perplexity, and zhipu (GLM-5.3-Flash System One) extend their lead. The roadmap to rebasing is essentially: we win this week, we rebase next quarter.
The decision-model lane is now crowded
Between late September and October 9, five first-party decision-model releases have shipped:
| Model | Date | Base |
|---|---|---|
| System One (GLM-5.3-Flash) | 2026-09-28 | Zhipu GLM-5.3-Flash |
| Jeff (firelex) | 2026-09-29 | Self-built 2B |
| Perplexity pplx-decider-v1-27b | 2026-10-02 | Self-built 27B |
| Cloudflare Clef | 2026-10-02 | Self-built |
| Microsoft-Decision-1 | 2026-10-09 | Qwen3.5-9B (rebase to MAI / OpenAI) |
Jev, the model that defined this category in H1 2026, is now flanked from every side: big-tech entrants (Microsoft, Cloudflare), strong-startup entrants (Perplexity), open-weights repos (Jeff), and incumbent-derivative entries (GLM-5.3-Flash System One). The crowded lane is the precondition that makes the first-party consolidation play rational.
What this signals for Chinese open weights
The standard read on Microsoft picks Qwen3.5-9B is an open-weight Chinese model gets adopted by a US hyperscaler. The more precise read is the rebasing sentence: Qwen3.5-9B is the launch vehicle, not the long-term base. Three downstream effects:
- Adoption is real, but bounded. Microsoft text-classification cost-claim (one-twentieth of GPT-6 Sol) and API pricing (output free) only make economic sense if the base model is small enough to serve on commodity hardware. Qwen3.5-9B delivers exactly that. But the same paragraph that publishes the cost numbers also commits to a rebasing. So Qwen3.5-9B absorbs the launch workload and gets replaced when MAI is ready.
- The pattern is the playbook, not the partnership. Microsoft AI MAI line has previously transition-tested on Llama and Mistral bases; Decision-1 is the same script in a new lane. The decision-model race is therefore not which open base will Microsoft standardize on, it is how fast can Microsoft ship a workable first-party base.
- The signal for other tier-one decision-model entrants. Cloudflare, Perplexity, and Zhipu are all running their own self-built bases; only Microsoft is openly running on a third-party Chinese open-weight base for launch. The implicit bet is that the Qwen3.5-9B-based Decision-1 is good enough for the launch window but not good enough for the MAI-window; whether this bet pays off depends on MAI decision-scoring capability landing in Q1 2027.
The cleanest way to read the announcement is to treat the rebasing sentence as the real headline. Microsoft shipped a Qwen-based decision model on October 9, but the more important sentence is the one saying they will not stay on Qwen3.5-9B for long.