Decision 3.0 Unveiled: Open Multimodal Decision Models (0.6B-27B) Set New Benchmarks for Agentic AI
Event Core
The Decision 3.0 (d3) suite has been released, introducing a specialized family of open-source multimodal models optimized for decision-making. Developed in collaboration with the vLLM team, these models range from 0.6B to 27B parameters and are built upon the Qwen 3.5/3.8 backbones. Supporting text, image, and video inputs, d3 categorizes decision logic into three distinct types—Choice, Yes/No, and Rating—while providing calibrated probabilities. It currently holds the #1 spot on the Jev Decision Index.
- ▶ Shift to Deterministic Agency: d3 pivots LLMs from conversational generation to structured decision-making, significantly enhancing the reliability of AI Agents in execution-heavy workflows.
- ▶ Native Multimodal Reasoning: By integrating vision encoders directly, the models handle complex video and image-based logic, bridging the gap between visual perception and actionable intelligence.
- ▶ Production-Ready Scalability: Optimized for the vLLM inference engine, the suite offers a seamless path from edge deployment (0.6B) to high-throughput enterprise applications (27B).
Bagua Insight
At Bagua Intelligence, we see Decision 3.0 as a pivotal moment in the “unbundling” of the LLM. While general-purpose models excel at reasoning, they often struggle with the deterministic constraints required for autonomous action. By focusing on probability-scored decision outputs, d3 provides the “quantifiable confidence” that developers need to build safe and reliable agentic systems. The choice of Qwen as the foundation further cements the Qwen ecosystem’s dominance in the specialized fine-tuning space. This is a move toward a modular AI stack where generalists handle the thought process and specialists like d3 pull the trigger.
Actionable Advice
Teams building AI Agents or complex RAG pipelines should look to offload decision-making nodes from expensive, general-purpose LLMs to d3 models. We recommend starting with the 1.5B or 7B variants to minimize latency and token costs. Furthermore, developers should leverage the probability scores to implement sophisticated threshold-based error handling, ensuring that low-confidence decisions are automatically routed for human intervention.