Open reproduction · measured 2026-09-21 · NVIDIA L40S

assay — our own Jev,
measured against the real one.

A System One decision model: unstructured state + typed questions in → typed answers and calibrated probabilities out, in one forward pass, with no text generation. Trained in 7.5 minutes on a single L40S, then run head-to-head against TypeSafe Jev 1.13 and laya on identical human-labelled rows.

97.7%of real Jev, in-distribution
95.2%of real Jev, out-of-domain
2 / 4families where we beat Jev
7.5 mintotal training, one L40S

01Head-to-head, identical rows

Metric is per-family balanced accuracy (mean per-class recall, so majority-class guessing scores at chance), macro-averaged across families — families are never pooled. The evaluator iterates gold labels: a missing or errored prediction counts as a failure. n = 100 rows per family.

assay-4B (ours) real Jev 1.13 laya (encoder, 421M) untrained pointer-head
0.00.25 0.500.751.0 In-distribution 0.811 Jev 0.792 assay 0.741 laya 0.324 untrained Out-of-domain 0.865 Jev 0.823 assay 0.683 laya 0.542 untrained

In-distribution — trained task families, held-out splits

FamilyTypeuntrainedlayaassay-4Breal Jev
ag_newschoice-40.2450.9560.9270.873
boolqnoul0.5020.7910.8430.979
mnlichoice-30.3480.8730.8600.834
sst5score-50.2000.3460.5390.558
Macro0.3240.7410.7920.811

Out-of-domain — task families never seen in training

FamilyTypeuntrainedlayaassay-4Breal Jev
emotionchoice-60.1670.5480.6300.655
imdbnoul0.9601.0000.8600.940
yelpnoul0.5000.5000.9811.000
Macro0.5420.6830.8230.865
Three findings. (1) The reproduction works — training lifted the architecture from 0.324 (random head) to 0.792, and past the separate zero-training LM-head bar of 0.503 / 0.717. (2) It does not collapse out of domain: 0.823 on unseen tasks, the same ~4 pp gap to Jev as in-distribution — the failure mode other reproductions warn about did not occur. (3) Ordinal is unsolved by everyone, including Jev: sst5 tops out at 0.558 (Jev), 0.539 (assay), 0.346 (laya). That is the open research gap, not an implementation bug.

02The near-Jev landscape

Every open reproduction of TypeSafe's Jev, and the axes that actually separate them. The load-bearing difference is the readout: only a pointer head over per-option hidden states is faithfully listwise — where adding an irrelevant option can legitimately shift the odds ratio between two existing ones, the behaviour Jev's IIA experiment demonstrated.

ProjectBackboneReadoutTrainingListwise-faithfulMultiling.
Jev (TypeSafe)frontier, likely sparse MoEslot / pointer, prefill-onlyRLCD (proper scoring)— referenceEN
kev (jaredpalmer)Qwen3 0.5–8B densepointer + block-causalLoRA, frozen suites, autoresearchyesno
assay (ours)Qwen3-4B → 3.8pointer + block-causalLoRA r16, lr 5e-5yesno
Nimble (Bespoke)Qwen3.5-9B denseLM-head candidate logitsLoRA + contrastive curationpartialno
SemIf (TheoLeeCJ)Qwen3.5-4B frozenLM-head letter logitsnone (zero-shot)partialno
laya (NandhaKishorM)ModernBERT 421M / mmBERTencoder + routerRLCD (proper scoring)↔ encoder branch100+

Which is the best open implementation?

No single winner — it depends on the axis, and saying so is more useful than crowning one.

most faithful + rigorous

kev

The only project that reproduces Jev's listwise architecture and wraps it in real research discipline — frozen checksummed suites, a locked test read once, a provenance ring, autoresearch, a whole size family. The reference open Jev.

most practical

laya

Fastest (~26 ms/row), tiniest (421M), pip install laya, 100+ languages with a per-request router. Best choice for shipping multilingual routing today — at the cost of ordinal quality (sst5 0.346) and some OOD instability (yelp 0.500).

best data engine

Nimble

Plan → pair → necessity-gate → label-by-code contrastive curation: the LLM never produces a final label, Python computes it from audited rules over verified facts. The single most worth-copying component in the field.

03How assay is built

Fuse the best of each, then add what nobody has built.

Honest caveats. n = 100 rows per family, so confidence intervals are wide — this is a first result, not a publication number. Training and evaluation use disjoint splits of the same sources (in-distribution transfer); the out-of-domain suite shares task families with training, so it is "easy OOD" — hard OOD (date arithmetic, multi-hop policy composition, paraphrase) is the next probe and is where the Jev gap is expected to widen. Single seed, no hyperparameter search, no temperature calibration yet. assay runs bf16; Jev numbers come from its live API.