Glossary: Decision contract
Decision contract is jev.pro’s term for the triple you actually ship: (1) the state shape, (2) the questions map (types, instructions, criteria), (3) the code that maps answers to actions and abstentions. It is not a TypeSafe legal term, not a DPA, and not an API type. TypeSafe documents HTTP fields on POST /v1/systemone; they do not ship a DecisionContract object.
This glossary entry is for builders who already heard of Jev / System One and need a citable definition before they scatter floors across three services. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Confirm request shapes on docs.typesafe.ai. We do not sell or issue API keys.
How it shows up
Pin jev-1.13.0 (or the current versioned id) as part of the contract once floors are fitted. jev-latest currently aliases that id on the vendor snapshot we read; aliases move. Change weights in code without hoping a monolithic prompt rebalances. Keep instructions, criteria, and floors in one reviewable file so a diff shows the closed set.
The contract’s question types are Choice (unordered, max 255, choice + probabilities + confidence), Score (2–10 ordered levels, fractional score allowed, legend + probabilities + confidence), and Noul (P(yes) 0–1, no confidence). Question IDs are not used in inference. State is text/JSON only. Confidence is derived from the distribution on Choice/Score; calibration is group-level under the RLCD vendor claim.
The action space is the finite side-effect set, including abstain. Thresholds live in your service, not in an undocumented request field. Schema-safe ≠ factually correct: a 200 with a closed key can still be the wrong department.
Contrast
Decision contract vs action space. The action space is the verbs. The contract also includes what you ask and how you cut.
Decision contract vs guardrail. A guardrail is one contract applied to untrusted text. Not every contract is a safety screen.
Decision contract vs schema validation. 422 means the body failed TypeSafe’s published shape. The contract is the product policy on top of a valid body.
Decision contract vs legal MSA. Legal terms live on TypeSafe’s legal pages. This page is engineering.
Common mistakes
- Calling this a DPA or treating jev.pro as counsel.
- Fitting floors on
jev-latestand never pinning. - Leaving criteria in one repo and τ in another with no shared review.
- Asking Jev to “apply the contract” as prose.
- Treating a valid schema as a correct fact.
See also
FAQ
Is this a DPA or MSA?
No. It is an engineering contract. Legal terms live on TypeSafe’s legal pages.
What belongs in one file?
Instructions, criteria, and floors — so reviewers can see the closed set in one diff.
Is decision contract an official type?
No. Unofficial working term. Canonical fields: docs.typesafe.ai/api.
Do I include the model alias in the contract?
Include the versioned id once floors are fitted. Log response.model.
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.