# Hugging Face — Decision Models in Hugging Face

- Company: Hugging Face (huggingface.co)
- Announced: 2026-11-10
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://huggingface.co/blog/decision
- Record: https://forck.live/items/34062-decision-models-in-hugging-face
- Subject: Platform
- Models affected: autotrust/GEV-26B-Decide, facebook/bart-large-mnli, ggml-org/gemma-4-e4b-it-GGUF:Q4_0

Hugging Face published an explainer on decision models, which take a state and a set of predefined answers and return a structured decision with probabilities instead of generating text. The post contrasts them with prompting an LLM for JSON, which can produce invalid output, unexpected keys or answers outside the allowed choices, and with constrained decoding libraries such as Outlines and XGrammar that enforce schemas but add computational work. It traces the term to TypeSafe AI's Jev, described as a System One model, and says the community settled on "decision model" because it names the model's computational role rather than a theory of cognition. The interface is given as state plus questions plus allowed answers producing decisions and probabilities, illustrated with a customer-support ticket routed to billing, technical or sales. The post also compares decision models with traditional classification, whose output classes are baked into the classification head, and with zero-shot classification, which takes candidate labels at inference time.

## Evidence

Verbatim from https://huggingface.co/blog/decision:

> Large Language Models (LLMs) are exceptionally good at generating text. We use them to answer questions, write code, reason about problems, and so much more. But not every problem requires generating text.
> 
> Consider a customer support system receiving the following message:
> 
> "I was charged twice for my subscription. I need a refund today."
> 
> The system needs to determine which team should handle the request, how urgent it is, and whether the customer is requesting a refund.
> 
> We could ask an LLM to return a JSON object containing these answers.
> 
> llama cli -hf ggml-org/gemma-4-e4b-it-GGUF:Q4_0 > We have the following customer support ticket, "I was charged twice for my subscription. I need a refund today." , which team should handle the request, how urgent it is, and whether the customer is requesting a refund. Give the answers in JSON. [Start thinking] ... [end thinking] ```json { "team_to_handle" : "Billing" , "urgency" : "High" , "request_refund" : true }
> 
> But what if the model could directly evaluate the available options and return a probability distribution over them, without generating any text ?

---

Record: https://forck.live/items/34062-decision-models-in-hugging-face
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
