Which published claims hold up?

Only matching data, metric, model version and protocol support a reproduction verdict. A failed portability test or a different private fixture is not a refutation. Updated 2026-10-05T00:49:25.539223+00:00. The ±2 percentage-point band is a practical replication tolerance, not a statistical equivalence test.

Live Jev comparison and business cases · Full audit data and source hashes

Model and claimAccuracyFindingScope of the evidence
decider-4bJevBench public easy100.00% published
100.00% measured
matches published roundingSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
decider-4bJevBench public original98.60% published
98.61% measured
matches published roundingSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
decider-4bJevBench public hard64.90% published
64.86% measured
matches published roundingSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
decider-2bJevBench public easy100.00% published
100.00% measured
matches published roundingSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
decider-2bJevBench public original88.90% published
88.89% measured
matches published roundingSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
decider-2bJevBench public hard57.70% published
56.76% measured
near reproduction within 2ppSame verified public cases and native scorer; bf16 Windows/RTX runtime, graphs disabled. The 2pp band is an engineering check, not a significance test.
Primary source
layaPublisher news.replication95.00% published
95.25% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher emotion.replication59.50% published
59.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher spam.replication99.25% published
99.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher phishing.replication98.00% published
97.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher jailbreaking70.75% published
71.25% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher toxicity53.00% published
53.00% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher intent78.33% published
78.00% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
layaPublisher scenario60.33% published
59.67% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher news.replication93.00% published
93.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher emotion.replication53.00% published
53.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher spam.replication99.25% published
99.75% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher phishing.replication99.25% published
99.25% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher jailbreaking75.50% published
80.50% measured
outside 2pp repeatability bandReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher toxicity52.50% published
53.50% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher intent65.67% published
65.33% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
laya-multilingualPublisher scenario56.00% published
56.00% measured
near reproduction within 2ppReconstructed publisher questions and sampling. Publisher did not pin dataset revisions; our source revisions are fixed. SDK and device differ. Task training exposure is explicitly reported.
Primary source
gliner-decideFast Decisions advertised 5100-example held-out average—not independently verifiable with public fixtureThe accessible fixture has 1700 development examples. Its results cannot verify or refute a claim on 5100 different held-out examples.
Primary source
gliner-decide-1bFast Decisions advertised 5100-example held-out average—not independently verifiable with public fixtureThe accessible fixture has 1700 development examples. Its results cannot verify or refute a claim on 5100 different held-out examples.
Primary source
gliner-decide-multiFast Decisions advertised 5100-example held-out average—not independently verifiable with public fixtureThe accessible fixture has 1700 development examples. Its results cannot verify or refute a claim on 5100 different held-out examples.
Primary source
kev-08bdocuments-v1 locked test / question accuracy85.10% published
85.04% measured
near reproduction within 2ppSame pinned public test and question metric; bf16 local serving instead of publisher fp32 claim evaluation. Devtools uses the publisher amendment: remove both rows sharing the duplicated CodeReviewer source ID (1071 questions). The common cross-model benchmark retains all 1073 questions. Hard-v1 holds out templates of trained skills; devtools labels are public proxies; documents use the same CFPB source and question templates as training.
Primary source
kev-08bhard-v1 locked test / question accuracy66.50% published
66.36% measured
near reproduction within 2ppSame pinned public test and question metric; bf16 local serving instead of publisher fp32 claim evaluation. Devtools uses the publisher amendment: remove both rows sharing the duplicated CodeReviewer source ID (1071 questions). The common cross-model benchmark retains all 1073 questions. Hard-v1 holds out templates of trained skills; devtools labels are public proxies; documents use the same CFPB source and question templates as training.
Primary source
kev-08bdevtools-v1 locked test / question accuracy63.70% published
63.77% measured
near reproduction within 2ppSame pinned public test and question metric; bf16 local serving instead of publisher fp32 claim evaluation. Devtools uses the publisher amendment: remove both rows sharing the duplicated CodeReviewer source ID (1071 questions). The common cross-model benchmark retains all 1073 questions. Hard-v1 holds out templates of trained skills; devtools labels are public proxies; documents use the same CFPB source and question templates as training.
Primary source
kev-4bhard-v1 locked test / question accuracy80.30% published
80.51% measured
near reproduction within 2ppSame pinned public test and question metric; bf16 local serving instead of publisher fp32 claim evaluation. Devtools uses the publisher amendment: remove both rows sharing the duplicated CodeReviewer source ID (1071 questions). The common cross-model benchmark retains all 1073 questions. Hard-v1 holds out templates of trained skills; devtools labels are public proxies; documents use the same CFPB source and question templates as training.
Primary source
kev-4bdevtools-v1 locked test / question accuracy75.60% published
75.54% measured
near reproduction within 2ppSame pinned public test and question metric; bf16 local serving instead of publisher fp32 claim evaluation. Devtools uses the publisher amendment: remove both rows sharing the duplicated CodeReviewer source ID (1071 questions). The common cross-model benchmark retains all 1073 questions. Hard-v1 holds out templates of trained skills; devtools labels are public proxies; documents use the same CFPB source and question templates as training.
Primary source
kev-4bPrevious round-8 documents-v1 locked test 90.4%—different checkpoint versionThe tested checkpoint is the later round-10 skills release. Its model card also documents older results. A round-10 score cannot verify or refute the older round-8 90.4% claim.
Primary source
vonJabr v2 macro accuracy 72.0% on 869 cases—fixture count mismatchOur pinned complete TOML contains 866 cases. Report it as a transfer result, not an exact replication. Von reports fitting its confidence map on the public JevBench cases and emotion in training.
Primary source
juliaNative typed-decisions 2000 heads73.15% published
72.55% measured
Near reproduction within the predeclared 2 percentage point band; not exact numerical equalityUnmodified publisher reproduce_typed.py; verified model and Parquet hashes; CPU fp32 native Torch backend, batch one, 1024-token context
Primary source
clm-int8CLM DeepSWE best-of-N 31/38 (81.6%)—exact downstream reproduction from published embeddingsEarlier local run used the authors' evaluator and public precomputed embeddings. This confirms the downstream evaluation, not full encoder/runtime equivalence. INT8 local classification is a separate test.

What the Jev marketing statements establish

The TypeSafe website advertises speed and cost multiples, calibrated confidence and zero hallucinations. This experiment measures accuracy, calibration and billable usage on fixed decision tasks. Its network timings and local GPU timings do not reproduce those speed or cost comparison protocols. Restricted output choices prevent invented labels; they do not prevent incorrect choices. “Zero hallucinations” must not be interpreted as zero decision errors.

Use the measured task-level errors and development-selected review thresholds in the live report. Confidence is evaluated on its own merits; a syntactically valid probability is not proof of calibration.