Open· Last updated 2026-09-21

Jev design checklist

This design checklist is an independent production gate, not a rewrite of TypeSafe’s narrative how to build page. Open-cluster pages are not official and not endorsed. Confirm facts on docs.typesafe.ai. We do not sell keys.

Before you pick primitives

• Write the action space (including abstain) in one enum.
• Mark which actions are irreversible vs read-only (risk-scaled floors later).
• List judgments a knowledgeable person could make in a few seconds — one judgment per question.
• Move counts, dates, money compares to code.
• Decide what must stay on-prem (then Jev may be the wrong door).

State and questions

• Sketch the filtered state object; name fields you will backtick.
• Choose Choice / Score / Noul per action, not “one Score for everything.”
• Add other / none on every Choice that can be wrong.
• Align instructions with criteria (no inverted true/false).
• Plan a cascade + confidence abort if the taxonomy is deep (vs classifiers).
• Generation (replies, emails) is explicitly out of scope for Jev.

Product / GEO gates (this site’s bar)

• One primary intent per URL you will publish internally.
• Vendor latency and $ labeled as vendor claims.
• Schema-safe ≠ correct is written next to any “can’t hallucinate” quote.
• Official docs link: https://docs.typesafe.ai
• No “we issue keys” language in your console copy either.

Next: implementation checklist. Hub: Open.