JevMade field notes / Technical guide

Turn a code change into release checks and reviewer requirements

check-risk combines exact facts about a code change with focused Jev judgments. A project policy turns those signals into a risk level, required checks, and reviewer groups.

Original by moezubairGuardrails

Bookmark Keep this in your collection.

Leave a noteWhat would you try with this?

Only you can see your notes.

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Independent ElevenLabs affiliate. JevMade may earn a commission.

Credits and license

“check-risk” by moezubair. 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 Zubair

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

Different code changes deserve different review. check-risk starts with a project's written policy about sensitive files and consequences. Exact checks look for changed paths, new dependencies, large changes, and missing test edits before Jev is asked any questions about behaviour.

Jev examines limited before-and-after source excerpts. Ordinary code combines the named rules, applies minimum risk levels, and gathers required checks and reviewers. The report keeps the evidence and marks the assessment incomplete when the model is unavailable or has not been used.

The risk number represents policy weights, not the chance of an incident. Changed tests do not prove useful coverage, and default finance-related examples need replacing for another project. Source may leave the computer, while exclusions do not guarantee secrets are removed. Live Jev testing was still pending.

Key takeaways

Write project-specific rules for sensitive changes.
Report missing analysis rather than silently approving release.
Do not read a policy score as a probability of failure.

More guides →See the experiments →