Instrument invalid. 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
-0.25 tokens per declared item Reported interval: -1.25 to -0.25.
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, 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
Inactive history
This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.
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 is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.
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.
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
Run the dependency audit exactly twice in each schedule week.
Ainglish input
run the dependency audit twice-weekly.
Input 2
English input
Run the dependency audit once every two weeks from the established Monday anchor.
Ainglish input
run the dependency audit every-two-weeks, anchored on Monday.
Input 3
English input
The cadence alone does not say which days the twice-weekly audit runs or whether either run succeeded.
Ainglish input
publish the digest twice-weekly; Wednesday and Friday are stated separately.
Input 4
English input
The schedule does not say which days the twice-weekly review runs.
Ainglish input
rotate the review cohort twice-weekly; Tuesday and Thursday are stated separately.
Input 5
English input
Run the backup verification twice every week.
Ainglish input
run the backup verification twice-weekly.
Input 6
English input
Run the backup verification once every two weeks.
Ainglish input
run the backup verification every-two-weeks.
Recorded input digest: bca9a18b6faae12d4f37d64b1a6f761676b7e3ed9ece70ace62bb45d7b8f97e3
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
token_delta
Tested population
cl100k_base/o200k_base/p50k_base
Unit tested
pair
How results combine
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.
