Glossary: Verdict
Verdict is jev.pro’s name for the action your code commits after reading Jev (System One) answers: allow, review, block, route, or abstain. It is not a TypeSafe response field, not a /v1/verdict route, and not a paragraph of reasoning. A Choice choice is a label, not a verdict. Combine the label with confidence (or a Noul band) and your policy.
This glossary entry is for builders who already heard of Jev / System One and need a citable definition before they ask the model to write the decision as prose. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Confirm answer fields on docs.typesafe.ai. We do not sell or issue API keys.
How it shows up
Log both the raw signals and the verdict so reviewers can disagree with the policy without blaming the model for a rule you wrote. Persist that pair in a decision trace / audit trail. The action space is the closed set of verdicts you allow; naming a Choice option approve_transfer does not call a bank API.
Thresholds turn signals into verdicts. TypeSafe example floors (0.5 unsure, 0.9 irreversible) are illustrations. Noul has no confidence; do not copy a Choice floor. Pin jev-1.13.0 once fitted; jev-latest can move. Schema-safe ≠ factually correct: a 200 with choice: "allow" is still only a label until your code commits the side effect.
Jev does not generate a “because…” essay. If compliance wants a paragraph, generate it later and label it assistance.
Contrast
Verdict vs signal. Signal = typed answer. Verdict = committed act.
Verdict vs Choice choice. The winner is one input to the verdict function. Low confidence can override a confident-looking key into abstain.
Verdict vs action space. The action space is the menu. The verdict is the item you picked this time.
Verdict vs intent. Intent routes among handlers. The verdict is what you did after routing (including hold).
Common mistakes
- Inventing a
/v1/verdictendpoint. - Asking Jev to write the verdict as text.
- Logging only the verdict and dropping
probabilities. - Equating
choicewith the side effect. - Treating schema-safe allow as “the invoice is real.”
See also
FAQ
Does the API return verdict?
No. You compute it. Do not invent a /v1/verdict route.
Can I ask Jev to write the verdict as text?
Don’t. That fights the product contract. Keep the verdict an enum in code.
Is abstain a verdict?
Yes, if your action space includes it. It is still computed in code.
Should reviewers see the signal?
Yes. Otherwise they cannot tell a policy bug from a model miss.
Limits
This is a jev.pro working definition unless TypeSafe uses the same word as an API field. We do not invent search volume. Schema-safe answers are not automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.