JevMade field notes / Technical guide

Test a Jev decision before publishing a fixed version

Jev Workbench is a local interface for writing decision questions, trying examples, and publishing fixed versions. Applications can keep using an approved version while later drafts change.

Original by molis-aiAgent workflows

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“Jev Workbench” by molis-ai. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Molis AI

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

Changing the words in an AI question can change an application's behaviour. Jev Workbench separates editable questions from fixed releases. A person can write a decision function, try examples, and publish a version that client applications are specifically allowed to call.

The guide separates the service key, temporary administrator access, and removable client access tied to particular versions. Routine run records keep operating details rather than ordinary inputs and answers. Test cases saved deliberately do retain their input, while exports leave out service and client secrets.

A simulated preview does not prove that real service access or publishing works. Saved examples may contain private material, and local protection still depends on the machine's security. Test each released version and maintain an approval and recovery process outside the model itself.

Key takeaways

Keep applications on a fixed approved version.
Separate service, administrator, and client access.
Do not mistake a simulated answer for a working release.

More guides →See the experiments →