JevMade

Sign in
← Back to guides

JevMade field notes / Reproducible evaluation guide

How to guide planning software using plain English rules

This guide explains how to use everyday words to stop planning software from making forbidden moves. It shows how the software translates future steps into simple terms so a decision tool can judge them.

Original by AbdelStarkEvaluation

Listen to this guide

JevMade’s plain-English explanation

0:00 /

Our summary

This project tests a way to give plain English rules to planning software. Normally, these programs only understand mathematical goals, making it hard to forbid specific actions. This method lets users write simple limits without changing the underlying computer code.

The software guesses hundreds of possible future steps and translates them into basic words, like locations or speeds. Then, it uses Jev—an AI tool that chooses from options rather than writing an answer—to decide if any step breaks the written rules.

This guide is for developers testing software limits. In these tests, the software often failed because its guesses about the future stopped matching reality over time. Also, if the program lacks a specific word in its dictionary, it silently ignores rules using that word.

Key takeaways

  1. Test rules on situations where it is actually possible for the software to succeed.
  2. Check if the program dictionary includes the exact words you use in your written rules.
  3. Turn off confidence filters when testing to see if the decision tool matches a perfect checker.

All study results were reported by the author. The tests were not rerun for this review.

Repository README

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

Your note

Only you can see this. Clear the text and save to remove it.

Keep what you save

Sign in to keep bookmarks and private notes on every device. We email you a link; there is no password, and the same link creates your account.