jevbooks

← All projects

hono-jev-router

yusukebe/hono-jev-router

Semantic router for Hono that routes requests by meaning with Jev.

Classification & Routing1.00Runner-up: Verification & GuardrailsQuestionnaireFunnel
Automated README summary

Automatically summarized from the README on 20 Sept 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

An experimental router for Hono where routes are described in plain words instead of method and path. Jev decides which description fits the incoming request. Aimed at developers experimenting with semantic routing.

How it uses Jev

JevRouter sends the request method, URL, headers and body to Jev with one yes/no Noul question per description, evaluated in parallel in a single call. The first registered route whose probability reaches the threshold wins; the result is available as c.get('jev') with route, confidence and probabilities.

Primitives:noul

Technique worth stealing

Describe routes in plain words and let a model pick the first description whose probability passes a threshold.

Try it

npm i hono-jev-router, then register routes with app.on('jev', description, handler).

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.86
  • Shows a System One patternnot found in the excerpt0.15
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.05
  • Is a runnable toolFound in material0.94
  • Top-10 learning shortlist signalnot found in the excerpt0.36
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale0.81 / 2
  • About JevFound in material0.98
Signals
Jev is core to the project0.86Shows a System One pattern0.15Describes handling uncertainty0.05Reports measured numbers0.05Is a runnable tool0.94Top-10 learning shortlist signal0.36Is a replica of the model0.0400.51Solves a common problem (0–2)0.81 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.97Funnel0.77Question bank0.57Prefetch0.25Inspection0.2300.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 20 Sept 2026.