jevbooks

← All projects

usher-point

juanpiRiv/usher-point

CLI that decides where a task runs and dispatches it.

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

usher-point is an on-demand CLI for developers that decides where a task should run — inline in Claude Code, via Codex CLI in a sandbox, or in an isolated Orca worktree — and optionally which skills and model to use, then dispatches it.

How it uses Jev

With --engine jev, usher-point optionally calls TypeSafe AI's Jev model via OpenRouter to return target + relevant skills + an optional model/effort override in one call. --engine auto tries Jev first and fails closed to the heuristic on any problem; --engine jev fails loudly.

Technique worth stealing

Fail-closed routing: try the model, fall back to inspectable heuristic rules on any problem.

Try it

npm install -g github:juanpiRiv/usher-point, then run usher or usher-point route "task".

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 projectnot found in the excerpt0.05
  • Shows a System One patternnot found in the excerpt0.28
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolFound in material0.95
  • Top-10 learning shortlist signalnot found in the excerpt0.16
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale1.16 / 2
  • About JevFound in material0.75
Signals
Jev is core to the project0.05Shows a System One pattern0.28Describes handling uncertainty0.05Reports measured numbers0.04Is a runnable tool0.95Top-10 learning shortlist signal0.16Is a replica of the model0.0400.51Solves a common problem (0–2)1.16 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.87Fail open, fail closed0.8700.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.