Pi Jev Guard

It reviews proposed code edits against your repository's Markdown rules before Pi writes them, using TypeSafe Jev, and returns the exact instruction text and source line range for each detected violation. Informative mode reports findings without blocking; enforcement mode blocks detected violations in reviewed code.

It selects one instructionRoot when the policy loads, by default the Git repository root containing Pi's working directory. Edits under that root are reviewed, including tests outside Pi's working directory; edits in another repository return status skipped with no Jev request in either mode.

pi install git:github.com/Reindeer-AI/pi-jev-guard, then set TYPESAFE_API_KEY in Pi's environment and restart Pi. It requires Pi 0.85.1 or newer and Node 22.19 or newer, and it does not read .env files automatically - use your shell or a secret manager.

Copy the starter config into .pi/jev-guard.md with curl, edit its frontmatter plus the paragraphs or list items under the Rules heading so each rule describes one requirement judgeable from changed code, then run /jev reload. Pi must trust the project before its project-local config is used.

No. Enforcement blocks detected violations only in code selected for review. Out-of-scope edits return skipped and are permitted in both modes, and onUnavailable: block does not block a skipped edit because no evaluation was attempted. Policy-file approval requirements still apply separately.

Only if you deliberately widen the active config's root to a common parent, for example instructionRoot: /workspace, then run /jev reload. A shared root still uses one config: the guard does not automatically load each target's .pi/jev-guard.md, so use separate Pi sessions for independent configurations.

Reindeer-AI publishes it under the logicrw listing, and GitHub metadata shows no license for the repository. The README calls it a semantic review aid, not a replacement for tests, linters or a security sandbox, and it ships a generic starter policy with no organization-specific rules.