jevbooks

← All projects

jev-orderby-bench

yodablocks/jev-orderby-bench

Independent measurement of whether ORDER BY over Jev probabilities is defensible.

Scoring & Ranking0.53Runner-up: Evaluation & Benchmarking
Automated README summary

Automatically summarized from the README on 20 Sept 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A benchmark harness measuring whether SQL ORDER BY over Jev probabilities yields a defensible order, for developers building semantic sort on Jev. It reports pairwise inversion, Score ordinality, calibration, wording invariants and sort-key ties against pre-registered gates.

How it uses Jev

Jev supplies the probabilities that are sorted: jev_bool, jev_choice and jev_score are called on 360 labeled rows and on Amazon ESCI query-product pairs, and the returned values are measured for inversion, ordinality, calibration and ties rather than used to make a product decision.

Primitives:choicescorenoul

Technique worth stealing

Pre-register gate thresholds, then add a paraphrase control so a negation result cannot be overclaimed as negation-specific.

Try it

python3 harness/run_calibration.py with a key; --analyze-only recomputes from cache.

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.81
  • Shows a System One patternnot found in the excerpt0.26
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersFound in material0.94
  • Is a runnable toolnot found in the excerpt0.09
  • Top-10 learning shortlist signalnot found in the excerpt0.29
  • Is a replica of the modelnot found in the excerpt0.05
  • Solves a common problem (0–2)score on a 0–2 scale1.09 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.81Shows a System One pattern0.26Describes handling uncertainty0.04Reports measured numbers0.94Is a runnable tool0.09Top-10 learning shortlist signal0.29Is a replica of the model0.0500.51Solves a common problem (0–2)1.09 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.56Questionnaire0.40Flight recorder0.37Viewfinder0.26Check-up0.2000.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 20 Sept 2026.