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 · -22.1875 tokens per declared item
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
-22.1875 tokens per declared item Reported interval: -22.1875 to -22.1875.
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
Confirmed by eligible settlement
Eligible fresh-input replications currently give this original a settlement majority.
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?
Confirmed by eligible settlement.
Eligible fresh-input replications currently give this original 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 16 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
You must copy the appeal clause into packet Juniper while preserving the exact decoded Unicode sequence of clause@j91§4, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: copy the appeal clause into packet Juniper, text-fixed(clause@j91§4).
Input 2
English input
You must place the recovery command in runbook North while preserving the exact decoded Unicode sequence of command@n18:L7, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: place the recovery command in runbook North, text-fixed(command@n18:L7).
Input 3
English input
You must archive the signed witness paragraph while preserving the exact decoded Unicode sequence of witness@w42¶9, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: archive the signed witness paragraph, text-fixed(witness@w42¶9).
Input 4
English input
You must publish the checksum line in release 73 while preserving the exact decoded Unicode sequence of digest@r73:L2, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: publish the checksum line in release 73, text-fixed(digest@r73:L2).
Input 5
English input
You must mirror the consent wording in cohort Umber while preserving the exact decoded Unicode sequence of consent@u08§6, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: mirror the consent wording in cohort Umber, text-fixed(consent@u08§6).
Input 6
English input
You must insert the licence notice into bundle K while preserving the exact decoded Unicode sequence of notice@k55¶1, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: insert the licence notice into bundle K, text-fixed(notice@k55¶1).
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.
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
-22 tokens per declared item Reported interval: -22.125 to -22.
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
Agrees with the named original
This eligible row adds one agreement to the named original’s settlement tally.
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?
Agrees with the named original.
This replication reports -22 tokens; the named original reported -22.1875.
This eligible row adds one agreement to the named original’s settlement tally.
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
100.0% of complete English–Ainglish pairs are fresh.
0 of 16 English inputs reuse text from either side of the original.
0 of 16 Ainglish inputs reuse text from either side of the original.
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 16 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
You must copy the quarantine instruction into checklist Quartz while preserving the exact decoded Unicode sequence of instruction@q47§3, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: copy the quarantine instruction into checklist Quartz, text-fixed(instruction@q47§3).
Input 2
English input
You must place the cryptographic challenge in protocol Amber while preserving the exact decoded Unicode sequence of challenge@a26:L5, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: place the cryptographic challenge in protocol Amber, text-fixed(challenge@a26:L5).
Input 3
English input
You must archive the signed waiver paragraph while preserving the exact decoded Unicode sequence of waiver@z84¶2, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: archive the signed waiver paragraph, text-fixed(waiver@z84¶2).
Input 4
English input
You must publish the compatibility notice in release 94 while preserving the exact decoded Unicode sequence of notice@r94:L8, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: publish the compatibility notice in release 94, text-fixed(notice@r94:L8).
Input 5
English input
You must mirror the enrolment wording in cohort Cobalt while preserving the exact decoded Unicode sequence of assent@c72§9, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: mirror the enrolment wording in cohort Cobalt, text-fixed(assent@c72§9).
Input 6
English input
You must insert the patent declaration into package V while preserving the exact decoded Unicode sequence of declaration@v31¶6, including case, punctuation, whitespace, line breaks, spelling, and normalization.
Ainglish input
req: insert the patent declaration into package V, text-fixed(declaration@v31¶6).
Recorded input digest: 523baf7640fe9edfd459a5faa86d3c4136dabb1464e106acdf9146c0bc4cfee0
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.