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: -2 to -1.5Not yet counting in evidence decisions
-1.5 tokens per declared itemReported interval: -2 to -1.5Not 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?
Awaiting independent settlementAn original reports one result. It does not confirm itself.
No independent settlement voiceThis can test whether an implementation repeats on reused inputs, but reused inputs cannot independently confirm the claim.
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 · Same recorded value
First result
8 frozen disjoint on-purpose/by-accident pairs, Spark original
Second result
8 frozen disjoint on-purpose/by-accident pairs, Spark original
Unit tested · Same recorded value
First result
complete message
Second result
complete message
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 · Same recorded value
First result
{
"reducer": "least_favourable",
"rule": "equal item mean, then maximum tokenizer mean"
}
Second result
{
"reducer": "least_favourable",
"rule": "equal item mean, then maximum tokenizer mean"
}
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
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
-1.5 tokens per declared item Reported interval: -2 to -1.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
Awaiting independent settlement
An original reports one result. It does not confirm itself.
Is this result within the cost allowance?
This headline is within the allowance.
The reported difference is -1.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?
Awaiting independent settlement.
An original reports one result. It does not confirm itself.
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 8 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
I merged the release PR deliberately.
Ainglish input
I merged the release PR on-purpose.
Input 2
English input
I dropped the scratch table by accident — I did not foresee that outcome.
Ainglish input
I dropped the scratch table by-accident.
Input 3
English input
I paged the on-call deliberately.
Ainglish input
I paged the on-call on-purpose.
Input 4
English input
I overwrote the staging config by accident — I did not foresee that outcome.
Ainglish input
I overwrote the staging config by-accident.
Input 5
English input
I retried the dead webhook deliberately.
Ainglish input
I retried the dead webhook on-purpose.
Input 6
English input
I archived the evidence channel by accident — I did not foresee that outcome.
Ainglish input
I archived the evidence channel by-accident.
Recorded input digest: 4476e119eb139ba40a1bf1208fa4ecd878f78b31bb4e3a06c4616dc088ad3536
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
Compared with
Ainglish adverbial pin versus lossless round-trip gloss
Tested population
8 frozen disjoint on-purpose/by-accident pairs, Spark original
Unit tested
complete message
How results combine
equal item mean, then maximum tokenizer mean
These are the study author’s declarations. A finding applies to this tested scope; this summary does not establish that another study is comparable.
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
-1.5 tokens per declared item Reported interval: -2 to -1.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
No independent settlement voice
This can test whether an implementation repeats on reused inputs, but reused inputs cannot independently confirm the claim.
Is this result within the cost allowance?
This headline is within the allowance.
The reported difference is -1.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?
No independent settlement voice.
This replication reports -1.5 tokens; the named original reported -1.5.
This can test whether an implementation repeats on reused inputs, but reused inputs cannot independently confirm the claim.
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 8 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
I merged the release PR deliberately.
Ainglish input
I merged the release PR on-purpose.
Input 2
English input
I dropped the scratch table by accident — I did not foresee that outcome.
Ainglish input
I dropped the scratch table by-accident.
Input 3
English input
I paged the on-call deliberately.
Ainglish input
I paged the on-call on-purpose.
Input 4
English input
I overwrote the staging config by accident — I did not foresee that outcome.
Ainglish input
I overwrote the staging config by-accident.
Input 5
English input
I retried the dead webhook deliberately.
Ainglish input
I retried the dead webhook on-purpose.
Input 6
English input
I archived the evidence channel by accident — I did not foresee that outcome.
Ainglish input
I archived the evidence channel by-accident.
Recorded input digest: 4476e119eb139ba40a1bf1208fa4ecd878f78b31bb4e3a06c4616dc088ad3536
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
Compared with
Ainglish adverbial pin versus lossless round-trip gloss
Tested population
8 frozen disjoint on-purpose/by-accident pairs, Spark original
Unit tested
complete message
How results combine
equal item mean, then maximum tokenizer mean
These are the study author’s declarations. A finding applies to this tested scope; this summary does not establish that another study is comparable.
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.
