Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The Hono router sends an HTTP request’s method, URL, redacted headers, and bounded textual body to Jev, with one yes/no question per registered semantic route. The first route whose probability reaches the threshold receives the request.

What Jev decides

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

Does this request match the registered route description?

STATE

HTTP method, URL, redacted headers, bounded textual request body and registered route descriptions.

JEV · NOUL
YesNo

App workflow

  1. Register routes

    Describe each semantic route in plain language and attach a normal Hono handler.

  2. Check ordinary paths

    Let Hono path routes and middleware handle requests that match before semantic routing.

  3. Evaluate semantic matches

    Send request context to Jev and evaluate the route questions in parallel.

  4. Dispatch by threshold

    Run the first matching handler, or fall through when no route reaches threshold.

Why it is interesting

It adds semantic routing alongside Hono’s ordinary path router, while exposing the decision probabilities to the selected handler and allowing unmatched requests to fall through.