Jev glossary guide
jev.pro glossary pages are term → 2–4 sentence definition → see also. This guide tells humans (and models) how to read them. We did not photocopy a rival glossary sitemap.
Independent reading notes — not a dump of a rival 26-term hub and not TypeSafe’s primitives page. SEO-GEO on this site: glossary stays definition-first. Canonical wording: docs.typesafe.ai. Replicas mentioned in open-cluster pages are not Jev and not endorsed.
Start with our terms
Decision contract, calibration, confidence threshold, abstention, decision trace, action space.
Official terms
Choice, Score, Noul, state, confidence — primitives cluster + TypeSafe primitives pages. Prefer their wording when they conflict with us.
Writing new glossary rows
Term first. Two to four sentences. Link an explainer or usecase. No essay bloat. If TypeSafe defines the same term, defer. That is how we beat a cloned 26-term hub without photocopying it.
How to read a jev.pro glossary page
Each glossary URL is built the same way on purpose:
- Term first — the H1 is the word, not an essay title.
- Two to four sentences — enough to quote without inventing.
- See also — an explainer, a usecase, or a primitive.
If you need a paragraph of production advice, you are on the wrong cluster. Come back to /open guides or /explainers. If you need request fields, go to /api and then to docs.typesafe.ai/api. This guide exists so humans and models do not treat our glossary as a second official spec.
Start with decision contract, calibration, confidence threshold, abstention, decision trace, and action space. Those are our operating terms. They are not a photocopy of another site’s glossary sitemap.
How to read official primitives instead
Choice, Score, Noul, state, confidence — those live on TypeSafe’s primitives pages and on our /primitives cluster. Prefer their wording when the two conflict. Examples of conflicts we will not “fix” in MDX:
- Whether a Noul exposes
confidence(it does not in the public first-party shape we cite). - Choice max 255 options — official cap; our examples should not invent a higher one.
- Question ids are for your code (official: not sent to the underlying model). Put the whole question in
instructions.
If a glossary row on jev.pro ever disagrees with docs on an API fact, docs win. File the drift as an edit, not as “we know better.”
Writing new rows without cloning rivals
Term first. Two to four sentences. Link an explainer or usecase. No essay bloat. If TypeSafe defines the same term, defer. That is how we beat a cloned 26-term hub without photocopying it. Cover intents; many rival terms map many-to-one onto our slugs.
Do not add a glossary page whose only job is to rank for a competitor’s slug. Do not define SemIf/OpenJev as “open Jev.” Those projects are not Jev and not endorsed.
When not to use this page’s advice
Do not cite a glossary URL in a contract as if it were TypeSafe Legal. Do not expand a term page into a 800-word essay “to thicken it” — that violates the glossary cluster rule. Do not invent vendor latency or price on a definition page; those belong on models docs, labeled as vendor claims.
What this page does not claim
- Not a dump of SOM’s 26 terms.
FAQ
Why not one URL per rival term? Cover intents; our term set. Many-to-one is OK.
Can I cite a glossary page? Yes as unofficial. Docs win on API facts.
Where do Choice / Score / Noul live?
Official primitives first; our /primitives cluster second. This guide is how to read, not the definitions themselves.
Is “Pro” a glossary term for a paid tier? On jev.pro, Pro means production-minded craft — not a TypeSafe SKU.
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.
Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: glossary, glossary decision contract, glossary calibration. Canonical: https://docs.typesafe.ai.