token costHow does the wording change tokenizer units for the declared tokenizer population?
token costHow does the wording change tokenizer units for the declared tokenizer population?
What was the result?
-1.5 tokens per declared itemReported interval: -1.5 to -1.5Retracted by submitter
-6.625 tokens per declared itemReported interval: -6.625 to -6.625Not yet counting in evidence decisions
Compared with what?
English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehension
English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehension
Independently settled?
Inactive historyThis row remains citable but has no current evidence effect.
Target no longer carries evidenceThe target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
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"
]
Second result
[
"cl100k_base",
"o200k_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
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
First result: full recordtoken cost · -1.5 tokens per declared item
Retracted by submitter. This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.
What was measured
token cost · token_delta How does the wording change tokenizer units for the declared tokenizer population?
Historical reported result
-1.5 tokens per declared item Reported interval: -1.5 to -1.5.
This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.
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
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
Inactive history
This row remains citable but has no current evidence effect.
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?
Inactive history.
This row remains citable but has no current evidence effect.
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. This historical row does not count.
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.
No readable study input pairs are stored inline in this receipt. This does not mean the experiment used none.
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.
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.625 tokens per declared item Reported interval: -6.625 to -6.625.
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
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
Target no longer carries evidence
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
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?
Target no longer carries evidence.
This replication reports -6.625 tokens; the named original reported -1.5.
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
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
Complete-pair freshness is not available for this receipt.
Separate-arm overlap is unavailable or has not been computed. This does not mean zero reuse.
Exact text comparisons only; repeated occurrences count separately. Shared text can deserve scrutiny even when each complete pair is new. These arm counts are descriptive and do not change settlement eligibility.
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 32 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
batch numbers from 12 to 48, including both 12 and 48
Ainglish input
batch numbers 12 to 48, include-both
Input 2
English input
release dates from Tuesday to Saturday, including both Tuesday and Saturday
Ainglish input
release dates Tuesday to Saturday, include-both
Input 3
English input
supported versions from 3.2 to 5.0, including both 3.2 and 5.0
Ainglish input
supported versions 3.2 to 5.0, include-both
Input 4
English input
temperature readings from -8 to 14, including both -8 and 14
Ainglish input
temperature readings -8 to 14, include-both
Input 5
English input
network ports from 4100 to 4199, including both 4100 and 4199
Ainglish input
network ports 4100 to 4199, include-both
Input 6
English input
priority ranks from 20 to 4, including both 20 and 4
Ainglish input
priority ranks 20 to 4, include-both
Recorded input digest: 4fc4eb85fb6b886ebfa6faa8589963fdb8ca30aff9822078cc10fe6fb094556c
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.
