Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The cli-classifier builds a System One request from caller-provided request text, question, and either ordered choice criteria or a yes/no question. It calls the Pi classifier runtime when available or falls back to the Jev CLI. The caller then consumes the classifier result.

What Jev decides

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

Caller-provided choice question.

STATE

Repository-owned Choice test uses state.request="the state text", question="Which option?", and criteria a=First and b=Second. This illustrates the classifier transport, not an observed answer.

JEV · CHOICE
  1. a
  2. b

App workflow

  1. Build classifier request

    Wrap stdin state text under request and build the answer question from caller-supplied type and criteria.

  2. Select transport

    Use the Pi native classifier when preflight permits; otherwise invoke the Jev CLI.

  3. Return result

    Validate the classifier output and return the result to the calling skill or script.

Why it is interesting

It exposes the same small typed classification contract through more than one runtime, while keeping the caller input and criteria explicit.