Screen inputs and outputs for injected instructions, policy breaches, and answers that disagree with themselves.
A compliance review is a fixed checklist run against a changing document. Jev answers the whole checklist in one request, returning a probability, a label or a rated level per item, so code can clear the clear-cut findings and send the borderline ones to a person.
Put one Jev request in front of an LLM and one behind it. Yes/no questions return the probability that each hazard holds, a Score rates how much harm complying would do, and your thresholds turn those numbers into pass, review, block, or a crisis path.
Run a rubric over the same document several times and compare the answers. The spread tells you which items sit safely away from a threshold and which ones wobble across it. TypeSafe documents that Jev does not guarantee structural identities between related questions, so code has to enforce those.
A semantic lint is a rule you can state in a sentence but cannot express in a regular linter. Jev turns each rule into a yes/no question over one diff hunk and returns a probability, so CI can comment on the likely violations and stay quiet about everything else.
Things people have built and written that match one of the use cases above.
The 1,863-point, 490-comment launch thread. Top comments argue the frontier-model framing is misleading, dispute the cannot-hallucinate claim on the grounds that type safety is not factual correctness, and note grammar-constrained decoding on ordinary LLMs already covers much of the interface.
Declares typed input/output Signatures for LLM modules and optimizes the underlying prompts and weights against a metric. Its Signature abstraction is the closest widely-used open equivalent of Jev's typed-question interface. Star count is GitHub's rounded display figure.
Guarantees valid structured output during generation by constraining decoding to a grammar or schema. The mechanism HN commenters repeatedly cited as already covering Jev's cannot-produce-a-type-error guarantee on ordinary LLMs. Star count is GitHub's rounded display figure.
Places Jev as a fast supervisor above slower Codex coding agents. Codex workers do the engineering while Foreman independently assesses whether the work is complete, requirements are met, tests suffice, or human input is needed.
Staged code-review workflow with a local dashboard, where Jev judges code changes or a whole codebase.
Local-first MCP plugin giving Claude Code, Codex, Cursor and OpenCode structured code-quality scores (correctness, complexity, modularity, security) while they work. Sends focused diffs to Jev and keeps keys and code local.
Guardrails for the Pi agent built on pi-typesafe. Jev judges irreversible and off-task tool calls, detects stuck loops, checks unverified completion claims and flags low-quality output, steering the agent rather than interrupting the user.
Extension making Jev the decision layer for the Pi coding agent: a measured tool-call gate plus a jev_ask tool. Judges whether an action is destructive, exfiltrates data or exceeds scope, then blocks or warns on calibrated thresholds.
Scores source-file quality by asking Jev a set of yes/no questions, runs the test command you already use, and turns uncovered paths into small queries a coding agent can work through. Scoring costs about a cent per megabyte of source; coverage needs no account, config file or hosted service.
Real-time Discord moderation bot that runs Jev evaluations over message text and metadata in parallel to catch phishing, spam and social engineering, with a progressive escalation ladder.
Auto mode for the Pi coding agent, which has no permission system of its own. A deterministic layer handles hard denies and your allow and deny patterns, then Jev judges the bash, write and edit calls it escalates and fails closed when it cannot decide. Thresholds come from recorded real-API calibration.
Agent-ergonomic CLI for Jev with pick, rate, check, rank, triage and guard subcommands, meant for agents offloading snap judgments from the shell.