Backend adaptation is separate from orchestration
The TypeSafe backend converts native request and response shapes; it does not itself decide when a browser action, compaction or writing task should run.
Inspect the supporting source ↗REPOSITORY ANALYSIS
jev-use
A small typed decision layer for agent integrations, with check, pick and rate primitives and explicit escalation to a generative model.
E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
- Stars
- 25
- Forks
- 3
- License
- MIT
- Last commit
- 2026-09-22
What Jev does here
The application dispatches suitable bounded decisions to the backend; the TypeSafe adapter converts native requests and parses answers, while escalation returns unresolved work to the caller.
Exposes the handoff between typed judgments and text generation without claiming that either component owns the whole agent.
Fixed-version documentation and implementation material were inspected on 2026-10-24. No demo, latency or recall experiment was reproduced. Shared API shape does not make different backends behaviorally equivalent.
What task does this project fit?
Share a typed decision API across a generative agent and bounded semantic tasks.
Material analysed：
From input to action
- A pre-call dispatcher separates tasks that should not reach the decision model.
- The Jev client sends check, pick or rate questions through a backend adapter.
- Results that cannot safely settle the requested decision can return escalate for the caller.
Implementation details that matter
A demo is not a universal comparison
The README distinguishes constrained baselines in its Pong discussion. Compare equivalent output spaces and full task conditions before adopting a speed multiplier.
Inspect the supporting source ↗When to choose it
Useful as a small integration layer when the application already owns the task loop. Keep writing with a generative model and honor escalation instead of coercing every result into an action.
How to inspect it yourself
Inspect the README library example and src/backends/typesafe.ts. Trace native-body construction into answer parsing; separately read the dispatcher boundary before considering live calls.
Limits of this review
- No demo, latency or recall experiment was reproduced.
- Shared API shape does not make different backends behaviorally equivalent.