Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

A MoonBit client calls System One with state plus typed Noul, Choice, and Score questions. The playground uses those decisions in single-question CLI experiments, Gomoku candidate selection, browser next-action selection, and task filtering.

What Jev decides

Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · urgency
YOUR APP
INSTRUCTION

How urgent is this request?

STATE

Customer message: “I was charged twice for my subscription. Please cancel the duplicate charge and refund me.” Subject: “Duplicate charge on my account”; premium subscriber for 3 years.

JEV · SCORE
02

App workflow

  1. Construct the request

    The CLI accepts text or JSON state and a questions file, including mixed typed questions.

  2. Send typed judgments

    The client posts the state and named questions to the System One endpoint and parses typed answers.

  3. Use the decision

    Examples consume the result for a Gomoku move, browser action, task filter, or ESLint judgment.

  4. Inspect experiments

    Replay saved transcripts or consult the experiment documentation for measured decision patterns.

Why it is interesting

It places several decision patterns and language wrappers in one inspectable playground, with example transcripts and measured experiment reports. In Gomoku, code supplies the board and nearby legal candidates while Jev ranks candidate moves.