The vLLM project’s Semantic Router team has released the ‘Decision 3.0‘ decision model family under the Apache-2.0 license, covering 0.8B–27B parameter scales and skipping the text generation step entirely. According to the October 11, 2026 announcement, the five models were fine-tuned from the Qwen3.5 and Qwen3.8 families and process text, JSON, and image inputs in a single forward pass, returning responses as normalized probability distributions. This approach, named the ‘System One’ routing pattern, appears to be a structural attempt to lower the cost of intent classification, guardrails, and branching decisions in agent systems.
Lineup Composition and Open Source Policy
The Decision 3.0 family consists of five sizes: d3-lite (0.85B), d3-nano, d3-mini, d3-flash (9B), and d3 (26.09B). The announcement states that all models are distributed under Apache-2.0 and only BF16 weight precision is provided. No separate quantized variants are available on official channels, so users must choose directly from 0.85B to 27B based on VRAM headroom.
The base models are Qwen3.5 0.8B, 2B, 4B, 9B and Qwen3.8-27B (according to vendor claims, which remain independently unverified) families, combined with vision encoders of 0.10B–0.46B scale to process text and images simultaneously. Input images support PNG, JPEG, and WebP up to 1.6 megapixels. The announcement added that all models were trained on a single AMD Instinct MI325X GPU.
How It Works — Probability-Based ‘System One’ Routing
The key differentiator of Decision 3.0 is the elimination of the traditional routing pattern that requires text generation followed by parsing. Users deliver a state description in the system prompt and a question schema in the user message. In a single call, forward passes for all questions are executed independently, and responses are returned only as normalized probabilities in three types: Choice, Yes/No, and Score. Since there is no text decoding step, decision latency drops significantly on the same hardware.
The announcement team compares this structure to Kahneman’s System 1/System 2 analogy and calls it ‘System One’ routing. The intent is to finish branching decisions on multimodal input in the 20–40ms range for text-only inputs and 60–85ms for multimodal inputs. Cloudflare’s Clef-omni, which belongs to the same Jev API ecosystem, has adopted the same question types (choice, yes-no, score) and response schema, forming the foundation for multi-vendor integration [cross-verification].
Architectural Details and Integration Requirements
A summary of the parameter distribution and vision encoder configuration of the five models is as follows. d3-lite is a lightweight configuration combining a 0.85B text decoder with a 0.10B vision encoder, while d3-flash and d3 mount 9B and 27B decoders with 0.45B and 0.46B vision encoders respectively to improve image processing quality.
| Model | Decoder Base | Decoder Size | Vision Encoder | Total Parameters |
|---|---|---|---|---|
| d3-lite | Qwen3.5-0.8B | 0.85B | 0.10B | ~0.95B |
| d3-nano | Qwen3.5-2B | 2B | 0.18B | ~2.2B |
| d3-mini | Qwen3.5-4B | 4B | 0.30B | ~4.3B |
| d3-flash | Qwen3.5-9B | 9B | 0.45B | ~9.45B |
| d3 | Qwen3.8-27B | 26.09B | 0.46B | ~26.55B |
Prerequisites for integration were also explicitly disclosed. transformers is pinned to 5.17.0, and it is recommended to enable the flash-linear-attention package as an option to activate linear-attention layer acceleration. trust_remote_code=True is required when loading models, and since only BF16 weights are provided, configuring a 27B model with KV cache fully offloaded on a single 8GB VRAM GPU is physically impossible. Since the 27B weights themselves exceed 50GB, a single-node H100 (80GB) and AMD MI300X (192GB) or NVLink-based multi-GPU sharding is effectively a prerequisite.
Jev Decision Index 0.3.1 Results and Latency
In the Jev Decision Index 0.3.1 results (vendor self-reported metric, requiring independent validation), the internal evaluation metric, d3 (27B) took first place with text 64.1 and vision 71.6. The key figure emphasized by the announcement is that in the same class, d3-flash 9B (59.0) surpassed the previous generation’s Decision 2.0 27B (55.9). However, d3-lite’s vision score of 41.1 was pushed down to 3rd place by JPT-0.8B (42.1), which was fine-tuned on the same base alone.
Reported public vision task scores include InfographicVQA 97.3, Mind2Web 89.9, Hateful Memes 44.6, and MMMU-Pro 46.2. Latency on a single AMD Instinct MI325X for serial 1-request processing ranges from 21.7–84ms for text-only and 60.7–342ms when images are included. The announcement team firmly stated that all models were trained on MI325X, and did not disclose multi-GPU sharding or batch throughput numbers. Reproduction numbers on other accelerators such as NVIDIA H100 and H200 remain areas that require separate verification.
Practical Adoption Implications
The point that the decision model family realistically changes is layer 1 of the agent architecture. The previous configuration that implemented routers, guardrails, and intent classification as separate LLM calls and text parsing pipelines is replaced by a single call to a 0.85B–9B decision-dedicated model. Since probability values are fed directly into threshold comparisons, code dependencies are reduced, and since text is not generated at the decision stage, routing errors stemming from generative text hallucinations are substantially minimized.
However, there are also clear constraints to review before adoption. BF16 half-precision distribution makes single 8GB VRAM GPU operation effectively impossible, and the 27B class requires a single node with 80GB+ VRAM, adding to on-premises costs. The transformers 5.17.0 pin and trust_remote_code=True requirement presuppose compatibility review with existing pipelines. The Jev Decision Index self-evaluation scores and the Qwen3.8-27B base model name designated by the same vendor are vendor claims that have not been externally reproduced, so it is safe to combine public suite scores with in-house workload A/B testing during the adoption phase.
The fact that the vLLM Semantic Router team systematically fine-tuned the Qwen family and unified them under the same API from 0.8B to 27B, and that external models like Clef-omni are adopting the same Jev schema, forming a multi-vendor ecosystem, raises the possibility that decision-dedicated models will become a default layer of the agent stack rather than an ‘experimental option.’ Future easing of the Hugging Face Transformers dependency, release of quantized variants, and reproduction numbers on accelerators beyond MI325X are expected to lower the adoption threshold by another step.
Source Reference
This article was prepared by verifying the following source: MarkTechPost — What is Decision 3.0? vLLM Semantic Router’s New Open Decision Models

Leave a Reply