Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The server sends the startup idea as `state.startup_idea` with eight goal-adjusted Score questions, a Choice for product category, and a Noul for understandability. Code normalizes and weights the eight scores, applies a clarity gate, and maps the result to KILL, FIX, or SHIP.

What Jev decides

Illustrative idea-scoring request shape; no Jev response was captured here.Example answers · not a recorded Jev response · Source ↗
Question 1 · problem
YOUR APP
INSTRUCTION

Does `startup_idea` solve a real problem that people actually feel?

STATE

The request state has one field, `startup_idea`, containing the submitted idea; no example runtime value is asserted.

JEV · SCORE
04

App workflow

  1. Submit an idea

    The server validates the idea text and selected goal.

  2. Evaluate dimensions

    Jev receives the idea and asks eight goal-adjusted Score questions alongside category and clarity questions.

  3. Compute the recommendation

    Code normalizes the scores to 0–100, applies goal-specific weights and a clarity gate, then maps the total to KILL, FIX, or SHIP.

  4. Review the breakdown

    The app presents dimension results and a collapsible panel with raw Jev answers and evaluation metadata; successful evaluations can be archived.

Why it is interesting

The verdict is assembled from inspectable dimensions, goal-specific weights, and a separate clarity gate rather than a single free-form model opinion.