A support ticket needs a route. A tool call needs a risk label. A request needs a model tier. Those are bounded judgments, not writing tasks.
If you ask a chat model for JSON, parse it, and call that automation, you are still recovering a decision from generated text. For those paths you want typed answers, usable uncertainty, and latency that fits an interactive request.
That is the gap a System One decision model is aimed at: state in, typed probabilities out. Keep the generative model for plans, edits, and repairs. Put classification, routing, scoring, and gating in a decision layer.
Top comments (0)