Four more evaluated systems join the regular draw

Refusals, errors and context-bound failures stay in the full 1,500 denominator. Every row kept its own package, model, runtime and context settings; nothing was re-run for presentation.

NOT DIRECTLY COMPARABLE WITH THE LIVE v1.6.1 BOARD OR WITH THE EARLIER FRESH DRAWS. This release is a different draw with its own small-field median: G_med = 9.839526770355711, frozen from the four v1.6.10 members (attest-31B-v1.0 does not move it), against 2.573387642438244 on the live field. G_med_flag_gt10 is false. The gap penalty is max(0, 1 - max(0, (gap - G_med) - 8)/100), so this field's threshold is G_med + 8 = 17.84. On the merged live board this draw is placed with offset 0 while its anchor runs are pending, exactly like the earlier fresh draws. Measured, not estimated: Applying the same penalty formula to the stored base and gap at the live field's median 2.573387642438244, attest-31B-v1.0 Intelligence 65.238 would be 65.238 (gap -0.628); the original four rows are as stated in the v1.6.10 notes: standard_one_3b_sh Intelligence 32.786 would be 31.294 and metask_jev_rain_12b_trained 67.826 would be 67.587; krino-2b and metask_jev_rain_31b_trained are unchanged.

Cost: no item is excluded from the cost basis on this draw. Every row is priced from its own measured usage block at a clearly-labelled ESTIMATE rate fixed before scoring (r99, r101, r103 and r106 pre-registrations); none is a bill any of these systems issued. Every row is under the published v1.6 cost ceiling of USD 0.0646 per 1,000 decisions. The cost normalizer C0 is USD 0.001 per 1,000 decisions with 30 cost points per decade.

No subject-topic radar in this release: this draw's items have not been topic-labelled yet, and the shared topic labels of earlier draws do not cover its items. Families, use cases and languages are authoring metadata and are shown.

v1.6.13 ADDS ONE ROW, attest-31B-v1.0, to the six of v1.6.12 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so all six earlier rows keep identical point scores, axes and capability; ranks and bootstrap confidence intervals are recomputed for the seven-row roster, and the existing raw_on_A and API-basis offset diagnostics are unchanged because the new row is full-set API, not a new self-hosted equating-pool member. No API offset enters its score.

krino-2b: All 1,500 items answered HTTP 200 with native probabilities. The 15 longest items of the draw (the same 15 that standard_one_3b_sh refuses) ran with the state truncated to 65,536 tokens, as the author's submitted serve command documents (KEV_TRUNCATE_STATES=1); every other item is at most 1,802 input tokens. Reference kernels were used (KEV_FUSED=0) because the documented pip install has no flash-linear-attention. Kev reports usage.output_tokens as the token count of the serialized answer JSON although nothing is generated (165,276 over 1,500 decisions); it is priced as reported at the frozen DeepInfra Qwen/Qwen3.5-2B reference, USD 0.02/0.10 per 1M. Measured on an evaluator-owned Lium H100 pod in an offline container (network none).

metask_jev_rain_12b_trained: All 1,500 items answered HTTP 200. The author's service runs the authors' own int4 (W4A16) quantization of Google's Gemma 4 12B QAT checkpoint with their own rank-16 LoRA applied unmerged by vLLM; per its model card it takes a second pass on part of the items, so it reports generated output tokens (84,238 over 1,500 decisions) and its latency has a long tail (raw p95 8.1 s against a raw p50 of 0.13 s). Measured on an evaluator-owned Lium H100 80GB pod (IP geolocated to Nizhny Novgorod, Russia) in an offline container (network none). google/gemma-4-12b-it is not listed on OpenRouter, so the cost uses the nearest listed sibling, google/gemma-3-12b-it at USD 0.05/0.15 per 1M, times its own usage. It is a different system from the earlier metask_jev_rain_12b row.

metask_jev_rain_31b_trained: All 1,500 items answered HTTP 200. The author's service runs Google's unchanged W4A16 Gemma 4 31B QAT checkpoint with the authors' own rank-16 LoRA applied unmerged by vLLM, at max_model_len 6,656 (per the measuring operator's handoff): longer inputs are shortened by the service's own documented extraction rule rather than refused, so the longest items were answered on a shortened state. The authors tested it on H200; it was measured on an evaluator-owned Lium H100 80GB pod (IP geolocated to Nizhny Novgorod, Russia) in an offline container (network none) with unchanged settings. The service reports 1 output token per decision; cost is the OpenRouter google/gemma-4-31b-it list price (USD 0.09/0.34 per 1M) times its own usage.

standard_one_3b_sh: 15 of 1,500 items returned HTTP 422: they are the 15 longest items of the draw and exceed the model's documented 32,768-token context, so the author's server refuses them rather than truncating; scored wrong per method. Measured on an evaluator-owned Lium H100 pod in an offline container (network none). Priced at the M2 base-model floor, OpenRouter mistralai/ministral-3b-2512 at USD 0.10/0.10 per 1M, because the author's own list price (USD 0.038 per 1M input) is below that floor; the schema head generates no text, so output tokens are 0.

torchcast-decision-4b-v1.1: evaluator-owned Lium GPU pod (H100), offline read-only container (--network none); author's torchcast_decision server unchanged at tag v1.1.0 with the bundled decision_config.json (bf16, one forward pass reading option letters, calibration temperature 0.9, yes/no commit floor 0.801) on the documented stack torch 2.9.1+cu128 / transformers 5.8.1 / flash-linear-attention 0.5.2 / causal-conv1d 1.7.0 (fast kernels active, CUDA graphs on) Paid fast-lane order 529be5d5 (public). Qwen3.5-4B fine-tune served by the author's own torchcast_decision package. Runtime: official pytorch/pytorch:2.9.1-cuda12.8-cudnn9-devel image (digest-pinned) plus an offline hash-locked overlay of the documented packages (Python 3.11 instead of the documented 3.12). decision_config.json sets a disclosed yes/no commit floor of 0.801: a yes/no probability with max(P, 1-P) below 0.801 is moved to 0.801 on its own side (answer unchanged; same mechanism as h2o-lightning-4b). Prompts over 16,384 tokens keep the head and the tail of the state (documented). Output tokens are 0 (no generation). CC BY-NC 4.0 (weights); base Qwen/Qwen3.5-4B Apache-2.0; serving package Apache-2.0. ESTIMATE, v1.5-M2 base-model reference rule: self-hosted open weights, no bookable tariff. Base model Qwen/Qwen3.5-4B (model card base_model). OpenRouter does not list Qwen3.5-4B (host snapshot source/public-docs/OPENROUTER-MODELS.json, fetched 2026-10-12T08:15:26Z, read 2026-10-12). Binding precedent INTERPRETATION-1 I-2/I-3: DeepInfra Qwen/Qwen3.5-4B, USD 0.03/M input, USD 0.15/M output, frozen 25 Sep 2026 price cut-off snapshot (listing later deprecated; frozen reference kept). Logit readout, no generation: server reports 0 output tokens. Isolation is container-level (--network none); no separate host-level netcut probe was taken. The input tar was on the rented pod host disk during the run, and the pod was destroyed after measurement (CUSTODY-RECEIPT.json).

uniphore-4b-decider: 15 of 1,500 inputs exceed the author's documented 16,384-token wrapper limit; the author's code refuses them (HTTP 422, no truncation) and they are scored as wrong per method, so 1,485 items were answered. The native readout is one forward pass, so output tokens are 0 and the cost is the input tokens at the frozen DeepInfra Qwen/Qwen3.5-4B reference, USD 0.03/0.15 per 1M (that listing is flagged deprecated in the frozen snapshot but remains the reference). Measured on an evaluator-owned Lium H100 pod in an offline container (network none), in the vllm/vllm-openai v0.31.0 image with transformers 5.17 and reference PyTorch kernels in place of the documented flash-linear-attention / causal-conv1d kernels, so its latency was measured on the fallback path. The author discloses that the public JevBench set was inspected repeatedly during development.

attest-31b-v1.0: Paid public fast-lane order 07d13315. Vendor-hosted attest.engineering /v1/systemone API; latency measured from Sandy (Germany), using the official per-item latency subset without API adjustment. Full S1200+P300 draw, not API A300 supplement; no API equating. 15 of 1,500 requests returned HTTP 500 after 8 retry invocations and are scored as wrong in the full denominator. Public model documentation declares frozen google/gemma-4-31B-it @842da3794eaa0b77d5f08bae87a17459d91ff475, unmodified bf16, no adapter or quantization; single forward pass reading option-label logits, no generated tokens, one fitted temperature (value not documented). Hosting implementation and deployed weights were not independently inspected. Hosted API access is not an open-weights release by the vendor; base weights are under the Gemma 4 licence. ESTIMATE, v1.5-M2 base-model reference rule: vendor-hosted API, customer list price USD 0.048/M input and USD 0.00/M output effective 2026-10-11 has been in force fewer than 30 days. Base model google/gemma-4-31b-it reference on OpenRouter USD 0.09/M input / USD 0.34/M output, snapshot fetched 2026-10-12T17:55:05Z (SHA-256 81eae2f3f94bf299c8d4499260f842c357b7a869ce82dfa1741ad6a89cf57014), same base-model estimate precedent as metask_jev_rain_31b_trained. Applied to measured response usage; failed HTTP 500 usage/billing may be unreported. No output generation; reported output tokens 0. Estimated, not a vendor bill.

Microsoft A2 re-run: 300 sealed supplementary A2 + 300 public items, not the full S1200 set. Unranked measurement; the official Microsoft row is retained on the merged boards. Equating pool four of six: Krino, Standard One, Uniphore, MeTask 12B. MeTask 31B and Torchcast were not completed after four unsuccessful allocation attempts (price/creation/controller failures); no inferred scores for missing pool systems. Seven HTTP 422 responses are wrong in the 600-item denominator. Pool re-runs used H200 in Helsinki, versus H100 parents; wide equating confidence intervals are reported. Latency from Sandy (Germany). Cost is the Azure Foundry tariff USD 0.042/M input, USD 0/M output; invoice/warmup/refusal charges unknown. No category cells or ranks are assigned to the A2 measurement.

v1.6.15 ADDS THREE SELF-HOSTED CPU ROWS to the seven official rows of v1.6.14 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so all seven earlier rows keep identical point scores, axes, capability and cost objects. Ranks and bootstrap confidence intervals are recomputed over the new roster - the scorer draws ONE paired resample for the whole field, so adding rows moves a carried row's confidence interval while no point estimate changes; six of the eight carried rows' intervals moved (attest-31b-v1.0 and the carried A2 measurement did not). One DIAGNOSTIC also moved, and it is named here rather than left to be found: the API-basis median diagnostic is computed over the ranked field, so it moved from 9.628699345543296 to 9.158662835848954 when three rows joined, and that moves the stored A-basis diagnostic (the row field v16.raw_on_A) of exactly one carried row, standard_one_3b_sh: intelligence 29.3339 -> 29.1921, capability 53.1539 -> 53.0830. That diagnostic is not part of any score, rank or axis on this release, and no carried row's composite, axis, capability or cost object changes. The unranked A2 measurement of v1.6.14 is carried through byte for byte and is not rescored. reflex-instinct-0.6b is LISTED BUT NOT RANKED: CoS deputy decision #18761 accepts its Intelligence, Calibration and Cost only and declares its Speed figure non-official, and the composite weights Speed. All three new rows were measured at USD 0 on the evaluator's own shared CPU host, so their Speed figures are loaded-host lower bounds; each row logs its own one-minute load trace and carries it in its note.

Where to look for the row that is shown but not ranked, and what it does NOT mean. reflex-instinct-0.6b is deliberately absent from the ranking charts, the Composite and Capability boards, the compare view and the category radars, because those are ranked views and this row has no rank. It is named in this release's own notes and header, and it appears in the collapsed "All data" table further up the page, after the Noul table. DISCLOSED: in that table the row still shows its composite as the scorer computed it, and a Jev-class verdict the site derives from its cost per decision and its MEDIAN LATENCY against the frozen Jev-class caps. The composite weights the Speed axis, and that latency is the very measurement CoS deputy decision #18761 declares non-official for this row, so neither figure is an official placement. They are not an official placement and must not be quoted as one. Its accepted figures are Intelligence 3.960, Calibration 73.153, Capability 38.556 and Cost USD 0.00630127 per 1,000 decisions. A dedicated row group for listed-not-ranked rows, with Speed greyed out and the composite hidden, is the right presentation and is a site change this release does not make.

Cost on the three new rows: each is priced from its own measured usage block at a clearly labelled ESTIMATE rate fixed before scoring, on the full 1,500-row basis, and each is far under the published v1.6 ceiling of USD 0.0646 per 1,000 decisions - phocinae-largha-150m-v1 USD 0.00143980, reflex-instinct-0.6b USD 0.00630127, julia-1 USD 0.00217445. None is a bill any of these systems issued. julia-1's declared base jhu-clsp/mmBERT-small has no market listing; adding it to the frozen pricing module's reviewed unlisted-base set was authorised by #18761, re-frozen, hashed, proved behaviour-identical over every registry entry on the evaluator's machine and independently reviewed before this row was scored.

julia-1: 1,500 attempted, 1,483 answered. The 17 misses are the author's own strict_encoding policy refusing rather than truncating (15 items above their lossless context budget, 2 with an option above their 48-token option contract); the totals AND the per-type split were pre-registered before the run and came back exact. All answered items native; the Speed figures are the published method's percentiles over this draw's open standard and judge items. 652,334 input tokens and 0 output tokens by construction (one encoder forward pass read at marker positions, nothing generated). The author ships no server, so the HTTP surface is the evaluator's - but their own julia.typed.predict_typed already speaks JevBench's typed-question shape, so no mapping decision of the evaluator's enters this row. Their hierarchical Router, which their own card says is not a global probability distribution, is neither used nor reachable here: every choice item of this draw has 3 to 9 options, inside their native 2-20 contract, so each decision is one call with one global softmax, and the probabilities are their raw values rather than their presentation helper's. Measured on the evaluator's own shared CPU host at their own settings read back from the run itself (float32, 4 threads, torch backend); one-minute load 10.87-13.78 logged, so Speed is a loaded-shared-CPU lower bound with the standard self-hosted x2 + 0.15 s adjustment on top. Cost is a clearly labelled size-class ESTIMATE: the declared base jhu-clsp/mmBERT-small has no market listing, and the base-size-encoder line of USD 0.005 per 1M input / 0 output that modernbert-jev-v2, tacet-sonata and watt-flash-0.1 carry in the PUBLISHED v1.6 field is used unchanged - no row of this draw carries it - and it is not a bill.

phocinae-largha-150m-v1: 1,500 attempted, 1,125 answered. The 375 score items are recorded as HTTP 422 misses by the EVALUATOR'S shim, under a rule pre-committed in writing before the run (PREREG-R92 section 4.6), because the author's API answers only a fixed nine-level 2..10 scale that does not fit this item type; the shim refuses them in about 0.7 ms without calling the author's server at all, so no claim is made that the author's code refused anything. They stay in the full 1,500 denominator as misses - the figure 1,125 was pre-registered and came back exact. All answered items native. The Speed figures on this row are the published method's percentiles over this draw's open standard and judge items, not a median over every attempt - and DISCLOSED: 37 of those 124 items are the shim's instant score refusals, which cost no model time, so the figures are faster than the model itself is. Over the 87 items the model actually answered the Speed axis would read 75.75 instead of 77.12, which changes no rank. Measured on the evaluator's own shared CPU host (AMD Zen 2, float32), NOT a dedicated machine: other jobs ran beside it and the one-minute load average was logged for the whole window (3.75 to 9.89, mean 5.81, 12 samples - the quietest of this release's three new rows). Speed is therefore a loaded-shared-CPU figure and a lower bound for this model on a dedicated core or a GPU; the standard self-hosted x2 + 0.15 s adjustment is applied on top and the raw percentiles are kept. DISCLOSED: the author's server places every short-option request in its own 512-token budget tier, so the state is truncated far below the 8,192 its MAX_POS advertises - the author's design, not the evaluator's, and visible in their own usage histogram. A SECOND mapping decision of the evaluator's, footnoted on the row: the item's instruction text (and for noul its true/false criteria) is appended to the state, because state is the only text field the author's API has. Cost is a clearly labelled size-class ESTIMATE on the base-size-encoder line the PUBLISHED v1.6 field carries - modernbert-jev-v2 (measured in v1.6.8 on the earlier a2 draw) and the v1.6.1 rows tacet-sonata and watt-flash-0.1 - and no row of this draw carries it. It is not a bill.

reflex-instinct-0.6b: 1,500 attempted, 1,500 answered, zero failures of any class - the pre-registered figure, exact. All answered items native; the Speed figures are the published method's percentiles over this draw's open standard and judge items. NOT RANKED, and here is exactly why: CoS deputy decision #18761 accepts this row's Intelligence, Calibration and Cost only and declares its Speed figure (58.972) NON-OFFICIAL, because the one-minute load on the shared host ranged 9.42-33.12 (mean 15.28, 155 samples) during the window and the evaluator's own preparation activity overlapped it. The published composite weights Speed, so this row is shown with its axes and its Capability 38.556 - which is Intelligence and Calibration only and contains no Speed - but it carries no rank and no composite placement. Its Capability 38.556 is the highest of this release's three new rows, above phocinae-largha-150m-v1's 30.240 - said here because the Capability board does not show it: that board contains no Speed at all, so a reader could reasonably ask why this row is absent from it. The answer is that THIS RELEASE applies #18761 to the whole row rather than axis by axis - the deputy's decision excludes the Speed figure, and whether a row with a non-official Speed may still be ranked on Capability alone is the open question #18825, which has no answer yet. The conservative reading ships. DISCLOSED: the author's own encode() truncates state lines above its own max_len of 16,384 instead of refusing them, so this row answers the 15 items of 106,804-122,936 characters that four other rows of this draw recorded as context refusals (attest-31b-v1.0, julia-1, standard_one_3b_sh and uniphore-4b-decider); that is the author's design choice, not the evaluator's, and those items are the slowest in the row. Cost is a clearly labelled size-class ESTIMATE on the sub-1B line the PUBLISHED v1.6 field carries (liquid-d1-omni-600m, jiwo-0.8b, vegaml-0.8b) - no row of this draw carries it - and it is not a bill.

v1.6.16 ADDS ONE SELF-HOSTED GPU ROW, vllm-sr-d3 (vLLM-SR d3), to the ten full-draw rows of v1.6.15 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so every carried row keeps identical point scores, axes, capability, cost and speed objects. What moved on carried rows, counted exactly. RANKS: vllm-sr-d3 has the highest Capability of this draw, so all nine ranked carried rows move down one place in this release's Capability order (attest-31b-v1.0 3 -> 4, julia-1 9 -> 10, krino-2b 7 -> 8, metask_jev_rain_12b_trained 2 -> 3, metask_jev_rain_31b_trained 1 -> 2, phocinae-largha-150m-v1 8 -> 9, standard_one_3b_sh 6 -> 7, torchcast-decision-4b-v1.1 4 -> 5, uniphore-4b-decider 5 -> 6); its composite (A 5.570) sits between krino-2b and phocinae-largha-150m-v1, so phocinae-largha-150m-v1 (8 -> 9) and julia-1 (9 -> 10) also move down one place on composites A, B and C and in their headline rank; no other composite rank moves. CONFIDENCE INTERVALS: none of the ten carried rows' bootstrap confidence intervals moved. The scorer seeds each row's bootstrap with the shared seed 16 plus the row's position in the key-sorted roster, and vllm-sr-d3 sorts last, so no carried row's position changed (in v1.6.15 the three new keys sorted into the middle of the roster, which is why six carried intervals moved then). Correction to the v1.6.15 note above: it says the scorer draws ONE paired resample for the whole field; it does not - the scorer seeds each row's resample by its position (seed 16 + index in the key-sorted roster), each row with its own resample, which is why rows that changed position moved in v1.6.15 and none moved here. The same mechanism is why d3's interval here differs from its private single-row preview while its point values are identical: Capability 95% interval [78.928, 84.441] here, [79.337, 84.362] in the preview. DIAGNOSTICS: the API-basis median diagnostic is computed over the ranked field, so it moved from 9.158662835848954 to 9.40342052601045, which moves the stored A-basis diagnostic (the row field v16.raw_on_A) of exactly one carried row, standard_one_3b_sh: intelligence 29.1921 -> 29.2660, capability 53.0830 -> 53.1199; and the release-level equating-offset diagnostic moved from I 0.1329 / C 1.0866 to I 0.2288 / C 1.2340. Neither is part of any score, rank or axis on this release: the only API row scored in this invocation, attest-31b-v1.0, is a full-set row and is not equated, and the carried A2 measurement keeps its own A2 equating and is not rescored. reflex-instinct-0.6b stays LISTED BUT NOT RANKED under #18761 and the unranked A2 measurement of v1.6.14 is carried; neither is changed.

Cost on vllm-sr-d3, and the scope of the cost note above: that note's "every row is under the published v1.6 cost ceiling of USD 0.0646 per 1,000 decisions" is true of the ten rows of v1.6.15 and is NOT true of vllm-sr-d3. d3 is priced as an ESTIMATE at the frozen Qwen/Qwen3.8-27B list reference of the published v1.6 field (USD 0.42 per 1M input and USD 3.00 per 1M output, the same pair the published Perplexity Decider v1.1 27B and Torchcast-Decision-27B rows carry) times its own measured tokens on the full 1,500-row basis: 1,951,205 input tokens and 0 output tokens, USD 0.5463374 per 1,000 decisions, about 8.46x that ceiling. It is not a bill and not a quote from the author or any host. Consequences: its Cost axis is 17.876, below 50, so the squared cost gate of the composite applies and its composite A is only 5.570 (rank 8 of 10 here) despite the highest Capability of this draw; and on the merged live board it is far above the official Jev-class cost cap, so it is NOT on the default (cost-capped) Capability ranking.

Board effect, and why this release needed an explicit GO. On the merged live board, with the default caps, the top five of composites A, B and C and of the cost-capped Capability ranking are unchanged on the mixed board, on the open-weights board and on the API board (vllm-sr-d3 is outside the cost cap and its composite is far down). The views that change are Capability views with the cost cap switched off: with the latency cap at 2x and open-weights and API models mixed, vllm-sr-d3 becomes #1 on Capability, 82.966 against Perplexity Decider v1.1 27B at 82.792; on the open-weights board it is #1 with the cost cap off whether the latency cap is 2x or off; on the mixed board with both caps off it is #6 and that top five is unchanged. The #1 is not a resolved order: d3's 95% interval here is [78.93, 84.44] and Perplexity Decider's is [79.18, 84.71], they were measured on different draws (this draw sits on the merged board with offset 0 while its anchor runs are pending), and d3's Speed was timed on different hardware (see its note). A change to a public top five needs Florian's GO; he gave it on 13 Oct 2026 at 15:12Z (card 17392).

vllm-sr-d3: Model vllm-sr/d3 at revision 5ce995dfb7ff07da00fec4211eb7f0560f52eaf8 (vLLM Semantic Router team), a fine-tune of the base Qwen/Qwen3.8-27B; its model card states 26.09B parameters including a 0.46B vision encoder. Weights Apache-2.0. The training data is not disclosed by the author, so the weight licence alone says nothing about the provenance of the training data. 1,500 attempted, 1,500 answered (all HTTP 200), 0 errors, 0 missing; the author's server sets no input-length cap, so it also answered the draw's 15 longest items that several rows of this draw refuse. Determinism check: 50 items re-asked, 50/50 bit-identical probabilities, 0 argmax flips. HARDWARE DIFFERS FROM THIS DRAW'S OTHER GPU ROWS AND FROM PERPLEXITY DECIDER AND TORCHCAST-27B: measured offline on one rented NVIDIA RTX PRO 6000 Blackwell Server Edition 96 GB GPU (Verda), while this draw's other GPU rows, Perplexity Decider and Torchcast-Decision-27B were timed on a single H100 80 GB, because no single H100 was available; the Speed axis (87.369; p50 0.1087 s raw, 0.3675 s adjusted, over the scorer's 124 open standard and judge items) therefore rests on different hardware, and the larger 96 GB memory may also matter for the longest inputs. The plain CUDA/PyTorch path of the author's unmodified d3_server.py was measured; the author's AMD ROCm fast path does not apply on CUDA. The own-server adjustment x2 + 0.15 s is an assumption, not a measurement. Cost is an ESTIMATE, not a bill: the frozen Qwen3.8-27B list reference (the same basis as Perplexity Decider and Torchcast-Decision-27B) times d3's own measured tokens, USD 0.5463374 per 1,000 decisions, far above the official Jev-class cost cap, so d3 is NOT on the default (capped) Capability ranking and its composite is small because of the squared cost gate. Source review of the pinned code before the run: PASS (no network on the text path, no benchmark-specific branches, no secret reads).

v1.6.17 ADDS 7 ROWS (Amos 1 large (Scira) (amos-1-large), Amos 1 medium (Scira) (amos-1-medium), metask-jev-rain-31B-trained service v3 (metask_jev_rain_31b_trained_v3), pjev-2b, PurpleMIST-Mini-1.0 (Olaverse) (purplemist-mini-1.0), Sage 1.4 (Levanto Labs) (sage-1.4.0), SubQ Snap (preview, SubQ) (subq-snap-preview)) to the eleven full-draw rows of v1.6.16 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so every carried row keeps identical point scores, axes, capability, cost and speed objects, and the listed-not-ranked reflex-instinct-0.6b and the unranked A2 measurement keep their wording. What moved on carried rows, counted exactly. RANKS: rows ranked in this release - amos-1-large, amos-1-medium, metask_jev_rain_31b_trained_v3, pjev-2b, purplemist-mini-1.0 - sit above some carried rows, so ranks recompute over the new roster and each carried rank moves only by the number of newly ranked rows above it: attest-31b-v1.0 capability 4 -> 6, julia-1 A 10 -> 15; B 10 -> 15; C 10 -> 15; capability 10 -> 15, krino-2b A 7 -> 10; B 7 -> 10; C 7 -> 10; capability 8 -> 13, metask_jev_rain_12b_trained capability 3 -> 5, metask_jev_rain_31b_trained capability 2 -> 4, phocinae-largha-150m-v1 A 9 -> 14; B 9 -> 14; C 9 -> 14; capability 9 -> 14, standard_one_3b_sh A 6 -> 7; B 6 -> 7; C 6 -> 7; capability 7 -> 11, torchcast-decision-4b-v1.1 C 4 -> 5; capability 5 -> 7, uniphore-4b-decider A 5 -> 6; B 5 -> 6; C 5 -> 6; capability 6 -> 10, vllm-sr-d3 A 8 -> 11; B 8 -> 11; C 8 -> 11. Rows listed but not ranked take no place in any order. CONFIDENCE INTERVALS: unlike v1.6.16, new keys sort into the middle of the key-sorted roster, and the scorer seeds each row's bootstrap with the shared seed 16 plus the row's position in that roster (each row has its own resample; the v1.6.15 note above that says the scorer draws one paired resample is corrected by the v1.6.16 note), so a carried row whose position changed gets a different interval while no point estimate moves. Carried rows whose intervals moved: attest-31b-v1.0, julia-1, krino-2b, metask_jev_rain_12b_trained, metask_jev_rain_31b_trained, phocinae-largha-150m-v1, reflex-instinct-0.6b, standard_one_3b_sh, torchcast-decision-4b-v1.1, uniphore-4b-decider, vllm-sr-d3. DIAGNOSTICS: the API-basis median diagnostic is computed over the ranked field, so it moved from 9.40342052601045 to 8.245659392674778; that moves the stored A-basis diagnostic (the row field v16.raw_on_A) of exactly the carried rows named here: standard_one_3b_sh: intelligence 29.2660 -> 28.9168, capability 53.1199 -> 52.9453; and the equating pool gains metask_jev_rain_31b_trained_v3 and pjev-2b and purplemist-mini-1.0 (10 -> 13 members; the self-hosted ranked field changes with it) and the release-level equating-offset diagnostic moved from I 0.2288 / C 1.2340 to I 0.1329 / C 1.5418. Neither is part of any score, rank or axis on this release: the hosted-API rows scored in this invocation are full-set rows and are not equated, and the carried A2 measurement keeps its own A2 equating and is not rescored. reflex-instinct-0.6b stays LISTED BUT NOT RANKED under #18761 and the unranked A2 measurement of v1.6.14 is carried; neither is changed.

Cost on amos-1-large, and the scope of the cost notes above: the inherited note's "every row is under the published v1.6 cost ceiling of USD 0.0646 per 1,000 decisions" is NOT true of amos-1-large (cost ceiling exceeded, as it was not true of vllm-sr-d3 in v1.6.16). Amos 1 large (Scira) is priced as an ESTIMATE at its frozen base-model market reference times the provider-reported tokens on the full 1,500-row basis: 1,938,726 input tokens and 0 output tokens, USD 0.5428433 per 1,000 decisions, 8.40x that ceiling. It is not a bill: the endpoint is free and keyless. Its Cost axis is 17.960, below 50, so the squared cost gate of the composite applies (composite A 5.536, rank 12 of 15), and on the merged live board it is above the official Jev-class cost cap, so it is NOT on the default (cost-capped) Capability ranking.

Cost on amos-1-medium, and the scope of the cost notes above: the inherited note's "every row is under the published v1.6 cost ceiling of USD 0.0646 per 1,000 decisions" is NOT true of amos-1-medium (cost ceiling exceeded, as it was not true of vllm-sr-d3 in v1.6.16). Amos 1 medium (Scira) is priced as an ESTIMATE at its frozen base-model market reference times the provider-reported tokens on the full 1,500-row basis: 1,938,726 input tokens and 0 output tokens, USD 0.1292484 per 1,000 decisions, 2.00x that ceiling. It is not a bill: the endpoint is free and keyless. Its Cost axis is 36.657, below 50, so the squared cost gate of the composite applies (composite A 16.594, rank 8 of 15), and on the merged live board it is above the official Jev-class cost cap, so it is NOT on the default (cost-capped) Capability ranking.

Board effect, and the basis for publishing it. Compared on the merged live board (the v1.6.1 feed plus the published fresh-draw cohort rows) before and after this release, over the mixed, open-weights and API boards: the top five of composites A, B and C is unchanged on all three boards; unchanged top fives also: Capability with no cost and no latency cap. The top five changes in: the mixed board (open-weights and API together): Capability with the official cost and latency caps (the default ranking) - before quyet-1-0-large, jeff_1_0_large, decisio-gemma-4-31b-v080, metask-jev-rain-31B-trained, sage-1.3.0; after quyet-1-0-large, jeff_1_0_large, metask-jev-rain-31B-trained service v3, decisio-gemma-4-31b-v080, metask-jev-rain-31B-trained (metask-jev-rain-31B-trained service v3 enters at #3) | the mixed board (open-weights and API together): Capability with the official cost cap and no latency cap - before quyet-1-0-large, jeff_1_0_large, decisio-gemma-4-31b-v080, wity-1, metask-jev-rain-31B-trained; after quyet-1-0-large, jeff_1_0_large, metask-jev-rain-31B-trained service v3, decisio-gemma-4-31b-v080, wity-1 (metask-jev-rain-31B-trained service v3 enters at #3) | the open-weights board: Capability with the official cost and latency caps (the default ranking); the open-weights board: Capability with the official cost cap and no latency cap - before quyet-1-0-large, jeff_1_0_large, decisio-gemma-4-31b-v080, metask-jev-rain-31B-trained, metask-jev-rain-12B-trained; after quyet-1-0-large, jeff_1_0_large, metask-jev-rain-31B-trained service v3, decisio-gemma-4-31b-v080, metask-jev-rain-31B-trained (metask-jev-rain-31B-trained service v3 enters at #3) | the API board: Capability with the cost cap off and latency 2x (Florian's settings) - before spx-cd-pro, sage-1.3.0, jev-1.13.0, fastino-glide, liquid-d1; after Amos 1 large (Scira), spx-cd-pro, sage-1.3.0, jev-1.13.0, fastino-glide (Amos 1 large (Scira) enters at #1). Added rows that enter a top five: Amos 1 large (Scira), metask-jev-rain-31B-trained service v3 (metask-jev-rain-31B-trained service v3 - a paid fast-lane row, order 4d9fef10); Amos 1 large (Scira) enters on Florian's explicit GO of 13 Oct 2026 (Telegram card #17487, Publish), for this row and this view, distinct from card 17392 (vllm-sr-d3). The other added rows (Amos 1 medium (Scira), pjev-2b, PurpleMIST-Mini-1.0 (Olaverse), Sage 1.4 (Levanto Labs), SubQ Snap (preview, SubQ)) appear in no top five. Amos 1 large's entry is not a paid order: it is a hosted row ranked above the cost ceiling and published on Florian's explicit GO of 13 Oct 2026 (Telegram card #17487, Publish), for this row and this view, distinct from card 17392 (vllm-sr-d3). The cause of the paid row's entry is the paid fast-lane order 4d9fef10 (a re-submission of the weights of order 147c5e18, disclosed in its row note): a paid public fast-lane row publishes automatically under the paid exception even when it changes a top five, exactly as the two paid metask rows did in v1.6.10 (whose release authority records the same top-five change); the change is disclosed here and in the proof authority.

amos-1-large: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. Hosted API: the row is the vendor-hosted api.amos.scira.ai endpoint, not self-hosted weights - open weights are declared at mukaddamzaid/amos-1-large (Apache-2.0, revision declared by the submitter, not verified), but this measurement is of the endpoint, whose deployed weights were not independently inspected, and the vendor reports its token usage. Free, keyless, one request per second for the documented 60 requests/minute; latency measured from Sandy (Germany) on the official per-item latency subset without API adjustment: p50 0.5090 s, p95 0.8543 s. All 1,200 sealed items were logged to provider scira before the first request. CUSTODY CONDITION: after this hosted exposure, no self-hosted measurement of Amos weights on this draw may be shown as a clean measurement. Cost is an ESTIMATE: the exact frozen base-model market reference times the provider-reported 1,938,726 input tokens (output 0), USD 0.542843 per 1,000 decisions, 8.40x the official cost cap, disclosed in the cost notes above; it is not a bill. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 0.5090 s, p95 raw 0.8543 s.

amos-1-medium: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. Hosted API: the row is the vendor-hosted api.amos.scira.ai endpoint, not self-hosted weights - open weights are declared at mukaddamzaid/amos-1-medium (Apache-2.0, revision declared by the submitter, not verified), but this measurement is of the endpoint, whose deployed weights were not independently inspected, and the vendor reports its token usage. Free, keyless, one request per second for the documented 60 requests/minute; latency measured from Sandy (Germany) on the official per-item latency subset without API adjustment: p50 0.4435 s, p95 0.5068 s. All 1,200 sealed items were logged to provider scira before the first request. CUSTODY CONDITION: after this hosted exposure, no self-hosted measurement of Amos weights on this draw may be shown as a clean measurement. Cost is an ESTIMATE: the exact frozen base-model market reference times the provider-reported 1,938,726 input tokens (output 0), USD 0.129248 per 1,000 decisions, 2.00x the official cost cap, disclosed in the cost notes above; it is not a bill. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 0.4435 s, p95 raw 0.5068 s.

metask_jev_rain_31b_trained_v3: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. PAID PUBLIC FAST-LANE ORDER 4d9fef10, published under the paid exception. RE-SUBMISSION, DISCLOSED: the same LoRA weights as the published metask_jev_rain_31b_trained row (order 147c5e18, v1.6.10) with a changed service/ layer (for example its yes/no constant); those changes may have been tuned on that row's published v1.6.10 aggregates (custodian #18945). Both rows are shown, each with its own numbers; the earlier row is carried unchanged, and no third same-weights row is admitted on this draw. HARDWARE DIFFERS FROM THE EARLIER ROW: this service v3 was measured on an evaluator-owned Lium RTX PRO 6000 96 GB pod (its reviewed recipe needs 96 GB), in an offline read-only container (--network none, verified by docker inspect before the input upload), while the earlier metask rows of this draw were timed on an H100 80GB, so the Speed axis (84.666; p50 raw 0.1808 s, adjusted 0.5116 s under the x2 + 0.15 s assumption) rests on different hardware; vllm-sr-d3 (v1.6.16) was also timed on an RTX PRO 6000 96 GB class GPU (Verda), so two rows of this draw share that class while the other self-hosted GPU rows are H100. The service reports generated output tokens (840,049 input / 17,397 output). Cost is the v1.5-M2 base-model reference for the exact base google/gemma-4-31B-it (OpenRouter list price USD 0.09/M input, 0.34/M output, snapshot 2026-10-13T12:10:25Z) times the service's own measured usage: USD 0.054346 per 1,000 decisions, under the cost ceiling, estimated and not charged. Weights file shas: model 1b9b1d62..., adapter 2b956899..., code tree 6a1234ee...

pjev-2b: 1,485 of 1,500 attempted answered (HTTP 200: 1,485; HTTP 422: 15); 15 not answered. The 15 misses are HTTP 422 refusals by the author's own letter_adapter.py, which raises rather than truncating a prompt above its 16,000-token contract; they are EXACTLY the same 15 items (106,804-122,936 characters) that uniphore-4b-decider (HTTP 422), attest-31b-v1.0 (HTTP 500) and standard_one_3b_sh (HTTP 422) failed on in the published v1.6.16 runs, verified set-equal, and julia-1's 17 refusals are a strict superset. Correction of an earlier entry text: torchcast-decision-4b-v1.1 and both metask_jev_rain rows answered all 1,500 and are NOT among the rows that refused them. The totals (1,485 answered, 15 HTTP 422, 0 other failures) were pre-registered before the run and came back exact; all answered items native. SPLIT WINDOW, DISCLOSED: the row was measured across four sittings under different host load on the evaluator's shared CPU (09:07-13:16Z until a pressure guard stopped it at load 57; two short attempts stopped by swap another job had left on the host; and 18:36-19:41Z to the end; one-minute load 6.96-54.44, mean 15.09 over 323 samples), resumed by task id so no item was answered twice. Its Speed is therefore a loaded-shared-CPU figure with the same kind of interference as reflex-instinct-0.6b, and a declared lower bound against the author's own H100 reference of 20-62 ms; the standard self-hosted x2 + 0.15 s adjustment (an assumption) is applied on top and the raw p50 10.06 s / p95 30.19 s are kept. Weights run in float32 (a strict upcast of the stored bfloat16, via the pre-registered PJEV_DTYPE one-line change that defaults to the author's bfloat16); serve.py and decision_core.py are byte-identical to the author's. Cost is a size-class ESTIMATE on the frozen DeepInfra 2-4B line (USD 0.03/M input, 0.0/M output; the same treatment the board gives decision-2b on the same MiniCPM5-2B base), 813,676 input tokens, USD 0.016274 per 1,000 decisions, not a bill. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 10.0633 s, p95 raw 30.1948 s.

purplemist-mini-1.0: 1,485 of 1,500 attempted answered (HTTP 200: 1,485; HTTP 422: 15); 15 not answered. The refusals are honest HTTP 422s: with --no-truncate the author's code refuses rather than truncates a prompt over 65,536 tokens, and the draw's 15 longest items (76-80 k tokens) are scored as wrong; they are the same 15 items that uniphore-4b-decider, attest-31b-v1.0, standard_one_3b_sh and pjev-2b failed on. DISCLOSED: the pre-registration predicted 0 refusals from a character-based estimate; the offline token count and the live 422s both show 15. TOKENS ARE AN OFFLINE COUNT, not provider usage (CoS deputy #18974): the author's server reports no usage, so input tokens were counted with the author's own pinned tokenizer and unchanged encode() on the exact prompts (independent recount PASS): 700,492 input tokens over the 1,485 answered items, output 0 (one forward pass, nothing generated). Measured on the evaluator's own shared CPU (AMD Zen 2, float32), not a dedicated machine, with the one-minute load logged; Speed is a loaded-shared-CPU lower bound and the standard x2 + 0.15 s adjustment (an assumption) is applied on top. Cost is an ESTIMATE on the exact base-model reference, USD 0.009340 per 1,000 decisions, not a bill. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 3.6021 s, p95 raw 8.9970 s.

sage-1.4.0: 1,483 of 1,500 attempted answered (HTTP 200: 1,483; HTTP 400: 15; HTTP 504: 2); 17 not answered. Hosted API (Levanto Labs), measured from Sandy (Germany) without API adjustment; native probabilities on all three question types; all 1,200 sealed items were logged to provider levanto before the first request; 665,989 input tokens and 0 output tokens. Treatment of its cost axis: UNPRICED under the frozen pricing_v15 path (sha256 dae86740...): proprietary hosted model with no base-model reference, and levanto-sage-v1.4 is in neither AGE_QUALIFIED_API nor LAUNCH_LIST_PRICE_API. sage-1.3.0's published row carries Levanto's list tariff (USD 0.05/M input, USD 10/M output), set before these sets bound new rows; it is not carried over here. Its Capability 74.773 is higher than that of 10 of the 15 ranked rows of this draw (it would sit at #6 of 16 in the draw's Capability order); it is withheld from every ranking, not rated lower. Ranking it would put it into every public Capability ranking, which needs Florian's review. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 1.7411 s, p95 raw 7.5714 s.

subq-snap-preview: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. NOT RANKED, and here is exactly why: CoS deputy decision #18975 accepts the measurement but gives the row no cost axis until a frozen-pricing change for its preview tariff (USD 0.05/M input, output free) passes re-freeze, unchanged-row proof and independent review; its model is proprietary with no base-model reference and the days-old preview tariff is in neither frozen tariff set, so under the frozen pricing path the cost is unpriced. Without a cost axis there is no composite, so the row shows Intelligence 72.250, Calibration 90.697 and Capability 81.474 (and Speed 86.405) and carries no rank, no composite and no place in the Capability ranking (the same conservative reading applied to reflex-instinct-0.6b under #18761). Its Capability 81.474 is higher than that of 14 of the 15 ranked rows of this draw (it would sit at #2 of 16 in the draw's Capability order); it is withheld from every ranking, not rated lower. Ranking it would put it into every public Capability ranking, which needs Florian's review. Where to look: it appears in the "All data" table and its detail view only. Hosted API, measured from Sandy (Germany) without API adjustment; 1,943,705 input tokens and 0 output tokens (nothing generated). SubQ retains API inputs indefinitely by default; acceptable only because every sealed item of this draw was already retired, and all 1,200 sealed items were logged to the provider before the first request. Hosting implementation and deployed weights were not independently inspected. Speed figures are the published method's percentiles over this draw's open standard and judge items: p50 raw 0.4656 s, p95 raw 0.4915 s.

v1.6.18 ADDS 3 ROWS (Bespoke Nimble-v4 (Bespoke Labs) (nimble-v4), Bespoke Nimble-v4-max (Bespoke Labs) (nimble-v4-max), Respan Span-02 (respan-span-02)) to the eighteen full-draw rows of v1.6.17 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so every carried row keeps identical point scores, axes, capability, cost and speed objects, and the listed-not-ranked reflex-instinct-0.6b and the unranked A2 measurement keep their wording. What moved on carried rows, counted exactly. RANKS: amos-1-large A 12 -> 13; B 12 -> 13; C 12 -> 13, amos-1-medium A 8 -> 9; B 8 -> 9; C 8 -> 9; capability 8 -> 9, julia-1 A 15 -> 16; B 15 -> 16; C 15 -> 16; capability 15 -> 16, krino-2b A 10 -> 11; B 10 -> 11; C 10 -> 11; capability 13 -> 14, phocinae-largha-150m-v1 A 14 -> 15; B 14 -> 15; C 14 -> 15; capability 14 -> 15, pjev-2b A 9 -> 10; B 9 -> 10; C 9 -> 10; capability 9 -> 10, purplemist-mini-1.0 A 13 -> 14; B 13 -> 14; C 13 -> 14; capability 12 -> 13, standard_one_3b_sh A 7 -> 8; B 7 -> 8; C 7 -> 8; capability 11 -> 12, torchcast-decision-4b-v1.1 capability 7 -> 8, uniphore-4b-decider A 6 -> 7; B 6 -> 7; C 6 -> 7; capability 10 -> 11, vllm-sr-d3 A 11 -> 12; B 11 -> 12; C 11 -> 12. Each moved rank shifts only by the newly ranked rows above it. Rows listed but not ranked take no place in any order. CONFIDENCE INTERVALS: as in v1.6.17, new keys sort into the middle of the key-sorted roster, and the scorer seeds each row's bootstrap with the shared seed 16 plus the row's position in that roster (each row has its own resample; the v1.6.15 note above that says the scorer draws one paired resample is corrected by the v1.6.16 note), so a carried row whose position changed gets a different interval while no point estimate moves. Carried rows whose intervals moved: phocinae-largha-150m-v1, pjev-2b, purplemist-mini-1.0, reflex-instinct-0.6b, sage-1.4.0, standard_one_3b_sh, subq-snap-preview, torchcast-decision-4b-v1.1, uniphore-4b-decider, vllm-sr-d3. DIAGNOSTICS: the API-basis median diagnostic is 7.703968975298743 (previous 8.245659392674778); carried v16.raw_on_A moves: standard_one_3b_sh: intelligence 28.9168 -> 28.7534, capability 52.9453 -> 52.8636. Equating offsets are I 0.1005 / C 1.4616 (previous I 0.1329 / C 1.5418); the equating pool gains respan-span-02 (13 -> 14 members; the self-hosted ranked field changes with it) and the equating pool has 14 members. These diagnostics are not part of any score, rank or axis on this release: the hosted-API rows scored in this invocation are full-set rows and are not equated, and the carried A2 measurement keeps its own A2 equating and is not rescored. reflex-instinct-0.6b stays LISTED BUT NOT RANKED under #18761 and the unranked A2 measurement of v1.6.14 is carried; neither is changed.

Cost on respan-span-02, and the scope of the cost notes above: the inherited note's "every row is under the published v1.6 cost ceiling of USD 0.0646 per 1,000 decisions" is NOT true of respan-span-02 (cost ceiling exceeded, as it was not true of vllm-sr-d3 in v1.6.17). Respan Span-02 is priced as an ESTIMATE at its frozen base-model market reference times the provider-reported tokens on the full 1,500-row basis: 776,560 input tokens and 102328 output tokens, USD 0.0670592 per 1,000 decisions, 1.04x that ceiling. It is not a bill: the endpoint is self-hosted on an evaluator-owned rented pod. Its Cost axis is 45.206, below 50, so the squared cost gate of the composite applies (composite A 51.804, rank 6 of 16), and on the merged live board it is above the official Jev-class cost cap, so it is NOT on the default (cost-capped) Capability ranking.

Board effect: compared on the merged live board before and after v1.6.18, over the mixed, open-weights and API boards, composites A/B/C and Capability with official caps, no caps, cost off + latency 2x (Florian settings), and official cost + no latency cap: No top five changes in any view. Neither Nimble-v4 nor Nimble-v4-max enters any ranked view; both are listed but not ranked under #19084. Respan Span-02 enters no top five and is outside all official-cost-cap Capability views.

nimble-v4: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. Vendor-hosted api.bespokelabs.ai /v1/systemone API, model `nimble-v4`, through the unchanged TypeSafe adapter; latency measured from Sandy (Germany) on the official per-item latency subset without API adjustment. Full S1200+P300 draw of v1.6-regular-20261012 through the unchanged run_api_full_v161.py; the full-set exposure gate logged all 1,200 sealed items to provider `bespoke` before the first request (CoS deputy #18998/#19084, custodian #18999; every sealed item of this draw was already retired). Native probabilities on all three question types. Hosting implementation and deployed weights were not independently inspected. Measured as our own add after Bespoke Labs' public announcement of 13 Oct 2026 (no paid order); key on Benchmark Heaven's own account with Bespoke's free credit. CoS deputy decision #19084 (one-time ruling, the unranked SubQ Snap precedent #18975/#19046): measured, but the frozen pricing path gives it no eligible price, so it carries no cost axis until a separate pricing change passes re-freeze, unchanged-row proof and independent review. Without a cost axis there is no composite, so the row shows Intelligence, Calibration, Capability and Speed and is not ranked. UNPRICED under the frozen pricing_v15 path (sha256 dae86740...): proprietary hosted model with no documented base model (Bespoke's Hugging Face repos for v4 are private), and `nimble-v4` is in neither AGE_QUALIFIED_API nor LAUNCH_LIST_PRICE_API. Bespoke's own list tariff (USD 0.04/M input, output free) is recorded here for information only and is not used. Measured Intelligence 41.405, Calibration 86.634, Capability 64.020 and Speed 88.399 only; NOT RANKED: no Cost, no Composite, no rank in any view, including the Capability order. Where to look: the collapsed "All data" table and the detail view. Provider-reported usage: 1,935,351 input tokens and 3,000 output tokens (usage, not an inspected implementation). Latency on the official subset, without API adjustment: p50 raw 0.2324 s, p95 raw 0.6222 s. Exposure was logged to provider bespoke before dispatch. No top five changes; both rows are excluded from every ranked view.

nimble-v4-max: 1,500 of 1,500 attempted answered (HTTP 200: 1,500); 0 not answered. Vendor-hosted api.bespokelabs.ai /v1/systemone API, model `nimble-v4-max`, through the unchanged TypeSafe adapter; latency measured from Sandy (Germany) on the official per-item latency subset without API adjustment. Full S1200+P300 draw of v1.6-regular-20261012 through the unchanged run_api_full_v161.py; the full-set exposure gate logged all 1,200 sealed items to provider `bespoke` before the first request (CoS deputy #18998/#19084, custodian #18999; every sealed item of this draw was already retired). Native probabilities on all three question types. Hosting implementation and deployed weights were not independently inspected. Measured as our own add after Bespoke Labs' public announcement of 13 Oct 2026 (no paid order); key on Benchmark Heaven's own account with Bespoke's free credit. CoS deputy decision #19084 (one-time ruling, the unranked SubQ Snap precedent #18975/#19046): measured, but the frozen pricing path gives it no eligible price, so it carries no cost axis until a separate pricing change passes re-freeze, unchanged-row proof and independent review. Without a cost axis there is no composite, so the row shows Intelligence, Calibration, Capability and Speed and is not ranked. UNPRICED under the frozen pricing_v15 path (sha256 dae86740...): proprietary hosted model with no documented base model (Bespoke's Hugging Face repos for v4 are private), and `nimble-v4-max` is in neither AGE_QUALIFIED_API nor LAUNCH_LIST_PRICE_API. Bespoke's own list tariff (USD 0.09/M input, output free) is recorded here for information only and is not used. Measured Intelligence 68.185, Calibration 91.250, Capability 79.717 and Speed 91.451 only; NOT RANKED: no Cost, no Composite, no rank in any view, including the Capability order. Where to look: the collapsed "All data" table and the detail view. Provider-reported usage: 1,935,351 input tokens and 3,000 output tokens (usage, not an inspected implementation). Latency on the official subset, without API adjustment: p50 raw 0.2545 s, p95 raw 0.2813 s. Exposure was logged to provider bespoke before dispatch. No top five changes; both rows are excluded from every ranked view.

respan-span-02: Regular queue GitHub issue #215, no paid order. Custodian #19055 admitted one use of the frozen draw input; container isolation was proven at 05:45:26Z (pod clock); the sealed file reached the pod host at 05:45:48Z (evaluator clock); the measuring container was re-created and re-proven at 05:45:50Z (pod clock), with the first sealed item entering at 05:45:55Z (pod clock). The host kept its network for ssh; cross-clock skew cannot be excluded. CoS deputy #19087/#19088: one EU RTX 5090, hard cap USD 2.00; actual approximately USD 0.20. Speed measured on an RTX 5090 with a Blackwell-only engine, NOT the H100 most GPU rows used. evaluator-owned rented Lium GPU pod, 1x NVIDIA RTX 5090 32 GB (Romania), NOT the 1x H100 80 GB on which most of this draw's GPU rows were timed: the author's engine runs only on Blackwell (sm_120a), so this row's Speed axis rests on different hardware. The author's own Rust/CUDA dllm-server, built unchanged from their Dockerfile at the pinned revision (weights model.safetensors sha256 5105d39d..., tokenizer cc8d3a0c..., public MTP draft google/gemma-4-26B-A4B-it-assistant pre-staged), started by their own launch.sh with their documented Decision Index settings (container environment HOST=127.0.0.1, PORT=8000; weights mounted read-only at /model, the pre-staged draft at /data) in a container with --network none. Isolation timeline: the container's cut was proven by docker inspect and a failing outbound probe at 05:45:26Z (pod clock) before the sealed input file was copied to the pod host at 05:45:48Z (evaluator clock); the measuring container was then re-created with the same --network none setting and re-proven at 05:45:50Z before the first sealed item was sent at 05:45:55Z. The pod host itself kept its network for the evaluator's ssh session, as for every self-hosted row; no request left the container; one disclosed invocation change: launch.sh is stored without the executable bit in the repository (mode 100644), so the unchanged file was run through the interpreter its own shebang names (/bin/bash) instead of being exec'd directly. Driven by the unchanged run_v15 runner and TypeSafe adapter against /v1/systemone, sequentially, after a 4-item synthetic smoke gate. The standard self-hosted x2 + 0.15 s own-server adjustment (an assumption, not measured) applies on top of the raw p50/p95. 15 of 1,500 requests returned HTTP 400 because prompt + 256-token cap exceeds the server's 16,384-token context: exactly the 15 task ids pre-registered from an offline count with the author's own tokenizer (the same 15 that Attest-31B, Standard One 3B SH, Uniphore-4B-Decider and PurpleMIST-Mini failed on); they are scored as wrong in the full denominator. Measured 14 Oct 2026 on the frozen v1.6-regular-20261012 self-hosted input (sha256 dfd36720077ef7c41ace367524896507c7f44ce71306fb3e659e8b85069d995b); pod removed afterwards. Regular-queue request GitHub issue #215; CoS deputy #19087/#19088 (spend), custodian #19055 (draw use). ESTIMATE (base-model reference; self-hosted open weights, no public tariff for these weights): the frozen market reference google/gemma-4-26b-a4b-it USD 0.09/M input, USD 0.3/M output for the declared base Gemma 4 26B-A4B (catalog id google/gemma-4-26b-a4b-it, supplied by the evaluator because the frozen path matches base names case-sensitively; the submission's model card spells it google/gemma-4-26B-A4B-it) x this row's own measured tokens on the full 1,500-row basis (776,560 input and 102,328 output tokens as reported by the author's server; the 15 refused items count as zero). Estimated, not charged; not a quote from the author or any host. OVER THE OFFICIAL COST CAP, DISCLOSED: USD 0.067059 per 1,000 decisions is 1.04x the official cap USD 0.064595; the row is ranked (v1.6.16 vllm-sr-d3 precedent) and falls outside the official-caps board views by construction. Pre-registration matched exactly: 1,485 of 1,500 answered; the 15 HTTP 400 refusals are exactly the 15 pre-registered over-length task ids; 776,560 input tokens. r111/PREREG-R111.md sha256 9aa388b0…; receipts r111/receipts/TOKCOUNT-SPAN02-R111.json and r112/receipts/ROW-RESPAN-SPAN-02-R112.json. Native probabilities on all three types. Official-subset latency: p50 raw 0.0270 s, p95 raw 0.6446 s; standard self-hosted x2 + 0.15 s adjustment (assumption, not measured). Ranked with over-cap disclosure and excluded from official-caps views by construction. No top five changes.

SubQ Snap PRICE-ONLY ADDENDUM: its measurement remains v1.6.17 (last measured 2026-10-13); no model was called again. The vendor publishes USD 0.05 per million input tokens and no output charge; the measured 1,943,705 input tokens and 0 output tokens produce USD 0.0647901667 per 1,000 decisions, 1.003x the official cap. The public basis discloses the capacity-limited public preview and waitlist under deputy ruling #19174. The initial candidate preview GO was Telegram card #17513. Florian approved publication of v1.6.20 on 2026-10-15T16:53Z in a direct message. The chief of staff recorded that as the answer "Publish (recommended)" to Telegram card #17515 (DECISIONS.md 2026-10-15 16:53 UTC; board #19649) - the card the refreshed merged-board full ranking and radar had been sent on, with preview PNG sha256 8cb19a14e4304228b3fccbd1a4a12feabb53b5a9fb884434a9a95c6a7639d88e attached. The card's own button was not pressed. The candidate and preview agree on SubQ point estimates: A 57.1609, Capability 81.4737, cost axis 45.6547. It is ranked outside official cost-capped views. Carried rank movements from this repricing: amos-1-large: A 13 → 14, B 13 → 14, C 13 → 14, capability 3 → 4, amos-1-medium: A 9 → 10, B 9 → 10, C 9 → 10, capability 9 → 10, attest-31b-v1.0: capability 6 → 7, julia-1: A 16 → 17, B 16 → 17, C 16 → 17, capability 16 → 17, krino-2b: A 11 → 12, B 11 → 12, C 11 → 12, capability 14 → 15, metask_jev_rain_12b_trained: capability 5 → 6, metask_jev_rain_31b_trained: capability 4 → 5, metask_jev_rain_31b_trained_v3: capability 2 → 3, phocinae-largha-150m-v1: A 15 → 16, B 15 → 16, C 15 → 16, capability 15 → 16, pjev-2b: A 10 → 11, B 10 → 11, C 10 → 11, capability 10 → 11, purplemist-mini-1.0: A 14 → 15, B 14 → 15, C 14 → 15, capability 13 → 14, respan-span-02: A 6 → 7, B 6 → 7, C 6 → 7, capability 7 → 8, standard_one_3b_sh: A 8 → 9, B 8 → 9, C 8 → 9, capability 12 → 13, torchcast-decision-4b-v1.1: C 5 → 6, capability 8 → 9, uniphore-4b-decider: A 7 → 8, B 7 → 8, C 7 → 8, capability 11 → 12, vllm-sr-d3: A 12 → 13, B 12 → 13, C 12 → 13.

Board effect: merged-live-board comparison before/after v1.6.20: 20 of 21 top-five lists are unchanged. On the API Capability view with the cost cap off and the official 2x latency setting, SubQ Snap enters at #1 of 23 (81.474), ahead of Amos 1 large (79.359). It remains excluded from every official cost-capped view because its estimated USD 0.064790 per 1,000 decisions is above the USD 0.064595 cap.

v1.6.21 ADDS 1 ROW (d1-ultra (Liquid AI, liquid-d1-ultra)) to the 21 full-draw rows of v1.6.20 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so every carried row keeps identical point scores, axes, capability, cost and speed objects, and the listed-not-ranked rows (reflex-instinct-0.6b, nimble-v4, nimble-v4-max, sage-1.4.0) and the unranked A2 measurement keep their wording. What moved on carried rows, counted exactly. RANKS: amos-1-large A 14 -> 15; B 14 -> 15; C 14 -> 15; capability 4 -> 5, amos-1-medium A 10 -> 11; B 10 -> 11; C 10 -> 11; capability 10 -> 11, attest-31b-v1.0 A 2 -> 3; B 2 -> 3; C 1 -> 2; capability 7 -> 8, julia-1 A 17 -> 18; B 17 -> 18; C 17 -> 18; capability 17 -> 18, krino-2b A 12 -> 13; B 12 -> 13; C 12 -> 13; capability 15 -> 16, metask_jev_rain_12b_trained A 3 -> 4; B 1 -> 2; C 2 -> 3; capability 6 -> 7, metask_jev_rain_31b_trained A 4 -> 5; B 3 -> 4; C 3 -> 4; capability 5 -> 6, metask_jev_rain_31b_trained_v3 A 5 -> 6; B 5 -> 6; C 4 -> 5; capability 3 -> 4, phocinae-largha-150m-v1 A 16 -> 17; B 16 -> 17; C 16 -> 17; capability 16 -> 17, pjev-2b A 11 -> 12; B 11 -> 12; C 11 -> 12; capability 11 -> 12, purplemist-mini-1.0 A 15 -> 16; B 15 -> 16; C 15 -> 16; capability 14 -> 15, respan-span-02 A 7 -> 8; B 7 -> 8; C 7 -> 8; capability 8 -> 9, standard_one_3b_sh A 9 -> 10; B 9 -> 10; C 9 -> 10; capability 13 -> 14, subq-snap-preview A 6 -> 7; B 6 -> 7; C 5 -> 6, torchcast-decision-4b-v1.1 A 1 -> 2; B 4 -> 5; C 6 -> 7; capability 9 -> 10, uniphore-4b-decider A 8 -> 9; B 8 -> 9; C 8 -> 9; capability 12 -> 13, vllm-sr-d3 A 13 -> 14; B 13 -> 14; C 13 -> 14. Each moved rank shifts only by the newly ranked row above it. Rows listed but not ranked take no place in any order. CONFIDENCE INTERVALS: as in v1.6.17 and v1.6.18, the new key sorts into the middle of the key-sorted roster, and the scorer seeds each row's bootstrap with the shared seed 16 plus the row's position in that roster, so a carried row whose position changed gets a different interval while no point estimate moves. Carried rows whose intervals moved: metask_jev_rain_12b_trained, metask_jev_rain_31b_trained, metask_jev_rain_31b_trained_v3, nimble-v4, nimble-v4-max, phocinae-largha-150m-v1, pjev-2b, purplemist-mini-1.0, reflex-instinct-0.6b, respan-span-02, sage-1.4.0, standard_one_3b_sh, subq-snap-preview, torchcast-decision-4b-v1.1, uniphore-4b-decider, vllm-sr-d3. DIAGNOSTICS: the API-basis median diagnostic is 7.703968975298743 (previous 7.703968975298743); carried v16.raw_on_A moves: none. Equating offsets are I 0.1005 / C 1.4616 (previous I 0.1005 / C 1.4616); the equating pool keeps its 14 members (a full-set API row is not equated and does not join it). These diagnostics are not part of any score, rank or axis on this release. reflex-instinct-0.6b stays LISTED BUT NOT RANKED under #18761 and the unranked A2 measurement of v1.6.14 is carried; neither is changed.

Board effect: merged-live-board top-five comparison before/after v1.6.21 over the mixed, open-weights and API boards, composites A/B/C and Capability with official caps, no caps, cost off + latency 2x (Florian settings) and official cost cap + no latency cap: 11 of 21 top-five lists change, all of them because d1-ultra enters. mixed board (open weights + API), composite A: d1-ultra (Liquid AI) enters at #1, decisio v0.8.0 on gemma-4-31B-it leaves the top five | mixed board (open weights + API), composite B: d1-ultra (Liquid AI) enters at #1, wity-1 (Wity, reasoning auto) leaves the top five | mixed board (open weights + API), composite C: d1-ultra (Liquid AI) enters at #1, decisio v0.8.0 on gemma-4-31B-it leaves the top five | mixed board (open weights + API), Capability, official cost + latency caps (default): d1-ultra (Liquid AI) enters at #3, metask-jev-rain-31B-trained leaves the top five | mixed board (open weights + API), Capability, official cost cap + no latency cap: d1-ultra (Liquid AI) enters at #3, wity-1 (Wity, reasoning auto) leaves the top five | API board, composite A: d1-ultra (Liquid AI) enters at #1, wity-1 (Wity, reasoning auto) leaves the top five | API board, composite B: d1-ultra (Liquid AI) enters at #1, Jev 1.13.0 (TypeSafe AI) leaves the top five | API board, composite C: d1-ultra (Liquid AI) enters at #1, wity-1 (Wity, reasoning auto) leaves the top five | API board, Capability, official cost + latency caps (default): d1-ultra (Liquid AI) enters at #1, Mercury Decide leaves the top five | API board, Capability, cost off + latency 2x (Florian's settings): d1-ultra (Liquid AI) enters at #2, Jev 1.13.0 (TypeSafe AI) leaves the top five | API board, Capability, official cost cap + no latency cap: d1-ultra (Liquid AI) enters at #1, SPX-CD Flash leaves the top five. Ranked rows: mixed 193 -> 194, open weights 162 (unchanged), API 31 -> 32. No other row enters or leaves any top five.

Publication of v1.6.21: on Florian's GO of 16 Oct 2026 in the laptop chat ("do we have released all the new JevBench and ImageJevBench pages? If not, please go for it"), with the merged-board top-five preview sent to him as a Telegram card first because d1-ultra changes top-five lists. The top-five preview (PNG sha256 b237ebbe44e0a74651f51db1435aff8aa951775ec8f22b11786ef97e170b5d85) was sent to Florian as Telegram card #17650. It offered a hold for 60 minutes; there was no answer, so it was published on his direct-message GO above at 2026-10-16T09:13Z ("no answer within the 60-minute hold window"; DECISIONS.md 2026-10-16 09:14Z). The card's own button was not pressed.

liquid-d1-ultra: d1-ultra (Liquid AI). Measured 15 Oct 2026 on Florian's instruction (DECISIONS 15 Oct 2026 16:53Z: measure d1-ultra now) through the unchanged full-set runner run_api_full_v161.py; the full-set exposure gate logged all 1,200 sealed items to provider `liquid` before dispatch, and none of this draw's items had been exposed to Liquid before (the v1.6.0 exposure of 2,705 items does not overlap). No paid order. 1,485 of 1,500 answered (HTTP 200: 1,485); 15 HTTP 422 refusals: in the API's own words those 15 prompts are "over the model's input limit of 32768 tokens ... or 250000 bytes of text", and they are scored as wrong answers in the full 1,500-item denominator (and count zero tokens). Two rate-limit stops (HTTP 429) during the run were resumed with a 2 s spacing between requests; the measurement report records that nothing was lost. Vendor-hosted api.liquid.ai/decisions/v1/systemone API, model `d1-ultra`, through the unchanged TypeSafe adapter; latency measured from Sandy (Germany) without API adjustment. Full S1200+P300 draw of v1.6-regular-20261012 through the unchanged run_api_full_v161.py; the full-set exposure gate logged all 1,200 sealed items to provider `liquid` before the first request (Florian GO 15 Oct 2026). Native probabilities on all three question types. 15 of 1,500 items exceed the model's 32,768-token input limit (HTTP 422) and are scored as failures. Liquid AI public price list, USD 0.042/M input, output free (fetched 16 Oct 2026): the models table of Liquid's public pricing page lists d1-ultra at USD 0.042 per 1M input tokens and USD 0.00 per 1M output tokens (saved copy sha256 89fb8ef2...); the same rate Liquid's API billed on the measurement's smoke call (48 input tokens -> USD 0.000002016). Counted as the manufacturer's standard launch list price under interpretation I-1 (the reading that admitted kushal-gemma4-31b-it-autoloops and SubQ Snap), through a scoped re-freeze of the frozen pricing module that adds this one key and nothing else, with a zero-difference proof for every other registry entry. ESTIMATE in the scorer's sense: the tariff x this row's OWN provider-reported tokens (638,436 input tokens over the 1,485 answered items, 0 output tokens), divided by the full 1,500-row basis the scorer uses; the 15 items refused with HTTP 422 count as zero tokens and as wrong answers. Not a bill and not a quote. Provider-reported usage: 638,436 input tokens over the 1,485 answered items and 0 output tokens; USD 0.017876208 per 1,000 decisions, 0.277x the official cost cap USD 0.064595, so the row is inside the official cost-capped views. Measured Intelligence 69.700, Calibration 91.254, Capability 80.477, Speed 89.000, Cost axis 62.432; composite A 76.105, B 74.732, C 76.105; on this draw rank 1 (A), 1 (B), 1 (C) and 3 by Capability, of 18 ranked rows. Latency on the official subset from Sandy (Germany), without API adjustment: p50 raw 0.2314 s, p95 raw 0.5442 s. Hosting implementation and deployed weights were not independently inspected. Raw sha256 f69bf80f48267017cd1fa506787850b81602ddfcea93a1451a45323b50ff045b; the scored copy is byte-identical.

v1.6.22 ADDS 4 ROWS (Messier One v0.4 (messier-one-v0.4), Nemotron Deciffusion 8B v2 (pst2154) (nemotron-deciffusion-8b-v2), Nev-2B (EryriLabs) (nev-2b), Trio-Spark v1.3 (MachineFi) (trio-spark-v1.3)) to the 22 full-draw rows of v1.6.21 on the same draw, under the same rule as the earlier same-draw additions: the field median stays the frozen v1.6.10 value, so every carried row keeps identical point scores, axes, capability, cost and speed objects, and the listed-not-ranked rows (reflex-instinct-0.6b, nimble-v4, nimble-v4-max, sage-1.4.0) and the unranked A2 measurement keep their wording. Two of the new rows are RANKED (Messier One v0.4 (messier-one-v0.4), Nev-2B (EryriLabs) (nev-2b)); two are LISTED BUT NOT RANKED because the frozen pricing path gives them no price (Nemotron Deciffusion 8B v2 (pst2154) (nemotron-deciffusion-8b-v2), Trio-Spark v1.3 (MachineFi) (trio-spark-v1.3)): they show Intelligence, Calibration, Capability and Speed only, no Cost, no Composite and no rank in any view. LONG ITEMS: 15 items of this draw have very long states. From the scored raws of this release, they are refused outright (all 15, scored as wrong answers) by 11 rows: attest-31b-v1.0, julia-1, liquid-d1-ultra, nev-2b, pjev-2b, purplemist-mini-1.0, respan-span-02, sage-1.4.0, standard_one_3b_sh, trio-spark-v1.3, uniphore-4b-decider; phocinae-largha-150m-v1 refuses 3 of them; every other row answers them under its own recipe (on a truncated or compacted state, or read whole), as the row notes say. What moved on carried rows, counted exactly. RANKS: amos-1-large A 15 -> 17; B 15 -> 16; C 15 -> 16, amos-1-medium A 11 -> 12; B 11 -> 12; C 11 -> 12, julia-1 A 18 -> 20; B 18 -> 20; C 18 -> 20; capability 18 -> 20, krino-2b A 13 -> 14; B 13 -> 14; C 13 -> 14; capability 16 -> 18, metask_jev_rain_31b_trained_v3 A 6 -> 7, phocinae-largha-150m-v1 A 17 -> 19; B 17 -> 19; C 17 -> 19; capability 17 -> 19, pjev-2b A 12 -> 13; B 12 -> 13; C 12 -> 13; capability 12 -> 13, purplemist-mini-1.0 A 16 -> 18; B 16 -> 18; C 16 -> 18; capability 15 -> 17, respan-span-02 A 8 -> 9; B 8 -> 9, standard_one_3b_sh A 10 -> 11; B 10 -> 11; C 10 -> 11; capability 14 -> 15, subq-snap-preview A 7 -> 8; B 7 -> 8, uniphore-4b-decider A 9 -> 10; B 9 -> 10; C 9 -> 10; capability 13 -> 14, vllm-sr-d3 A 14 -> 16; B 14 -> 15; C 14 -> 15. Each moved rank shifts only by the newly ranked rows above it. Rows listed but not ranked take no place in any order. CONFIDENCE INTERVALS: as in v1.6.17, v1.6.18 and v1.6.21, new keys sort into the key-sorted roster, and the scorer seeds each row's bootstrap with the shared seed 16 plus the row's position in that roster, so a carried row whose position changed gets a different interval while no point estimate moves. Carried rows whose intervals moved: metask_jev_rain_12b_trained, metask_jev_rain_31b_trained, metask_jev_rain_31b_trained_v3, nimble-v4, nimble-v4-max, phocinae-largha-150m-v1, pjev-2b, purplemist-mini-1.0, reflex-instinct-0.6b, respan-span-02, sage-1.4.0, standard_one_3b_sh, subq-snap-preview, torchcast-decision-4b-v1.1, uniphore-4b-decider, vllm-sr-d3. DIAGNOSTICS: the API-basis median diagnostic is 7.703968975298743 (previous 7.703968975298743); carried v16.raw_on_A moves: none. Equating offsets are I 0.0681 / C 1.5418 (previous I 0.1005 / C 1.4616); the equating pool changes from 14 to 17 members (messier-one-v0.4, nemotron-deciffusion-8b-v2, nev-2b joined). These diagnostics are not part of any score, rank or axis on this release: the hosted-API row is a full-set row and is not equated, and the carried A2 measurement keeps its own equating and is not rescored. reflex-instinct-0.6b stays LISTED BUT NOT RANKED under #18761 and the unranked A2 measurement of v1.6.14 is carried; neither is changed. CORRECTION to the v1.6.20 note: the refreshed-preview Telegram card #17515 on which Florian's v1.6.20 approval was recorded had been sent to him on 14 Oct 2026 at 14:59Z (CoS deputy #19679); the v1.6.20 note did not state that time.

Board effect: merged-live-board top-five comparison before/after v1.6.22 over the mixed, open-weights and API boards, composites A/B/C and Capability with official caps, no caps, cost off + latency 2x (Florian settings) and official cost cap + no latency cap: 0 of 21 top-five lists change. No row enters or leaves any top five. Best placement of the two new ranked rows on the merged board: messier-one-v0.4 #21 (open-weights board, composite A); nev-2b #71 (open-weights board, Capability, official cost cap + no latency cap). nemotron-deciffusion-8b-v2 and trio-spark-v1.3 are listed but not ranked and take no place in any ranking. Ranked rows: mixed 194 -> 196, open weights 162 -> 164, API 32 (unchanged).

Publication of v1.6.22: on Florian's GO of 16 Oct 2026 12:50Z, a direct message in the laptop chat ("I really want all of the models we have evaluated to be online (even if they land in #5) on both JevBench and ImageJevBench"; DECISIONS.md 2026-10-16 12:50 UTC). No top-five list changes (see the board-effect note), so no top-five preview card was sent and none is claimed; the GO arrived as a direct message and no Telegram button was pressed.

messier-one-v0.4: Messier One v0.4 (agentmessier-ai), a newer revision of the live messier-one-v0.2 row. Measured 14 Oct 2026 by the add-requests lane on the open draw under custody #19335 (one use), with the independent pre-score review before scoring. No paid order. 1,500 of 1,500 answered (HTTP 200: 1,500). LICENCE: weights CC BY-NC 4.0 (non-commercial; listing a measured score is evaluation use). Two readout facts, both the author's own and both documented by the author. (1) --noul-floor 0.801 is ON BY DEFAULT: a yes/no probability closer to 0.5 than the floor is reported at the floor, the decision never changes, and the author writes that this is because JevBench scores yes/no answers this way; the raw probability is not recoverable from a floored answer, so a separate floor-0 diagnostic pass over the 375 noul items only was run under custody #19341 and is reported as a sensitivity figure - it is NOT this row's score and never substitutes for it. (2) The author's Prompter TRUNCATES a state longer than 7,500 tokens to its beginning + '...[truncated]...' + its end: exactly 15 of the 1,500 items are affected, and they are the same 15 long items that other rows of this draw refuse outright, answer on truncated input or read whole (the rows that refuse them are listed in the v1.6.22 release note). Three different policies exist on this draw; each is the system's own recipe and is scored as such. An as-refused sensitivity figure (those 15 set invalid) is published next to this row's score. v0.4 also differs from the live v0.2 row in more than the floor: bidirectional attention, AA labels, the qboth layout, the gate and an 8,192-token window. Floor-0 sensitivity (custody #19341; a separate diagnostic pass over the 375 yes/no items with the floor off, substituted into this row offline): Capability 60.888 against the row's 62.444, Intelligence 48.282 against 52.025, yes/no Calibration 71.094 against 69.196: the floor is worth +1.56 Capability on this draw. It is a footnote only, never this row's score. As-refused sensitivity (those 15 long items scored as refusals): Capability 62.403 against the row's 62.444. SPEED: measured on one rented RTX A6000 48 GB, not the H100/RTX 5090 hardware most GPU rows of this draw used, so its Speed is not comparable to the live messier-one-v0.2 row. Evaluator-owned rented Lium GPU pod (measurement receipts on file), 1x NVIDIA RTX A6000 48 GB - different hardware from the H100/RTX 5090 rows of this draw and from the RTX 3090 the author quotes. Started by the author's OWN ./serve_vllm.sh MODEL_DIR 8080 with its defaults, which is what the author insists on for v0.4: vLLM 0.30.0, --max-model-len 8192, chunked prefill and prefix caching OFF (this revision is non-causal), --max-logprobs 256, processed_logprobs, front end --max-state 7500 --max-total 8150 --gate 0.5 --noul-floor 0.801; transformers 5.18.0 exactly as pinned. One request at a time from the unchanged runner. Isolation: the server ran inside a network namespace with loopback only (unshare -n), the cut proven before the sealed input was staged and re-proven immediately before the first sealed request, with the synthetic smoke gate passed in between; a network namespace replaces docker --network none because the pod carried no local image (custody #19335, same property, proven the same way). The pod host kept its network for ssh. ESTIMATE (*est.), base-model market reference through the frozen pricing_v15 module (sha256 dcfcecb0..., the module in force; its base-model references are unchanged since the dae86740... module this row was first priced with - the two later re-freezes each added one hosted-API launch-list key and nothing else): declared base Qwen/Qwen3.5-4B -> deepinfra:Qwen/Qwen3.5-4B USD 0.030000000000000002/M input, USD 0.15/M output, the same basis the live messier-one-v0.2 row carries. The author's server reports NO usage block of any kind, so the input tokens are counted OFFLINE with the author's own Prompter (prompt.py at tag v0.4) at the exact serving settings (--max-state 7500 --max-total 8150, AA labels, qboth layout) and cross-checked against vLLM's own prompt-token counters from the measured pass; output tokens are 0 (the engine is asked for one token restricted to the option labels and nothing is generated for the caller). The reference listing was deprecated after the 25 Sep 2026 cut-off and replaced by Qwen/Qwen3.5-9B; the frozen snapshot rates remain in use (I-3). Estimated, not charged, not a quote from the author or any host. Offline-counted input tokens (the author's server reports no usage): 1,105,885, matching vLLM's own prompt-token counter delta; 0 output tokens. USD 0.022117700 per 1,000 decisions, 0.342x the official cost cap USD 0.064595, so the row is inside the official cost-capped views. Measured Intelligence 52.025, Calibration 72.862, Capability 62.444, Speed 89.671, Cost axis 59.658; composite A 65.725, B 62.436, C 49.415; on this draw rank 6 (A), 7 (B), 9 (C) and 12 by Capability, of 20 ranked rows. Latency on the official 124-item subset: p50 raw 0.0664 s, p95 raw 0.1157 s; published with the standard self-hosted x2 + 0.15 s adjustment (assumption, not measured): p50 0.2829 s, p95 0.3813 s. Latency figures quoted in the endpoint condition are over all answered items. Raw sha256 c7a7841a102e676804cfbb9a12fca5b86c8a3845ff3990996f3d20a00ecf10cb; the scored copy (offline token counts injected) has sha256 d2a0c4f797b9e607aebf26b613920a0573844b537aa0ea4aa288d677295a80eb.

nemotron-deciffusion-8b-v2: Nemotron Deciffusion 8B v2 (pst2154), a follow-up of the live nemotron-diffusion-8b row. Measured 15 Oct 2026 by the add-requests lane on the open draw under custody #19428, with the independent pre-score review before dispatch. No paid order. 1,500 of 1,500 answered (HTTP 200: 1,500). LICENCE: NVIDIA Nemotron Open Model License. LONG ITEMS: it answers the 15 long items on about 10% of their state through its own BM25 compaction, where other rows of this draw refuse them outright (listed in the v1.6.22 release note). As-refused sensitivity (the 15 compacted items scored as refusals): Capability 68.851 against the row's 69.320, i.e. answering them on about a tenth of their state is worth 0.469 Capability points. UNPRICED: the frozen pricing path raises on its declared base nvidia/Nemotron-Labs-Diffusion-8B (no market-listing decision; question #19427 is open); no rate is invented and the predecessor row's carried per-decision price is not reused. Five facts travel with this row, four of them established by the independent pre-score review (PASS WITH FINDINGS, no P1), which ran the author's own compaction offline before anything was dispatched. (1) THE 15 LONG ITEMS ARE ANSWERED, NOT REFUSED, AND ON ABOUT A TENTH OF THEIR STATE. The server reduces any prompt over 8,192 tokens to the most relevant 8,192 tokens with BM25 over sentences (no model call, deterministic, verified byte-identical across two offline runs). On this draw exactly 15 items are affected: 78,830-84,436 raw tokens cut to 8,002-8,385, i.e. 9.5-10.6% of the state kept as 21-27 of 210-238 fixed 70-word chunks in their original order. The question and its options are rendered outside the state and are never touched. The response carries no flag that it happened, so the compacted items are identifiable only by their input_tokens (8,002-8,385 against a maximum of 1,923 for every other item). Other rows of this draw, nev-2b among them, refuse those same items outright (listed in the v1.6.22 release note), so those 15 cells are not like for like; an as-refused sensitivity is published next to this row. The author's own long-context evidence (BABILong, QuALITY) is prose question answering and covers nothing of this draw's numeric, log-like long states. (2) THE ROW IS UNPRICED, AND NOT BECAUSE OF ANYTHING THE AUTHOR DID. The frozen pricing module raises on the declared base nvidia/Nemotron-Labs-Diffusion-8B - that base has no market-listing decision in the frozen table and the dated snapshot carries no listing of the family - so no cost number can be formed without a decision that is not this measurement's to make. The row is therefore listed, measured and shown without a cost and without a rank, the pre-declared default; the question is on the record and the server reports both token fields, so a later pricing decision needs no re-measurement. The predecessor nemotron-diffusion-8b row's carried per-decision price belongs to a different draw and is deliberately not reused. (3) PRECISION AND LIMITS ARE THE AUTHOR'S OWN. BF16 (QUANTIZATION=none) is the author's documented switch and the precision of every headline number on the author's card; the container's default is FP8. MAX_MODEL_LEN=16384 is the value the author's own start.sh picks for a memory-constrained GPU, and the review proved it behaviour-neutral on this draw (prompt limits of 65,534 / 16,382 / 10,000 / 8,450 all produce byte-identical prompts). Nothing else was changed. The row ran from the image DIGEST, not the mutable tag, and the review verified that image layer by layer against vllm/vllm-openai:nightly-fe4df3df0eb7 plus exactly the four author layers of the public repository. (4) OUTPUT TOKENS ARE COUNTED DIFFERENTLY HERE. The server reports output_tokens equal to the number of scored decision positions (one per request for us) under output_tokens_basis "scored_decision_positions", with generated_text_tokens 0; it generates no text. Rows such as pjev-2b report 0 for the same physical behaviour. The difference is immaterial while the row is unpriced and must be restated if it is ever priced. (5) DECONTAMINATION. The author states that no benchmark test, validation or dev split was trained on, with a row-level licence and overlap check, and that every training row was checked against the public JevBench items; the review found nothing in the repository contradicting that, but notes that the public JevBench set was used as a model-selection gate and that the tasksource sub-sources are unaudited. The licence (NVIDIA Nemotron Open Model License) permits this evaluation. Evaluator-owned rented Lium GPU pod (United States; measurement receipts on file), 1x NVIDIA RTX A6000 48 GB - different hardware from the L40S and GB200 the author quotes and from the H100/RTX 5090 rows of this draw. Started from the author's OWN published container, by DIGEST ghcr.io/pst2154/nemotron-deciffusion@sha256:944c0af4967ebd1e461a3b1faa9d16db197288af24393b21c917617461f35276 (image config sha256:0a4bd2d039b5c2da9ff8b181232ee3714f6b38e31bd9a3100a29326068d6f802), in the author's own documented sandboxed form: docker run --gpus all --shm-size=8g --network none --read-only --tmpfs /tmp:rw,exec,size=16g --user 1000:1000 --cap-drop ALL --security-opt no-new-privileges -v <checkpoint>:/models/checkpoint:ro, with QUANTIZATION=none (BF16) and MAX_MODEL_LEN=16384 and every other default of the image (ATTENTION=noncausal, COMPACT_OVER=8192, COMPACT_BUDGET=8192, MAX_BATCHED_TOKENS=65536, --no-enable-prefix-caching, --max-logprobs 1052, --logprobs-mode processed_logits, vLLM nightly fe4df3df0eb7 with the author's overlay). /health reported back quantization none, attention noncausal, max_prompt_tokens 16382. All ten checkpoint files verified against the author's own SHA256SUMS (sha256sum -c, 10/10 OK) BEFORE the container started. One request at a time from the unchanged runner, which reached the server through the container's own network namespace with nsenter - the container published no port and had no network at all. The cut was proven before the sealed input was staged (only lo, no routes, a name probe and a bare-IP probe both failed) and re-proven immediately before the first sealed request, with a synthetic smoke gate passed in between (custody #19428). 1,500/1,500 answered, HTTP 200 on every item, raw p50 105 ms / p95 180 ms / max 1.82 s. unpriced: the frozen pricing path has no market-listing decision for the declared base nvidia/Nemotron-Labs-Diffusion-8B and raises rather than estimating; the deputy's answer to #19427 decides whether an entry is added UNPRICED. The frozen pricing_v15 module RAISES on the declared base nvidia/Nemotron-Labs-Diffusion-8B ('base model lacks an explicit market-listing decision') and the dated snapshot carries no listing of that family, so this row carries no pricing_base and is listed, measured and shown WITHOUT a cost number and WITHOUT a rank - the pre-declared default (Sage 1.4, Celeris Option A). No rate is invented. The predecessor nemotron-diffusion-8b row's usd_per_1000_override is a v1.5.4 historical carry on a different draw and is deliberately NOT reused. Asked of the deputy on board #19427; the server reports both token fields, so a later pricing decision needs no re-measurement. Measured Intelligence 49.600, Calibration 89.039, Capability 69.320 and Speed 87.704 only; NOT RANKED: no Cost, no Composite, no rank in any view, including the Capability order. Where to look: the collapsed "All data" table and the detail view. Provider-reported usage: 992,887 input tokens and 1,500 output tokens on the server's scored-decision-positions basis (no text generated). Latency on the official 124-item subset: p50 raw 0.1015 s, p95 raw 0.1654 s; published with the standard self-hosted x2 + 0.15 s adjustment (assumption, not measured): p50 0.3529 s, p95 0.4807 s. Latency figures quoted in the endpoint condition are over all answered items. Raw sha256 1a0953d441ab462cbdfad12537ba10a7e858331414843d04e5e035d6878d2c0f; scored copy sha256 b2d3d5047bb9fa49141d4ce9e724a93934508bf9f0760f1788c1345e242d2af7.

nev-2b: Nev-2B (EryriLabs), GGUF Q8_0. Measured 15 Oct 2026 by the add-requests lane on the open draw under custody #19428 (one use per weight set), with the independent pre-score review before dispatch. No paid order. 1,485 of 1,500 answered (HTTP 200: 1,485); 15 HTTP 502 context-overflow refusals (llama-server's own 400 exceed_context_size_error at the author's documented -c 8192), scored as wrong answers in the full 1,500-item denominator and counted as zero tokens, so the cost excludes those refused long prompts. ENGLISH-ONLY by the author's declaration; 23.3% of this draw (349 of 1,500 items) is not English. SPEED is Sandy's loaded shared CPU, not the model: not comparable to the GPU and API rows of this draw. Four facts travel with this row, three of them found or sharpened by the independent pre-score review (PASS WITH FINDINGS, no P1). (1) CONTEXT, not capability, costs this row 15 items: the author's layout cuts a state longer than 20,000 characters (nev.layout.MAX_CONTEXT_CHARS) and the author's card calls that "about 5,000 tokens", but this draw's 15 long items are dense, digit-heavy structured text at about 1.6 characters per token, so the cut still leaves 12,463-14,914 tokens and every one of them overflows the author's own documented -c 8192. llama-server answers HTTP 400 exceed_context_size_error - it does not silently truncate, which was verified on synthetic filler before any sealed item (measurement receipts on file) - and the shim relays it as HTTP 502. These are the same 15 items that other rows of this draw refuse outright, answer on truncated input (messier-one-v0.4 among them) or read whole (the rows that refuse them are listed in the v1.6.22 release note). Three policies exist on this draw; each is the system's own recipe. (2) THE READOUT IS CALIBRATED, and the calibration can move a decision. The per-file temperatures stored in the GGUF metadata (choice 0.9220, noul 0.9169, score 0.8460, verified against the repo's calibration_Q8_0.json with our own GGUF reader, byte-identical) and, for choice questions with exactly four options, a fitted letter-position prior of at most 2.2% spread, are both the author's own and are the route the author's published 0.810 public-item number was measured through. On choice the temperature can never change the winner and the prior can only flip near-ties; on yes/no a temperature below 1 sharpens, so a raw probability just inside JevBench's 0.2/0.8 abstention band can become a decision instead of an abstention - never the opposite decision; on score it moves the expected value toward the modal level in either direction. This is the same class as the disclosed --noul-floor 0.801 of h2o-lightning-4b and messier-one-v0.4, but a continuous calibration rather than a discontinuous floor, and it reaches only items within about 2% of the band edge. A no-calibration sensitivity is published next to the row; it is recoverable exactly from the returned probabilities and cost no further model call. (3) PROVENANCE. Nev is distilled from the full option distributions of Mapika/decider-4b v2 and crh225/Plumb-4B - models, not items - and both are rows on this board, so neither is independent evidence for this one. Its training mix lists "jev-bench/*" configs, which are Praveenrajus/jev-bench, a DIFFERENT benchmark from JevBench; the author holds out the public JevBench items by exact-state hash, and this draw's items are sealed, bespoke and never published (the review measured containment against the public items at mean 0.005, max 0.23, and custody #19428 agreed the risk is low). One training source, avbiswas/bev-decision-150K, carries an unknown licence on its own card. (4) THE AUTHOR DECLARES THE MODEL ENGLISH-ONLY and 23.3% of this draw (349 of 1,500 items) is not English; the multilingual cells are where this row should be read most carefully. The no-calibration sensitivity, computed offline from the same raw with no further model call, moves 15 of the 375 yes/no answers across JevBench's 0.2/0.8 abstention boundary and flips exactly one of the 750 choice answers - the near-tie the four-option letter prior can reach. It is a sensitivity and a footnote, never this row's score. No-calibration sensitivity (recomputed offline from the same raw, no further model call): Capability 50.811 against the row's 49.917. A footnote only, never this row's score. Sandy, the evaluator's own SHARED CPU host (AMD Ryzen 5 3600, 6 cores / 12 threads, Zen 2, AVX2, no AVX-512), NOT a dedicated machine and NOT a GPU: other jobs ran beside it throughout and the 1-minute load average was sampled every 60 s (measurement receipts on file) - over this row's window of 199 samples it ran 6.89 to 35.91, mean 13.06. The author's own two documented processes, unedited: llama-server -m nev-Q8_0.gguf -c 8192 --port 8080 --metrics (llama.cpp b11372, the one build the author names; --metrics is the only addition and changes no model behaviour), and the author's shim PYTHONPATH=python python -m nev.serve --backend llama-server:http://127.0.0.1:8080 --gguf nev-Q8_0.gguf on port 8090, with --backend-arg timeout=900 (the author's own documented flag, raised from the 300 s default because a loaded shared box can otherwise turn an answerable item into a false refusal). llama.cpp chose n_threads=6, its own default; the author passes none. One request at a time from the unchanged runner. Isolation: a user+network namespace (unshare -Urn, loopback only - Sandy permits no privileged unshare -n), and the author's two processes additionally inside bwrap with a cleared environment, a read-only root, tmpfs /home and /tmp and read-only binds of only the GGUF, the llama.cpp build, the venv, its interpreter and the author's own python/ tree, so the sealed item directory does not exist inside that sandbox; the runner stays outside it and the author's code never sees the file. All three cuts were PROVEN before the sealed input was read (only lo, no routes, a name probe and a bare-IP probe both failing, and an ls of the sealed tree failing inside the sandbox) and the network cut was re-proven immediately before the first sealed request, with a synthetic smoke gate passed in between (custody #19428). 1,485/1,500 answered, the 15 refusals all HTTP 502 relaying llama-server's own 400 exceed_context_size_error. Raw p50 7.02 s / p95 15.29 s / max 56.88 s - this is the shared box, not the model, and it is not comparable to the GPU and API rows of this draw. ESTIMATE (*est.), base-model market reference through the frozen pricing_v15 module (sha256 dcfcecb0..., the module in force; its base-model references are unchanged since the dae86740... module this row was first priced with - the two later re-freezes each added one hosted-API launch-list key and nothing else): declared base Qwen/Qwen3.5-2B-Base -> deepinfra:Qwen/Qwen3.5-2B USD 0.02/M input, USD 0.1/M output. The author's shim reports usage {calls, permutations, backend} and NO token fields at all, so the input tokens are counted OFFLINE with the author's own prompt code (nev.layout.single_prompts over hev.decider_layout.render_row) at the exact serving settings, and cross-checked against llama-server's own prompt-token counter delta from the measured pass; output tokens are 0, because one readout position per call is restricted to the option letters and nothing is returned as text (the pjev-2b convention and the 9 Oct CoS rule for native option-probability models). Estimated, not charged, and not a quote from the author. Offline-counted input tokens (the author's shim reports none): 685,652 over the 1,485 answered items, cross-checked against llama-server's own counter; 0 output tokens. USD 0.009142027 per 1,000 decisions, 0.142x the official cost cap USD 0.064595, so the row is inside the official cost-capped views. Measured Intelligence 20.232, Calibration 79.602, Capability 49.917, Speed 54.829, Cost axis 71.169; composite A 6.947, B 5.697, C 4.824; on this draw rank 15 (A), 17 (B), 17 (C) and 16 by Capability, of 20 ranked rows. Latency on the official 124-item subset: p50 raw 6.3431 s, p95 raw 12.7389 s; published with the standard self-hosted x2 + 0.15 s adjustment (assumption, not measured): p50 12.8362 s, p95 25.6278 s. Latency figures quoted in the endpoint condition are over all answered items. Raw sha256 76b58967b5133653a5530966338efde6c8b32f854fd66da707040dc2195df4f3; the scored copy (offline token counts injected) has sha256 3ca90aef11ed254956211d443887fb8cd0a3577f2bbf995f9667416dd5ccd22b.

trio-spark-v1.3: Trio-Spark v1.3 (MachineFi), hosted API. Measured 15 Oct 2026 by the add-requests lane under custody #19732 (one hosted-API use) and deputy #19740, with the submitter's own API key; the full-set exposure gate logged all 1,200 sealed items to provider `machinefi` before dispatch. No paid order. 1,398 of 1,500 answered (HTTP 200: 1,398); 102 HTTP 422 refusals, scored as wrong answers in the full 1,500-item denominator: 58 because the question has 9 options and Trio-Spark supports at most 8, 43 over MachineFi's own documented 1,024-token input cap, 1 "cannot be evaluated". Latency is raw from Sandy with no API adjustment. UNPRICED: no eligible tariff under the frozen pricing path. Vendor-hosted `platform.machinefi.com/v1/systemone` API, model `trio-spark-v1.3`; latency measured from Sandy (Germany) without API adjustment — the submitter explicitly asked for it to be timed as a hosted endpoint with the network included (over all 1,398 answered requests p50 1.346 s, p95 1.855 s wall; the Speed axis uses the official per-item latency subset; loadavg samples for the whole run are in the measurement receipts on file). Full S1200+P300 draw of `v1.6-regular-20261012` through the unchanged `run_api_full_v161.py` (sha256 `eceea17e…`) and the unchanged `jevbench.adapters.typesafe` (sha256 `780f8794…`); the full-set exposure gate logged all 1,200 sealed items to provider `machinefi` before the first request (custody #19732; this draw's sealed items were already past the two-provider retirement threshold, so the admission cost the reserve nothing). Native System One answer fields on all three question types, nothing generated — with one honesty note the independent review asked for (P2-3): MachineFi's public docs describe only `choice`, so `noul` and `score` are documented here by observation, not by their documentation. The adapter's `noul` → P(yes) orientation is not assumed either: on the 231 PUBLIC items this mapping scores 80.6 % (54 of 67 noul items) against 19.4 % if it were inverted, which settles the direction without touching a sealed item (`output_tokens` 0 on every answered row, 573,254 input tokens over the full set). Hosting implementation and deployed weights were not independently inspected; no weights or training code are published. Regular-queue request `bh-submit:216579c8` (ref BBAEFC3A), measured with the submitter's own API key. 102 of 1,500 requests returned HTTP 422 `request_refused`, for three reasons given in MachineFi's own error messages: 58 because the question has 9 options and Trio-Spark supports at most 8 ("Question decision has 9 options; Trio-Spark supports at most 8." - every 9-option item of this draw), 43 with "Input exceeds the supported token limit." (MachineFi's documented cap of 1,024 model input tokens; answered prompts reach at most 955 billed input tokens), and 1 with "The decision input cannot be evaluated." By type: 76 choice, 17 score, 9 noul. The runner never re-sends a failed item and no request was truncated or shortened, so all 102 are scored as wrong in the full 1,500 denominator. No further requests failed for other reasons. The refusal count was pre-declared at 27–193 before the run, expecting token-limit refusals only; the 8-option limit was not foreseen there, and the add-requests hand-over attributed all 102 to the token cap, which the raw's own error messages correct. The pre-data text is §4 of the pre-registration at sha256 `e4340cdb…`, published on the agent board at 22:45Z and 22:55Z — before the dispatch began at 23:03:30Z — and preserved byte-exactly in the measurement receipts on file; the file itself was amended twice afterwards and now hashes `2fbc0ceb…`. Measured, but the frozen pricing path gives it no eligible price: MachineFi publishes a usage tariff for Trio-Spark (USD 0.042 per 1M billed input tokens, output not billed), yet `trio-spark-v1.3` is in neither frozen tariff set (`AGE_QUALIFIED_API`, `LAUNCH_LIST_PRICE_API`) and the system declares no base model and releases no weights, so there is no base-model market reference either — the frozen module (unchanged on this point since the 32117d75... module it was first checked against) returns "no eligible 30-day list price or base-model estimate" (verified by executing it; measurement receipts on file). Without a cost axis there is no composite, so the row shows Intelligence, Calibration and Capability and is not ranked, the same outcome as `sage-1.4.0` and as `subq-snap-preview` before CoS deputy decision #19174. The pricing question is open and can be decided in a later release without re-measuring anything. UNPRICED under the frozen pricing_v15 path (sha256 dcfcecb06525ce4a5ece37400ea261b97d2fe5d41155f3cd02b03cac86572835, the module in force since v1.6.21; also under its predecessor 32117d754104b3ead8bebdc9da5f8e0116a7550f4316cfc6874fbe6234c2d72b, against which it was first checked): MachineFi publishes a usage tariff for Trio-Spark of USD 0.042 per 1M billed input tokens with no output charge (docs/visual.md and the README of machinefi/trio-spark), but `trio-spark-v1.3` is in neither AGE_QUALIFIED_API nor LAUNCH_LIST_PRICE_API, and the system declares no base model and releases no weights, so there is no base-model market reference to fall back on. The frozen path therefore returns no eligible price (the same outcome as sage-1.4.0, and as subq-snap-preview before CoS deputy #19174). Measured Intelligence 28.409, Calibration 85.643, Capability 57.026 and Speed 76.467 only; NOT RANKED: no Cost, no Composite, no rank in any view, including the Capability order. Where to look: the collapsed "All data" table and the detail view. Provider-reported usage: 573,254 input tokens over the 1,398 answered items and 0 output tokens. Latency on the official 124-item subset: p50 raw 1.2838 s, p95 raw 1.7570 s, without API adjustment. Latency figures quoted in the endpoint condition are over all answered items. Hosting implementation and deployed weights were not independently inspected. Raw sha256 19cdb9cf78bac0f72b96e4f6af0ae3c76d392b5b959870b83b5ed132238244bf; scored copy sha256 23db012ec50f2876526d8f52225585c0b2b49fb2cbb6ebbc5c13ddfdfbe844c9.