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
cl100k_base/o200k_base/p50k_base
Second result
cl100k_base/o200k_base/p50k_base
Unit tested · Same recorded value
First result
pair
Second result
pair
Named instruments (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
1.125 tokens per declared item Reported interval: 0.5 to 1.125.
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
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 1.125 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 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 deleted the stale release branch deliberately; the tags survive.
Ainglish input
I deleted the stale release branch on-purpose; the tags survive.
Input 2
English input
The rebase deleted the release branch, which I had not foreseen — restoring it from the reflog.
Ainglish input
The rebase deleted the release branch by-accident — restoring it from the reflog.
Input 3
English input
The migration was skipped deliberately: it needs the maintenance window.
Ainglish input
The migration was skipped on-purpose: it needs the maintenance window.
Input 4
English input
Handover: the cache was cleared by mistake during the test run, unforeseen; expect a cold start.
Ainglish input
Handover: the cache was cleared by-accident during the test run; expect a cold start.
Input 5
English input
I deployed the hotfix deliberately; the rollback plan is documented.
Ainglish input
I deployed the hotfix on-purpose; the rollback plan is documented.
Input 6
English input
The script deleted the production database by mistake; recovering from snapshot.
Ainglish input
The script deleted the production database by-accident; recovering from snapshot.
Recorded input digest: 0b11ee2289d74c77826ee552c7fce3b4be1a47cd96a6c29c50da2d0456e29b59
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.
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: -1.5 to -0.875.
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 -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 1.125.
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 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 · quarantine-candidate
English input
I quarantined the unstable release candidate deliberately; the signed build remains available.
Ainglish input
I quarantined the unstable release candidate on-purpose; the signed build remains available.
Input 2 · reset-allowlist
English input
The migration reset the service allowlist, which I had not foreseen — restoring it from the audited export.
Ainglish input
The migration reset the service allowlist by-accident — restoring it from the audited export.
Input 3 · archive-audit
English input
The operator archived the rotated audit log deliberately: its retention period had ended.
Ainglish input
The operator archived the rotated audit log on-purpose: its retention period had ended.
Input 4 · overwrite-route
English input
Handover: the routing table was overwritten by mistake during recovery, unforeseen; the standby copy is loading.
Ainglish input
Handover: the routing table was overwritten by-accident during recovery; the standby copy is loading.
Input 5 · revoke-token
English input
We revoked the stale deployment token deliberately; the replacement credential is active.
Ainglish input
We revoked the stale deployment token on-purpose; the replacement credential is active.
Input 6 · close-incident
English input
The dashboard closed the active incident by mistake, an outcome its operator did not foresee; reopening it from the event log.
Ainglish input
The dashboard closed the active incident by-accident; reopening it from the event log.
Recorded input digest: df56ac8cb581382311e66d3b859baa6bdfe280c9ea9f46a4f16cd39dedc84358
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.
