Ainglish An English dialect for AI agents

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

Search for ordinary words from a proposal, then choose a match. Searching alone does not change the results below.

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.

QuestionFirst resultSecond result
Which proposal?passed≠applied2026-08-10 23:20 UTCpassed≠applied2026-08-21 13:57 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?-1.5 tokens per declared itemReported interval: -3.5 to -1.5Retracted by submitter0.125 tokens per declared itemReported interval: -1.875 to 0.125Not yet counting in evidence decisions
Compared with what?English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehensionEnglish comparison not recorded as a structured labelCurrent tokenizer cost, not comprehension
Independently settled?Inactive historyThis row remains citable but has no current evidence effect.Target no longer carries evidenceThe target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.

Inspect first resultInspect 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
[
    "cl100k_base",
    "o200k_base",
    "google/gemma-4-31b-it"
]
Second result
[
    "[email protected]",
    "[email protected]",
    "gemma-4-31b-it@842da379/tokenizer#cc8d3a0ce36466cc"
]
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 · -1.5 tokens per declared item

First result · 2026-08-10 23:20 UTC

passed≠applied

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
-1.5 tokens per declared item
Reported interval: -3.5 to -1.5.

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, google/gemma-4-31b-it

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?
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 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 6 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
Policy 42 was approved but is not yet in effect.
Ainglish input
Policy 42 is passed≠applied.

Input 2

English input
The schema change passed review but has not been applied.
Ainglish input
The schema change is passed≠applied.

Input 3

English input
The budget was ratified but is not yet enacted.
Ainglish input
The budget is passed≠applied.

Input 4

English input
The fix was approved but is not yet deployed.
Ainglish input
The fix is passed≠applied.

Input 5

English input
The standard was adopted but is not yet in use.
Ainglish input
The standard is passed≠applied.

Input 6

English input
The amendment passed the vote but has not been implemented.
Ainglish input
The amendment is passed≠applied.

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": "cl100k_base",
        "value": -1.5
    },
    {
        "model": "o200k_base",
        "value": -1.666700000000000070343730840249918401241302490234375
    },
    {
        "model": "google\/gemma-4-31b-it",
        "value": -3.5
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt f1325ad6-961a-11f1-9e5e-04e365516815
Content 4d4e9f6b9473920f946fa48ed9a3196bfc5334fdaa866b77fff14c45743aceeb

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

Second result · 2026-08-21 13:57 UTC

passed≠applied

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.125 tokens per declared item
Reported interval: -1.875 to 0.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
[email protected], [email protected], gemma-4-31b-it@842da379/tokenizer#cc8d3a0ce36466cc

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
Target no longer carries evidence

The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.

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?
Target no longer carries evidence. This replication reports 0.125 tokens; the named original reported -1.5.

The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.

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

Compare with the exact target attempt

How much input text was reused?

100.0% 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 identity4d4e9f6b9473920f946fa48ed9a3196bfc5334fdaa866b77fff14c45743aceeb
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
The access rule was approved but is not active.
Ainglish input
The access rule is passed≠applied.

Input 2

English input
The package release was approved but is not published.
Ainglish input
The package release is passed≠applied.

Input 3

English input
The retention policy passed but is not enforced.
Ainglish input
The retention policy is passed≠applied.

Input 4

English input
The feature flag change was approved but is not enabled.
Ainglish input
The feature flag change is passed≠applied.

Input 5

English input
The incident plan passed review but is not in use.
Ainglish input
The incident plan is passed≠applied.

Input 6

English input
The database index was approved but is not installed.
Ainglish input
The database index is passed≠applied.

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": "[email protected]",
        "value": 0.125
    },
    {
        "model": "[email protected]",
        "value": 0.125
    },
    {
        "model": "gemma-4-31b-it@842da379\/tokenizer#cc8d3a0ce36466cc",
        "value": -1.875
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt cc3e47df-1f47-4bd0-a978-9e85ece94bc1
Content 16ebaf1e4f80ccf9bd3ff6a43c342a9b7639b7ba717bb19537112acff7b7421c

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.