Introduction & quick start ↗
Start here to understand state, questions and answers before sending a request.
docs.typesafe.ai
A guided path through TypeSafe’s documentation, demonstrations and published evaluations.
Start with the basics, choose a workflow, then check limitations and evaluation examples.
Start here to understand state, questions and answers before sending a request.
docs.typesafe.ai
Choose a category, an ordered rating or a yes/no probability to match the result your code needs.
docs.typesafe.ai
Work backward from product behavior, keep rules and execution in code, and use Jev for the semantic judgment.
docs.typesafe.ai
Install the official skill so Codex, Claude Code or another coding agent can find current Jev patterns and API guidance.
docs.typesafe.ai
Use a decision and its confidence to choose when to act and when to ask for review.
docs.typesafe.ai
Ask candidate questions together, then let code use the relevant answers. Useful when calls do not truly depend on one another.
docs.typesafe.ai
An example of device-control questions, result selection and a fallback to a text-generating model.
docs.typesafe.ai
Scan decision patterns by industry, then translate a promising idea into explicit state, questions, code policy and review paths.
docs.typesafe.ai
Screen LLM inputs and outputs with separate hazard judgments, then let explicit code thresholds pass, review, block or route.
docs.typesafe.ai
Distinguish confidence from answer probability. Noul has no separate confidence field.
docs.typesafe.ai
Read the documented weak spots and turn relevant ones into test cases for your application.
docs.typesafe.ai
Check model identifiers, pricing and input limits before configuring a deployment.
docs.typesafe.ai
Find the side-by-side, Doom and Wikiracing demonstrations. Read the conditions beside each demo.
typesafe.ai
Read the publisher’s case against optimizing for public leaderboards and its stated preference for dated, caveated evaluation snapshots.
typesafe.ai
Explore four publisher-evaluated workflows. Their reference answers are based on model consensus.
evals.typesafe.ai
Inspect a customer-service workflow, including inputs, code policies and prediction disagreements.
evals.typesafe.ai
The Workbench gives the reading path a practical next step: encode one Choice, Score, or Noul policy, keep ambiguous cases in review, and test it without handing the product control of downstream actions.
Google sign-in · provider key stays server-side · no automatic tool actions · no payment required during beta