jev-3000
Small web demo of Jev's Noul, Choice and Score primitives with branch composers, probability bars and a warm-connection latency demo.
Overview
DecisionMachines3000 (jev-3000) is a small demo of TypeSafe's Jev and its three primitives. Each primitive has its own panel with a tree-based branch composer for building questions and state, alongside a JSON editor for editing the same request by hand; a readout renders the answers with probabilities drawn as bars. A separate demo shows the latency difference between a cold TypeSafe connection and one that has already been warmed up.
It is aimed at developers learning the primitives. It also doubles as an example of secret handling: the API key is never stored in the repo but loaded from 1Password through Varlock, using a committed .env.schema that validates, redacts and types the variable. It requires Node 24, the Vite+ toolchain (vp) and the 1Password CLI.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | User-composed yes/no question | yes · no |
| Choice | User-composed choice question | — |
| Score | User-composed score question | — |
How it works
- Compose a question and state in a panel or JSON editor
- Send to Jev
- View probabilities as bars
- Compare cold and warm connection latency
Strengths
- Visual way to learn the three primitives
- Shows the latency benefit of warm connections
- Key kept out of the repo via 1Password and Varlock
Caveats
- Setup depends on 1Password CLI and Vite+
- Demo only
Getting started
`vp install` then `vp dev`, with TYPESAFE_API_KEY resolved from 1Password via Varlock.At a glance
- Type
- App
- Status
- prototype
- Language
- TypeScript
- Runtime
- browser (Vite+)
- Has code
- yes
Use cases and integrations
How curated lists describe it
Demo of TypeSafe.
wh000wh000/awesome-jev-live
Frequently asked questions
What does the demo show?
How Noul, Choice and Score requests are built and what their probability outputs look like.
What is the warm-connection demo?
A comparison of latency between a cold and an already-open TypeSafe connection.
Where is the API key stored?
In 1Password, loaded at runtime through Varlock.
Related projects
Server behind api.typesafe.pro, a free anonymous System One-compatible endpoint that forwards to TypeSafe on the operator's key.
ServiceproductionBrowser form for building Jev requests from pasted text without hand-writing JSON, then rerunning to see how steady the answers are.
ProjectbetaJavaScriptTerminal REPL for shaping System One requests before writing code, with lessons, a sketch editor, conversation turns and offline simulation.
ServicebetaTypeScriptNushell module for TypeSafe's System One API: pipe content in, ask noul, choice and score questions, and filter on the numbers.
ServicebetaNushellOne-page playground and test bench for Jev with TypeSafe, OpenRouter, LLM-baseline and mock backends behind one /v1/systemone contract.
ServiceprototypeTypeScriptStatic browser interface for making structured Jev decisions through the Pollinations API, with multilingual READMEs.
ServiceprototypeJavaScript