Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

Before configured tools run, pi-jev sends a summarized action state and user request. Jev answers Noul judgments for destructive, exfiltration, and beyond-scope risk plus an impact Score; separate output checks detect secrets and classify failures. Local thresholds and patterns shape allow, warn, or block behavior.

What Jev decides

Illustrative Jev decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · destructive
YOUR APP
INSTRUCTION

Does the action delete or overwrite data or rewrite shared history?

STATE

Working directory, tool name, truncated argument summary, platform, and user request when available.

JEV · NOUL
YesNo
Question 2 · impact
YOUR APP
INSTRUCTION

Score potential damage if the action is unwanted across four defined levels.

STATE

Working directory, tool name, truncated argument summary, platform, and user request when available.

JEV · SCORE
03

App workflow

  1. Summarize tool action

    Build state from cwd, tool name, bounded arguments, platform, and user request.

  2. Ask risk questions

    Request Noul checks and an impact Score in one call.

  3. Combine evidence

    Apply thresholds and offline pattern checks.

  4. Gate tool call

    Allow, warn, or block according to configured mode and risk.

Why it is interesting

It combines semantic risk questions with local patterns and keeps the guarded arguments bounded before sending them for judgment.