mghafiri/qwen3.5-0.8B-decision-model

qwen3.5-0.8B-decision-model

A decision model fine-tuned from Qwen/Qwen3.5-0.8B-Base. It answers typed questions about a state and returns calibrated probability distributions, not generated text:

The interface follows the publicly documented request/response shape of TypeSafe's System One API (docs). This is an independent open model. It is not affiliated with or endorsed by TypeSafe, and it is not Jev.

Head to head: TypeSafe Jev vs this model on unseen scenarios

We sent the same 150 held-out scenarios (714 questions) to both models, as identical POST /v1/systemone requests. None of these scenarios was used to train, select or calibrate this model.

• —Jev: jev-1.13.0 through TypeSafe's hosted API.
• —This model (0.8B parameters): ran locally on a MacBook Pro (Apple M2 Max, 64 GB), not on a GPU server.

What this means:

• —Head to head: on questions where only one model was right, Jev was right 103 times and this model 17. The two models agree on 82.5% of top answers.
• —Jev is the stronger model on accuracy, Brier and confidence-gated automation.
• —This model is a small open alternative that runs fully offline. On a GPU it answers in about 50 ms per request (see the evaluation section below).
• —This model is under-confident. Its average top probability is 0.75, while the labels average 0.87, so it automates fewer decisions at high confidence thresholds.
• —¹ Read log-loss and ECE with care. The labels are soft probabilities written with this project's rubric, and this model was trained on the same labelling style. Jev often answers with near-certainty (42% of its top probabilities are ≥ 0.99), which log-loss penalises whenever the labels spread some probability to other options. Accuracy and Brier are the fairer comparison.

The comparison script and a guide to reproduce it with your own TypeSafe API key are in the project repository (scripts/compare_jev.py, docs/compare_jev.md).

How it works

• —Logit readout. Each question is rendered after the state and ends in Answer:. The probabilities are a softmax of the next-token logits restricted to single-token labels: A… Z/ a… z for options and levels, and yes/ no for Noul. Every answer is a valid distribution over exactly the options you declared, from one forward pass per question, with no JSON parsing.
• —Confidence is (K·p_max − 1)/(K − 1), the definition published at docs.typesafe.ai/confidence.
• —Training objective (RLCD-inspired). Because the output is a distribution, the expected log-score reward equals negative cross-entropy. We therefore minimise CE(target, p) + 0.5·Brier(target, p), two strictly proper scoring rules, against soft expert-agreement targets. TypeSafe has not published RLCD's actual objective, so this is an approximation, not a reproduction.
• —Post-hoc temperature per primitive, fitted on the validation set: choice T=1.3, noul T=1.5, score T=1.2. It is stored in calibration.json and applied by the bundled jevlite package.

Usage

from huggingface_hub import snapshot_download
import sys

path = snapshot_download("mghafiri/qwen3.5-0.8B-decision-model")
sys.path.insert(0, path)              # bundled jevlite/ package
from jevlite.model import SystemOne

engine = SystemOne(path)              # applies calibration.json automatically
print(engine.system_one(
    state="Help! My payouts have been failing for 3 days.",
    questions={
        "is_urgent": {"type": "noul", "instructions": "Does this convey urgency?"},
        "department": {"type": "choice", "instructions": "Which team should handle this?",
                        "criteria": {"billing": "Payments, invoicing, refunds",
                                      "technical": "Bugs, outages, integrations",
                                      "sales": "Pricing, upgrades, new accounts"}},
        "frustration": {"type": "score", "instructions": "How frustrated is the customer?",
                         "criteria": ["Calm", "Frustrated", "Very angry"]},
    },
))

Training data

The dataset has 2000 synthetic English scenarios (9716 questions), each a state plus 3–6 independent questions. It covers 32 domains: agenttoolrouting, airlinetravelops, amlkyccompliance, appmarketplacepolicy, bankingfintech, citationverification, clinicalliteraturescreening, customersupport, cybersecuritysoc, ecommerce, educationadmissions, energyutilities, entitymatching, governmentservices, healthcareadmin, hrrecruiting, insuranceclaims, ithelpdesk, legalcompliance, llmguardrails, logisticssalescrm, manufacturingqa, newsclaimverification, payrollbenefits, procurementvendorrisk, propertymanagement, ragpassagerelevance, smarthomeiot, softwareengineering, spanselectionextraction, telecomsupport, trustsafety_moderation.

• —Question mix: noul 41%, choice 37%, score 22%.
• —Difficulty mix: clear 39%, moderate 31%, borderline 16%, insufficient 9%, adversarial 6%.
• —How targets were made: Claude authored them as the fraction of careful experts who would pick each option. A blind second annotator relabelled every question without seeing the originals.
• —Agreement on the top answer: 9434/9718 = 97.1%.
• —Where the two agreed, the target is 0.6·author + 0.4·reviewer.
• —Borderline disagreements were averaged 50/50.
• —The remaining disagreements were adjudicated one by one.
• —Splits by scenario: train 1700 / val 150 / test 150.

Training

• —Full fine-tune with frozen token embeddings, fp32 weights and bf16 autocast.
• —AdamW, lr 1e-5, cosine schedule. Option-order shuffles were used as augmentation.
• —Epochs run: 10 of 10 requested (completed all epochs), with 2720 optimizer steps in 48 min.
• —The published weights are the checkpoint with the lowest validation cross-entropy: epoch 9.

Evaluation (held-out test split)

Accuracy compares the predicted argmax with the target argmax. Log-loss and Brier are measured against the soft targets. ECE uses 10 bins over the top-option probability (P(yes) for Noul).

Limitations

• —The targets are expert-agreement estimates written by an LLM, not real-world outcomes. Calibration here means calibration to those targets. Validate on your own labelled data before automating decisions.
• —The test set is small (about 714 questions), so ECE is noisy.
• —The model is English-only and text-only.
• —Keep arithmetic, counting and date comparison in code. Ask atomic, literal questions.
• —Use confidence to route uncertain cases to a human or a larger model.