Assistant state
Message, page, trace, intent, or task context. Keep the state small enough to audit.
A Jev assistant is not another chat wrapper. It uses Jev for the small, repeatable decisions that make an agent feel fast and reliable: which model to call, which tool to use, which browser action is safe, or whether a page answers an AI assistant's question.
Message, page, trace, intent, or task context. Keep the state small enough to audit.
A bounded Choice, Score, or Noul with a probability—not a paragraph that code has to parse.
Application code calls a tool, chooses a model, retries, asks for approval, or hands control back.
The useful boundary is simple: the assistant or frontier model keeps the open-ended plan, while Jev handles a closed decision surface. That makes the output easy to test and lets ordinary code enforce thresholds, fallbacks, confirmation gates, and audit records.
These cases are linked to the exact source post. Repository buttons appear only where the public repository was checked; numbers remain attributed to the original author.
A QA loop where Jev selects browser actions while a frontier model plans and vision verifies.
Jev role: Browser action selection, retry and human-review routing
A bounded browser-action tool for Claude Code and OpenCode on a real logged-in Chrome session.
Jev role: Pick the next click or type action on the visible page
One-call browser sub-tasks for Claude Code and Codex, with Jev choosing each low-level action.
Jev role: Click/type selection and stop-or-return routing
Jev exposed as a governed, discoverable tool alongside DigitalOcean's large tool catalog.
Jev role: Typed classification and probability output through a governed MCP endpoint
A governed execution layer that turns Jev probabilities into deterministic policy actions.
Jev role: Translate a typed decision into ALLOW, ASK, or DENY before tool execution
An MCP connector that gives Claude Code, Claude Desktop, and Codex typed Jev judgments.
Jev role: Return structured answers and probabilities for bounded questions
A per-turn router that sends easy Claude Code or Codex work to a fast model and hard work to a stronger one.
Jev role: Assess task difficulty and choose the model tier
A personal assistant that uses Jev to classify email work and trigger proactive analytics.
Jev role: Email classification and proactive-workflow routing
A page-scoring workflow that asks whether an AI assistant can find the answer.
Jev role: Score page answerability for an AI assistant
A voice assistant that uses Jev to route between a fast local voice model and a larger LLM.
Jev role: Intent routing between fast and large voice-model paths
Jev chooses tools while a small extraction model turns the request into arguments.
Jev role: Tool selection before argument extraction
Jev is a typed decision layer. The assistant gives it a bounded state and a question such as which tool, model, browser action, or review path should happen next. Jev returns a structured choice, score, or probability; application code then executes the selected path.
Usually no. The strongest examples keep a generative model for planning, writing, or open-ended reasoning and use Jev for repeated bounded decisions such as routing, tool selection, browser actions, evaluation, and guardrails.
Start with the exact source post and repository when available. Identify the state Jev sees, the bounded decision it returns, the code or tool that acts next, and which metrics are author-reported versus independently reproduced.
Yes. One sourced case uses Jev to score whether pages answer an AI assistant's question, then uses engineering changes such as prerendering and structured metadata. Treat those score changes as author-reported until the rubric and measurements are independently verified.