JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Technical guide

Check an AI assistant's next step with Jev

These examples use Pydantic AI, a toolkit for AI assistants, to ask Jev a question before another model runs, a computer command executes, or a game action is chosen.

Original by adtyavrdhnGuardrails

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“Pydantic AI + Jev examples” by adtyavrdhn. Read the original source.

This expanded guide is an AI-narrated adaptation prepared by JevMade. It expands the source’s essential ideas, examples and caveats in JevMade’s own words and is not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

Our summary

An AI assistant can call other models and computer tools. These examples use the Pydantic AI toolkit to put a Jev check immediately before a particular step. Examples include reviewing a request, considering a computer command, and choosing an action in a simple game.

The program supplies a small amount of relevant information and asks yes or no, or offers a list of actions. It then compares the answer with its own rules. Those rules decide whether to continue, decline, or follow another path.

An AI check can misunderstand unfamiliar or misleading information. It is not enough to protect a dangerous tool by itself. Ordinary software must still restrict permissions, check command details, and limit the environment in which actions run. Serious consequences may also justify asking a person.

Key takeaways

  1. Check immediately before the step that may need stopping.
  2. Keep the decision to act in the program's own rules.
  3. Retain exact permissions even when Jev checks meaning.

The repository presents examples and cost or latency claims from its author. JevMade did not run them or make paid requests.

GitHub README · Source reviewed

Read the original guide Opens the author’s site in a new tab.