Is this a general decision framework or a one-off demo?

A one-off. The board is hard-wired to a shortlist of eleven ideas for a specific stream, and the README frames the output as the MVP that gets built next on that stream. The System One pattern is real, but the option set is not something you swap out and reuse for your own decisions.

Does the model make the choice, or does the code?

The code does. Following the System One split, the model only answers narrow typed questions, while gates and weights are applied in the composition module rather than left to the model. Blocked ideas are filtered out before a winner is printed, so the pick is a function of the scoring code as much as of Jev's answers.

Does Jev just pick the idea with the most stars?

No, and the README is explicit that stars are only interest and that live shippability outranks them. The shortlist carries manual marks where a blank is neutral, an asterisk is a mild signal and X is caution, and shippability is one of the per-option questions fed into the weighting.

Do I need a TypeSafe key set up in the environment first?

No. You can paste a key into the Ask JEV panel, which is sent to the decide endpoint and never written to disk, or set TYPESAFE_API_KEY for a server-side default. The documented path is npm install, copy .env.example to .env.local, then npm run dev on port 4317 and open the board locally.

How do I run it, and how is the key handled?

npm install, copy .env.example to .env.local, paste a TYPESAFE_API_KEY, then npm run dev -- --port 4317 and open http://127.0.0.1:4317. You can also paste a key in the board without the env file; it is sent to /api/decide and is not written to disk.

What typed questions does the board ask Jev?

One Choice question for the pick, three shared questions, and four questions per option covering fitness, shippable, JEV-native and blocked. Jev answers them in parallel, and code in src/lib/jev/compose.ts, not the model, applies gates and weights fitness, shippability and native-JEV fit.

What does the briefing sent to Jev contain?

A structured briefing built in src/lib/jev/briefing.ts: the goal, the constraints, what this machine actually has, and a card for every one of the eleven candidate ideas. The approach keeps control flow in code, asks narrow questions, and composes probabilities.

CommunityJev Demos & Experiments

Harden Jev Decides

A decision board that sends one System One request describing eleven stream ideas, then lets code gate and weight Jev's answers into a single pick for what to build next.

See highlights

Open github.com

Stars: 1
Language: TypeScript
Published by: Community
Author: tylerjharden
Last verified: Oct 2026

tylerjharden/harden-jev-decides

User repository on GitHub

View on GitHub

JEV picks which stream idea becomes the live MVP. TypeSafe System One decision board.

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

JEV picks which stream idea we turn into a live MVP. The board sends TypeSafe one System One request: a structured briefing of the eleven notes, plus typed questions. JEV answers them in parallel. Code gates blocked ideas, weights fitness / shippability / native-JEV fit, and prints a winner. Stars are interest. X is caution. Live shippability in this environment outranks a star. Open You can also paste a key in the board without putting it in the env file. The key is sent to /api/decide and is not written to disk.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification Jev for Routing

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

A single System One call carries a structured briefing of all eleven ideas plus typed questions, and Jev answers them in parallel.
Code, not the model, applies the gates and weights, with briefing, question building and composition split across separate files under src/lib/jev.
Each option gets four questions on fitness, shippability, JEV-native fit and blocked status, on top of one Choice for the pick and three shared questions.
It runs without a server-side key: you can paste a TypeSafe key into the panel and it is posted to the decide endpoint without being written to disk.

Watch out

This is a self-referential board, not a general decision tool. The eleven ideas are one stream's shortlist and the marks beside them are the author's own hand annotations, where X means caution and the stated rule is that live shippability outranks a star. The README documents the wiring but reports no accuracy, latency or cost measurements, and it does not publish the gate thresholds or weight values, which live in code. The winner is simply the idea the stream builds next, so there is no downstream result to check the pick against. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

ui-generator-instinct-jev

Demo that turns free-text UI descriptions into real shadcn components using only Jev typed Choice, Noul, and Score answers, with no generated code on the decision path.