JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Evaluation framework guide

jevals

A trace-evaluation framework that batches typed checks, calibrates thresholds per backend, defines gate failure behavior, and replays the same YAML against stored traces.

Original by OpenlayerGuardrailsGitHub repositorySource reviewed

Before you dive in

What you’ll find in the original

  1. Define each evaluation through a shared sample contract and batch independent checks against the same trace.
  2. Recalibrate whenever the backend changes because Jev, local models, and emulated LLM-judge probabilities are not interchangeable.
  3. Choose fail-open or fail-closed behavior explicitly; irreversible tools should not inherit a convenience-oriented default.
Worth knowing

The README's 6,015-request run and gateway latency are author measurements. Kev and Laya are supported interfaces, but the published benchmark rows had not been run against them.