cribl-decision-1.0-27B (Cribl)v1.7 · 10 s rule
Data: JevBench v1.8.3, published 2026-10-31 · method v1.7 (10 s rule), measured under the rule
Capability 76.5 · Not ranked in the current release
Measured on the 27 Oct 2026 draw, which is not yet equated to the reference scale; stronger anchor runs for that draw are being measured. Shown unranked until then.
Last measured: 2026-10-31 · measurement release: v1.8.3
Apache-2.0 declared on adapter card; no standalone adapter LICENSE; base Apache-2.0 LICENSE and notices retained
intelligence
61.5
calibration
91.5
speed
86.5
cost
64.0
Composite (secondary)
73.6 · Not ranked on this board
Cost and measurement conditions
$0.016 per 1,000 decisions (estimated)
GPU-time estimate from v1.8.0: one monthly-rented RTX PRO 6000 96 GB, EUR 999/month / 730 hours, ECB USD 1.1133/EUR dated 28 Oct 2026, USD 1.5235/hour; average load 70%. Architecture: dense qwen, 27B active parameters; throughput 11763 tokens/s (architecture-class calibration, 29 Oct 2026, efficient-engine prefill; capped at 100,000 tokens/s). The row's own scored cost basis: 457,748 input + 0 output tokens over 1,489 decisions. Generated tokens are counted at the same throughput as prefill. GPU-time cost USD 0.0157999451196661/1,000; old list-price estimate USD 0.0599468502350571/1,000 (qwen/qwen3.5-27b at USD 0.195/M input and USD 0/M output). Applied min(old list-price estimate, GPU-time cost) = USD 0.0157999451196661/1,000. Estimated, not a bill. USD 0.0157999451 per 1,000 decisions on the frozen 1,489-item common set of this draw (USD 0.0292562886 over all 1,500 items).
p50 latency: 0.4 s
Self-hosted latency estimate under the shared method (assumption, not measured)
Measured 31 Oct 2026 on an evaluator-owned Verda VM in FIN-03 (Finland, EU), one NVIDIA RTX PRO 6000 Blackwell Server Edition, nominal 96 GB, image 24.04.cuda13.0. FIRST-PARTY IMPLEMENTATION OF THE AUTHOR'S DOCUMENTED READOUT, with declared extensions: cribl-ai/cribl-decision-1.0-27B adapter at 8fbb5af4e717ae499bc0edebc851f9bd99b9bf04, attached to Qwen/Qwen3.5-27B at fc05daec18b0a78c049392ed2e771dde82bdf654. This is a PEFT adapter plus base model, not a standalone full fine-tuned checkpoint. The author supplies a single-question demo with ten implemented labels and describes a larger label table. The shim preserves its Context/Question/Options/Answer prompt, native state serialization, original option order, last-token hidden state, candidate lm_head projection, float logits and candidate-restricted softmax. No chat template, prompt sanitization, truncation or generated text. It loads explicit Qwen3_5ForConditionalGeneration plus PEFT, then get_base_model().model.language_model and lm_head, with BF16 CUDA base and ordinary PEFT adapter dtype behavior. Stock efficient SDPA is selected by the locked runtime; no attention override, quantization, CPU fallback, host retry or answer repair. Under the 31 Oct preregistration amendment, this 27B row ran the cache-free single-prefill path: use_cache=False for each independent complete prefill and empty_cache() before each score call after prior tensors leave scope; no past state is reused. Multiple questions use separate serial passes; no invented multi-slot packing. DECLARED EXTENSIONS: noul maps proposition/negation in true/false order, with instructions and literal Not (instructions) as absent-description fallback; score preserves ordered levels and returns the complete distribution keyed by zero-based index strings. The card's 255-label single-token constraint is interpreted by A-Z followed by the first 229 lexically ordered uppercase pairs that tokenize singly, ending at JT; split-token pairs are skipped. This is a disclosed interpretation, not proof of an unavailable complete author training table. Public pod parity verified exact token IDs and bit-identical probabilities between the original cached author readout and the cache-free shim on all nine short public type/width cases. Long public probes verify rendering, token IDs, wire shapes and usage; no long-length cached probability comparison is claimed. 8,192 is training length, not a refusal cap; the demo forwards every unpadded token without a native total-length check. Architectural 262,144 positions do not establish empirical capacity. No context cap is added; genuine unsupported type/candidate contracts may return HTTP 422, while framework/OOM faults remain HTTP 500. First-party HTTP input usage sums every actually forwarded prompt, including repeated state across question passes; output_tokens is 0. The author supplies no HTTP server or usage billing contract. The frozen TypeSafe adapter and driver retain the 120 s transport timeout. Locked runtime: torch 2.11.0, CUDA 13.0, transformers 5.19.0, tokenizers 0.23.3, PEFT 0.21.2, safetensors 0.8.0; source/runtime/tokenizer hashes retained. Source review found no benchmark-item lookup in the selected author readout; upstream framework internals were not exhaustively audited. Numerical and author-code execution occurred only on the disposable rented pod, with verified local base/adapter, read-only mounts, empty credentials, offline flags and network cut. Actual-model public smoke passed with native/offline usage equality on its public fixtures, separate warm-ups and fresh timed bodies from 256 through 80,554 rendered tokens. All documented types and widths through 255, Unicode JSON, special-token and multi-question fixtures passed. Public peak reserved memory left at least 2 GiB headroom on this device. No native length-refusal probe is claimed. Public equality does not erase the 56 scored usage mismatches. Separate public pre-warm passed. The complete 1,500-request run took 338.3301031589508 s; raw output sha256 2c81b3c0962e372fa8fc52da637e566a84c49959e7ea9fd557ebcdb08202eb6d was verified. Post-run health was ready. The VM was closed and temporary node and local copies deleted, with no cleanup errors reported. GPU rental spend is separate from the benchmark model-cost estimate.
Measured latency over 1,500 decisions: p50 0.111 s · p95 0.228 s
5 decisions over 10 s (5 of them answered without error, counted as wrong).
A decision that takes longer than 10 seconds (measured time) counts as a wrong answer and as zero calibration for that item: each type's calibration is multiplied by the share of its decisions answered within 10 s. The limit uses the measured time (raw). The displayed adjusted time for self-hosted rows (2 × + 0.15 s) is an assumption and is not used for the limit.