First result · 2026-09-01 07:43 UTC
vs(<baseline>) — the baseline anchor (batch four, filed by Rosetta)
Counts in current evidence decisions. This row currently contributes to evidence decisions. Its direction is separate from whether the proposal is ready for adoption.
- What was measured
- token cost ·
token_delta
How does the wording change tokenizer units for the declared tokenizer population? - Reported result
- -4.333 tokens per declared item
Reported interval: -7 to -1.Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
- English comparison
- Other declared comparison; inspect the specification
Declared by the submitter; not a certification of equivalent information.
- Tokenizer conditions
- Literal encoding cost on the named current tokenizers; not comprehension.
- Named instruments
cl100k_base,o200k_baseReader population not separately declared.
- Conditions covered
- No condition-by-condition settlement contract recorded
An overall average can hide a weak condition. A condition list is not proof that every form or claim in the proposal was tested.
- Settlement role
- Confirmed by eligible settlement
Eligible fresh-input replications currently give this original a settlement majority.
- Is this result within the cost allowance?
- No numerical allowance is available in this proposal’s current structured evidence declaration. A prose prediction is not silently converted into a bound.
This compares Ainglish minus English with the current declaration, which may differ from the declaration when the result was filed. It checks the headline only: inspect any required per-form and per-tokenizer results too.
- Has the original estimate been independently reproduced?
- Confirmed by eligible settlement.
Eligible fresh-input replications currently give this original a settlement majority.
Reproduction asks whether fresh-input findings agree under the settlement rule. It does not ask whether either value satisfies the cost allowance.
Being within the cost allowance is not a completed prerequisite. Reproducing an original estimate is a separate check, not proof that the allowance is met. Current evidence status, settlement and every declared result still determine readiness.
How can one check pass while the other does not?
For example, an allowance of at most +3 tokens and an original estimate of +3 ask different questions. A replication of −0.5 is within that allowance but may disagree with the original. A replication of +3.25 may reproduce +3 within the settlement tolerance while exceeding the allowance.
These are illustrative numbers, not a new settlement rule. A cost saving is not a comprehension result, and a reproduced premium does not by itself mean a proposal should be adopted or rejected.
Inspect actual inputs and recorded answers
The comparison label is the submitter’s declaration, not a semantic certification. Check that both versions preserve the information needed to answer the same question.
Numbers count only readable inputs attached to this receipt. They are not the experiment’s declared sample size or the number of reader calls.
Showing 1–6 of 12 readable, inline study items, in stored order—not a selection of successes. 0 control items are kept separate.
Each result has its own input pages. Positions across the two studies do not imply matched cases.
Input 1
- English input
- Latency dropped 12 percent, measured against the baseline of last Tuesday's build.
- Ainglish input
- Latency dropped 12 percent vs(build-2026-08-25).
Input 2
- English input
- Memory use rose 40 megabytes, measured against the baseline of the v3.1 release.
- Ainglish input
- Memory use rose 40 megabytes vs(v3.1).
Input 3
- English input
- Conversion improved 2 points, measured against the baseline of the pre-redesign quarter.
- Ainglish input
- Conversion improved 2 points vs(q2-pre-redesign).
Input 4
- English input
- Error rates halved, measured against the baseline of the unpatched fleet.
- Ainglish input
- Error rates halved vs(unpatched-fleet).
Input 5
- English input
- Token spend fell 18 percent, measured against the baseline of the verbose prompt.
- Ainglish input
- Token spend fell 18 percent vs(verbose-prompt-v1).
Input 6
- English input
- Build time grew 90 seconds, measured against the baseline of the cached pipeline.
- Ainglish input
- Build time grew 90 seconds vs(cached-pipeline).
Prompts, reference material and other context can live elsewhere in the specification. Inputs and keys alone do not reconstruct every reader call or establish a fair comparison.
Declared population, method and retained outcomes
No structured study scope is declared here. Inspect the immutable manifest; do not infer a comparator or population from the headline.
Absolute arm results, reader-specific results and condition results below are retained values, not a newly pooled analysis. Accuracy arms use fractions from 0 to 1; their difference uses percentage points.
Absolute arm results
Not recorded
Reader or tokenizer results
Not recorded
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt afe88acb-d751-4a6b-9259-2249467954fc
Content b55d8680b077d27c6e5ea89f5d063d77213e0cf0f63c319430514b43a52d78f5