Check what changed in the question, wording or readers before comparing the numbers.
This view keeps both results separate. It does not calculate a combined score or decide whether they reproduce each other.
Find experiments by proposal
What differs in the declared methods?
These are literal recorded values, not a compatibility test. Matching declarations do not prove equivalent inputs or fair scoring. A missing structured field may be described elsewhere in the immutable specification.
What was measured · Same recorded value
First result
token_delta
Second result
token_delta
English comparison declarations · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Tested population · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Unit tested · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Named instruments (including order) · Same recorded value
First result
[
"cl100k_base",
"o200k_base",
"p50k_base"
]
Second result
[
"cl100k_base",
"o200k_base",
"p50k_base"
]
Reader exposure · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Exposure window · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
How results combine · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Scoring declaration · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Conditions (including order) · Not recorded on either side
Not yet counting in evidence decisions. This row remains available for assessment, but does not currently carry a counting evidence result.
What was measured
token cost · token_delta How does the wording change tokenizer units for the declared tokenizer population?
Reported result
-6.333 tokens per declared item Reported interval: -8.333 to -6.333.
Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
English comparison
English comparison not recorded as a structured label
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_base, p50k_base
Reader 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
Disputed
Eligible replications disagree and this original does not hold a settlement majority.
Is this result within the cost allowance?
This headline is within the allowance.
The reported difference is -6.333 tokens; the current declaration allows at most 3 tokens.
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?
Disputed.
Eligible replications disagree and this original does not hold 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 6 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
In every region considered separately, checkout success increased; the same result held in each of the named regions.
After the observations from all the named regions were pooled together, checkout success increased, though this says nothing about any single region on its own.
In each model family on its own, the error rate stayed below two percent, evaluated separately for every family.
Ainglish input
each-group(model-families@eval-v4): error rate is below 2%.
Input 4
English input
Once all the age bands were combined into a single aggregate, treatment recovery exceeded the threshold, with no claim about any one band.
Ainglish input
groups-combined(age-bands@trial-v2): treatment recovery exceeded the threshold.
Input 5
English input
In every department considered individually, the budget was spent; the result held separately within each department.
Ainglish input
each-group(departments@2026): the budget was spent.
Input 6
English input
When the two data centers were treated as one combined pool, total uptime met the target, without implying either center met it alone.
Ainglish input
groups-combined(centers@prod): uptime met the target.
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.
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
-5 tokens per declared item Reported interval: -7.6666666666667 to -5.
Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
English comparison
English comparison not recorded as a structured label
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_base, p50k_base
Reader 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
Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
Is this result within the cost allowance?
This headline is within the allowance.
The reported difference is -5 tokens; the current declaration allows at most 3 tokens.
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?
Disagrees with the named original.
This replication reports -5 tokens; the named original reported -6.333.
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
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.
This result checks a named original, not every experiment on the proposal.Read its target original
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 6 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
In every warehouse considered separately, dispatch accuracy improved; the same result held in each of the named warehouses.
After the readings from all the named sensors were pooled together, mean drift stayed within tolerance, though this says nothing about any single sensor.
Ainglish input
groups-combined(sensors@cal-v9): mean drift stayed within tolerance.
Input 3
English input
In each shift on its own, handoff completeness exceeded ninety percent, evaluated separately for every shift.
When the three checkout lanes were treated as one combined pool, total throughput met the target, without implying anything about a single lane.
Ainglish input
groups-combined(lanes@store-14): total throughput met the target.
Recorded input digest: cb9d7469e53101651dc4280fc3607b7e919adee9acf47886e6a1b4710dcfea49
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.
Different wording, readers, exposure or populations can legitimately produce different results. A visible reference is not training the model’s weights. Current models and tokenizers have learned English; future Ainglish-trained performance remains a research question.
