A family of open System One models by Mark Marosi that softmax option-letter logits at an answer slot: decider-0.8b, 2b, 4b and 35b-a3b on Qwen3.5 bases, decider-12b on Gemma-4-12B-it, and training-free readouts of larger chat models. This page carries decider-2b v11.
Nandakishor M's typed-decision model. A frozen Qwen3.5 backbone is read, never trained, and cut off mid-stack; a small trained physics engine settles each choice, score or yes/no question into calibrated probabilities, a conformal set and an abstain flag. 0.8B and 4B.
Decides
choice, score, noul, classify, route
choice, score, noul, classify, route
Architecture
decider
vega
Fine-tuned from
qwen/qwen3.5-2b-base
qwen/qwen3.5-0.8b
License
apache-2.0
apache-2.0
Availability
Open weights
Open weights
Hosted by
—
—
Input price
—
—
Decision accuracy
75.2%
55.6%
Calibration error
—
0.151
Valid action rate
—
—
Median latency
—
—
p95 latency
—
Figures are from each model’s manifest; accuracy and latency are what the publishers report, on their own suites and hardware. Add a third model.
Questions
What is the difference between decider and vega?
decider is from Mapika and vega from Nandakishor M. Both have open weights you can download and run. Both answer choice, score, noul, classify and route questions. vega reads up to 72K tokens of state, against 32K tokens for decider. vega is the smaller model, at 800M parameters to 1.9B.
Which is more accurate, decider or vega?
They report on different suites — decider 75.2% on Decider regression set, 28 held-out tasks (decider-2b v11), vega 55.6% on His 11 October 2026 benchmark, published with its results and its harness (a notebook in vegaml): macro accuracy over 43 public tasks for the 0.8B, 0.717 for the 4B; with JevBench (231 items) and DecisionBench (1,075 rows), 3,841 decisions in all, seed 20261011. On his own set of 2,050 choice decisions over six intent workflows (esci, clinc150, appliances, banking77, when2call, apibank), one choice question each, which he has not published with its question wording, he reports 0.763 (calibration error 0.026) for the 0.8B with its public_intents adapter, 0.389 without the adapter and 0.803 for the 4B with it. He publishes no accuracy for the typed_decisions adapters — so the numbers do not rank them. Test both on your own labelled examples.
Which is cheaper, decider or vega?
decider: Free (open weights). vega: Free (open weights). Open weights cost nothing per call beyond your own hardware.
Can I run decider or vega locally?
Yes, both: systemone pull mapika/decider and systemone pull nandakishorm/vega download the weights.
His 11 October 2026 benchmark, published with its results and its harness (a notebook in vegaml): macro accuracy over 43 public tasks for the 0.8B, 0.717 for the 4B; with JevBench (231 items) and DecisionBench (1,075 rows), 3,841 decisions in all, seed 20261011. On his own set of 2,050 choice decisions over six intent workflows (esci, clinc150, appliances, banking77, when2call, apibank), one choice question each, which he has not published with its question wording, he reports 0.763 (calibration error 0.026) for the 0.8B with its public_intents adapter, 0.389 without the adapter and 0.803 for the 4B with it. He publishes no accuracy for the typed_decisions adapters
