Jev in production › Agent guardrails and approvals
Local Go gateway checks each coding-agent tool call against deterministic policy, asks Jev for risk and confidence on ambiguous calls, returns allow, ask or block, and fails closed when Jev is unreachable; policy fixtures pass 9/9 (author).
A local safety gateway for AI coding agents. Every tool call goes through jev-guard, which normalizes it, applies deterministic policy, consults Jev for ambiguous cases, and fails closed when Jev is unreachable. A React dashboard manages policy, users, approvals, and audit.
Jev never decides. Jev returns a structured judgment (risk/confidence/action); the Go policy engine turns it into the final allow / approvalrequired / block.
Interactive version (pan/zoom, trace, search): docs/jev-guard-how-it-works.html. Source: docs/jev-guard-flow.workflow.json.
For the project's own README, linking back here: