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
64 prospective authored pairs: eight operational domains (service, manufacturing, education, transit, retail, energy, evaluation, operations), four fresh claims per domain crossed with both forms; exact tiktoken 0.14.0 cl100k_base/o200k_base/p50k_base roster
Second result
64 prospective authored pairs: eight operational domains (service, manufacturing, education, transit, retail, energy, evaluation, operations), four fresh claims per domain crossed with both forms; exact tiktoken 0.14.0 cl100k_base/o200k_base/p50k_base roster
Unit tested · Same recorded value
First result
one complete assertion including its verbatim group reference
Second result
one complete assertion including its verbatim group reference
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": "maximum tokenizer mean over 64 equally weighted complete pairs; retain two equally weighted 32-pair form strata and all tokenizer means; domain summaries descriptive only"
}
Second result
{
"reducer": "least_favourable",
"rule": "maximum tokenizer mean over 64 equally weighted complete pairs; retain two equally weighted 32-pair form strata and all tokenizer means; domain summaries descriptive only"
}
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) · Same recorded value
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
0.75 tokens per declared item Reported interval: -1.25 to 0.75.
More 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
Separate outcomes retained for all 2 declared conditions
each-group, groups-combined
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 0.75 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.
Does the overall result hide differences between conditions?
Every stored condition, without new pooling. Differences and intervals use tokens. Condition names come from the frozen experiment.
Condition
Reported difference
Reported interval
each-group
0.75
Not recorded
groups-combined
0.75
Not recorded
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
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 64 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.
For all groups in queues-larch-v7 combined, the completion share increased.
Ainglish input
groups-combined(queues-larch-v7): the completion share increased.
Condition
groups-combined
Recorded input digest: 5f90a277b56033a87bb8caaaabfb687143f004743e11f969d54c4492c2ddb185
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
each-group(REF): CLAUSE versus In every group in REF, CLAUSE; groups-combined(REF): CLAUSE versus For all groups in REF combined, CLAUSE
Tested population
64 prospective authored pairs: eight operational domains (service, manufacturing, education, transit, retail, energy, evaluation, operations), four fresh claims per domain crossed with both forms; exact tiktoken 0.14.0 cl100k_base/o200k_base/p50k_base roster
Unit tested
one complete assertion including its verbatim group reference
How results combine
maximum tokenizer mean over 64 equally weighted complete pairs; retain two equally weighted 32-pair form strata and all tokenizer means; domain summaries descriptive only
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.
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
0.875 tokens per declared item Reported interval: -0.625 to 0.875.
More 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
Separate outcomes retained for all 2 declared conditions
each-group, groups-combined
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 0.875 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 0.875 tokens; the named original reported 0.75.
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
Every declared condition must agree. Overlapping overall intervals alone do not confirm this original.
How much input text was reused?
100.0% of complete English–Ainglish pairs are fresh.
0 of 64 English inputs reuse text from either side of the original.
0 of 64 Ainglish inputs reuse text from either side of the original.
Declared item-bank digests: different. This compares bank identity, not shared sentences; different bank digests can still contain identical pairs.
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.
Does the overall result hide differences between conditions?
Every stored condition, without new pooling. Differences and intervals use tokens. Condition names come from the frozen experiment.
Condition
Reported difference
Reported interval
each-group
0.875
Not recorded
groups-combined
0.875
Not recorded
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
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 64 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.
For all groups in endpoints-juniper-v11 combined, the successful-request share increased.
Ainglish input
groups-combined(endpoints-juniper-v11): the successful-request share increased.
Condition
groups-combined
Recorded input digest: 8680875135f71748a93bd3bdf5c52b4989a5d9c889cce6120d4ddc3db7e8e00a
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
each-group(REF): CLAUSE versus In every group in REF, CLAUSE; groups-combined(REF): CLAUSE versus For all groups in REF combined, CLAUSE
Tested population
64 prospective authored pairs: eight operational domains (service, manufacturing, education, transit, retail, energy, evaluation, operations), four fresh claims per domain crossed with both forms; exact tiktoken 0.14.0 cl100k_base/o200k_base/p50k_base roster
Unit tested
one complete assertion including its verbatim group reference
How results combine
maximum tokenizer mean over 64 equally weighted complete pairs; retain two equally weighted 32-pair form strata and all tokenizer means; domain summaries descriptive only
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.