Jev for product teams
Product managers should write the action space (including abstain) before anyone opens an SDK. Jev implements judgments; it does not invent the product.
Unofficial product notes — Jev implements judgments; it does not invent the product, and jev.pro is not TypeSafe PM. Design gates: design checklist. Canonical: docs.typesafe.ai. Replicas are not Jev and not endorsed.
UX implications
If you auto-act, show what you did. If you abstain, say a human will look — do not emit a generated apology from Jev (it cannot).
Scope control
One primary intent per surface. Do not ship a mega-Choice with 80 product questions. Decompose.
One intent per surface
SEO-GEO on this site is also a product rule: one primary decision per flow. A settings page that asks Jev twenty unrelated questions in one catch-all Choice will be unmaintainable and, on jev-1.13, worse as state and criteria sprawl.
Write the abstain UX before the happy path. Users forgive “a human will look.” They do not forgive a confident wrong refund.
Pair with design checklist before implementation.
Write the abstain UX before the happy path
If you auto-act, show what you did and how to contest it. If you abstain, say a human will look — do not emit a generated apology from Jev (it cannot generate). If the door times out, the empty state is still a product surface: review, not a spinner that becomes a hallucinated enum from another model.
The action space — including abstain — is the product spec. See action space. Ops will staff whatever remainder you create; read for operations before you promise “deflection.”
Noul 0.5 is official “yes and no equally likely.” Shipping a floor there on money movement is a product decision, not a model default. Pin jev-1.13.0 once floors exist so jev-latest cannot move the UX under you.
Name the surface, then compose
Official how-to: snap judgments, decompose. Name the surface (Checkout.riskScreen, Inbox.route, Moderation.hold) and give it one job. Compose with an LLM only after the decision — when to use Jev. Do not ship “our AI brain” as a chatbot that happens to call System One.
Vendor speed/cost multiples and list price $0.042 / M input (confirm models page) are vendor claims. Do not put them in release notes as if you measured them.
Audience checklist (PM + design)
- Action enum includes
review/ abstain and a timeout default. - Copy never says “Jev thought” or “the model explained.”
- One primary intent per surface; extra questions are extra hops or extra files.
- Floors have an owner and a flag; lowering τ is a launch, not a hotfix.
- Gold cases include the ugly remainder, not only the demo ticket.
- Jaggedness out of scope: math, dates, generation, persistence.
When not to use this page’s advice
Do not treat this as TypeSafe’s roadmap. Do not use Jev as a feature-flag service. Do not copy floors onto SemIf/OpenJev and call the UX “Jev.” Schema-safe ≠ the judgment is correct — plan contestability anyway.
What this page does not claim
- Not a roadmap template for TypeSafe.
FAQ
Is Pro a paid Jev tier? On this site, Pro means production craft — not a SKU.
Chat product? Jev can route; an LLM talks. See when to use.
Who writes criteria — PM or engineering? PM owns the intent and the enum; a named reviewer ships the wording in git. Live-edit in a console is how silent false-allows ship.
Can abstain be “the model failed”? No. Abstention is a successful product path when the floor says so.
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: design checklist, glossary action space, for operations. Canonical: https://docs.typesafe.ai.