Pi Jev Auto Mode
A fail-closed permission gate for Pi that asks Jev to judge tool calls left undecided by hard rules.
Added to Jevfast
How it uses Jev
Pi first applies deterministic hard-deny rules to proposed bash, write, and edit calls. Calls that reach the semantic layer are judged by Jev for allow/block decisions; configured thresholds and uncertainty handling determine the gate result.
What Jev decides
Flagged tool-call checkExample answers · not a recorded Jev response · Source ↗
Question 1 · intent coverage
YOUR APP
INSTRUCTION
Is the flagged tool call part of the user request or necessary to complete it?
STATE
A proposed Pi tool call and the user request are included in the bounded state. The intent_coverage rule is asked only for a deterministically flagged dangerous shape.
JEV · NOUL
YesNo
App workflow
- Apply deterministic rules
Block hard-denied patterns before they reach the model; determine which remaining calls enter semantic review.
- Judge eligible calls
Send the proposed tool call to Jev and obtain probability judgments for the policy rules.
- Resolve the gate
Apply configured thresholds and uncertain-result policy; unavailable Jev blocks the call by default.
- Inspect and tune policy
Use Pi commands to view thresholds, change uncertainty handling or scope, and review the active status.
Why it is interesting
The two-layer gate combines hard rules with a semantic decision and fails closed when Jev is unavailable. Operators can inspect and tune thresholds, scope, and uncertain-result behavior, with project overrides limited to trusted projects.