Evidence

Compare two experiments

Check what changed in the question, wording or readers before comparing the numbers.

This view keeps both results separate. It does not calculate a combined score or decide whether they reproduce each other.

Change the selected experimentsSearch by proposal, select a result or enter an exact identifier

Find experiments by proposal

Choose two experiments by title, measurement and date. The choices include up to 50 newest public completed results, plus your current selections. Historical results stay labelled. For older records, use the evidence explorer or exact entry below.

Use an exact experiment identifier instead

A full attempt UUID entered here replaces the corresponding choice above. Content hashes are not result identifiers.

Clear comparison

Compare the essentials

Read each question across both results. A matching description is not proof that the studies are scientifically comparable.

Question	First result	Second result
Which proposal?	each-group / groups-combined — did the result hold in every group, or only after pooling them?2026-08-29 07:50 UTC	each-group / groups-combined — did the result hold in every group, or only after pooling them?2026-08-31 20:09 UTC
What was measured?	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?	-2.6875 tokens per declared itemReported interval: -4.625 to -2.6875Retracted by submitter	2 tokens per declared itemReported interval: 2 to 2Result invalid
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?	Inactive historyThis row remains citable but has no current evidence effect.	Inactive historyThis is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

Inspect first result Inspect second result

What differs in the declared methods?

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) · Recorded values differ

First result

[
    "tiktoken/cl100k_base",
    "tiktoken/o200k_base",
    "tiktoken/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 · 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 · -2.6875 tokens per declared item

First result · 2026-08-29 07:50 UTC

each-group / groups-combined — did the result hold in every group, or only after pooling them?

Retracted by submitter. 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: -2.6875 tokens per declared item
Reported interval: -4.625 to -2.6875.
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: tiktoken/cl100k_base, tiktoken/o200k_base, tiktoken/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 row remains citable but has no current evidence effect.

Is this result within the cost allowance?

This headline is within the allowance. The reported difference is -2.6875 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?

Inactive history.

This row remains citable but has no current evidence effect.

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 32 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: In every group in regions@2026Q3, considered separately, checkout success increased.
Ainglish input: each-group(regions@2026Q3): checkout success increased.

Input 2

English input: In every group in model-families@eval-v4, considered separately, error rate stayed below 2%.
Ainglish input: each-group(model-families@eval-v4): error rate stayed below 2%.

Input 3

English input: In every group in age-bands@trial-v2, considered separately, treatment recovery exceeded control.
Ainglish input: each-group(age-bands@trial-v2): treatment recovery exceeded control.

Input 4

English input: In every group in data-centres@week-35, considered separately, p95 latency decreased.
Ainglish input: each-group(data-centres@week-35): p95 latency decreased.

Input 5

English input: In every group in review-teams@release-14, considered separately, defect escape rate fell.
Ainglish input: each-group(review-teams@release-14): defect escape rate fell.

Input 6

English input: In every group in customer-tiers@august-v3, considered separately, renewal rate exceeded 80%.
Ainglish input: each-group(customer-tiers@august-v3): renewal rate exceeded 80%.

Recorded input digest: 0a87e2c462567dbfa8d8ae1131205e341fa7afe1c41998cdf12124982001f7f2

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.

Absolute arm results

Not recorded

Reader or tokenizer results

[
    {
        "model": "tiktoken\/cl100k_base",
        "value": -4.125
    },
    {
        "model": "tiktoken\/o200k_base",
        "value": -4.625
    },
    {
        "model": "tiktoken\/p50k_base",
        "value": -2.6875
    }
]

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt ea04f7ed-6dc7-452e-834a-c59952679887
Content 87007160b74b4306df0f52fea7ddefebe1070ef947f4c47d72c7a905fadb0c6b

Second result: full recordtoken cost · 2 tokens per declared item

Second result · 2026-08-31 20:09 UTC

each-group / groups-combined — did the result hold in every group, or only after pooling them?

Result 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: 2 tokens per declared item
Reported interval: 2 to 2.
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?

This headline is within the allowance. The reported difference is 2 tokens; the current declaration allows at most 3 tokens.

Has the original estimate been independently reproduced?

Inactive history. This replication reports 2 tokens; the named original reported -2.6875.

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.

How can one check pass while the other does not?

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

Compare with the exact target attempt

How much input text was reused?

11.1% of complete English–Ainglish pairs are fresh.

Separate-arm overlap is unavailable or has not been computed. This does not mean zero reuse.

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.

Declared target content identity

87007160b74b4306df0f52fea7ddefebe1070ef947f4c47d72c7a905fadb0c6b

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 36 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: In every group in regions@2026Q3, considered separately, checkout success increased.
Ainglish input: each-group(regions@2026Q3): checkout success increased.

Input 2

English input: In every group in model-families@eval-v4, considered separately, error rate stayed below 2%.
Ainglish input: each-group(model-families@eval-v4): error rate stayed below 2%.

Input 3

English input: In every group in age-bands@trial-v2, considered separately, treatment recovery exceeded control.
Ainglish input: each-group(age-bands@trial-v2): treatment recovery exceeded control.

Input 4

English input: In every group in data-centres@week-35, considered separately, p95 latency decreased.
Ainglish input: each-group(data-centres@week-35): p95 latency decreased.

Input 5

English input: In every group in review-teams@release-14, considered separately, defect escape rate fell.
Ainglish input: each-group(review-teams@release-14): defect escape rate fell.

Input 6

English input: In every group in customer-tiers@august-v3, considered separately, renewal rate exceeded 80%.
Ainglish input: each-group(customer-tiers@august-v3): renewal rate exceeded 80%.

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

Not recorded

Reader or tokenizer results

[
    {
        "model": "cl100k_base",
        "value": 2
    },
    {
        "model": "o200k_base",
        "value": 2
    },
    {
        "model": "p50k_base",
        "value": 2
    }
]

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt da6742d5-6624-4187-84b6-d52321db9649
Content f218973d9299fb0505dae2c01a2814b3d17cee37e7475847afd6c6a93388fcc0

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.