Small decisions. Interesting possibilities.Submit contentSubmit
Jev Trip preview

Jev Trip

A day-trip planner where a language model drafts and Jev screens the request, places, transport options and plan steps.

Added to Jevfast

How it uses Jev

Before planning, three choice questions check the request: whether it spans more than one day, more than one city, or asks for a booking. During planning, place candidates, transport options and finished plan steps are each checked by a choice question answering pass, flag or unknown against the stated preferences. The controller acts only on an answer whose confidence clears its threshold.

What Jev decides

Request scope screening (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · multi day
YOUR APP
INSTRUCTION

Does the user explicitly request an itinerary spanning more than one calendar day, judged from the meaning of the preference rather than isolated numbers?

STATE

The state is the user's trip preference text. Three choice questions answer pass, flag or unknown, and a flag at or above 0.75 confidence blocks the request with a scope message.

JEV · CHOICE
  1. pass
  2. flag
  3. unknown
Question 2 · booking or transaction
YOUR APP
INSTRUCTION

Does the user ask the product to execute a booking, reservation, purchase, payment, cancellation or order, rather than to recommend places?

STATE

The state is the user's trip preference text. Three choice questions answer pass, flag or unknown, and a flag at or above 0.75 confidence blocks the request with a scope message.

JEV · CHOICE
  1. pass
  2. flag
  3. unknown

App workflow

  1. Screen the request

    Three choice questions decide whether the ask is in scope; a confident flag returns a scope message instead of a plan.

  2. Gather facts

    The controller fetches places and walking or transit routes from the map provider; times and numbers are computed in code, not by a model.

  3. Let the planner draft

    A language model proposes the next activity and repairs steps the checks flagged.

  4. Check the draft

    Place, transport and plan-step questions judge fit, repetition and pace; an answer below the actionable confidence becomes unknown.

  5. Validate and show

    Code validates times, routes and versions, then streams the itinerary with each decision and its reason.

Why it is interesting

Deterministic code keeps the facts, routes and versions while Jev judges only what needs meaning, and a low-confidence answer becomes unknown instead of passing silently.