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?ctl(control) — declare whether a null result could have been otherwise2026-08-27 14:41 UTCctl(control) — declare whether a null result could have been otherwise2026-09-17 19:39 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?-20.96875 tokens per declared itemReported interval: -20.96875 to -20.96875Counts in current evidence decisions-21.09375 tokens per declared itemReported interval: -21.09375 to -21.09375Counts in current 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?Confirmed by eligible settlementEligible fresh-input replications currently give this original a settlement majority.Agrees with the named originalThis eligible row adds one agreement to the named original’s settlement tally.

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

First result · 2026-08-27 14:41 UTC

ctl(control) — declare whether a null result could have been otherwise

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

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
tiktoken/cl100k_base, tiktoken/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 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
The invoice validator found no invalid totals, and the altered-checksum known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The invoice validator found no invalid totals ctl(altered-checksum).

Input 2

English input
The backup verifier reported no missing blocks, and the deleted-block known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The backup verifier reported no missing blocks ctl(deleted-block).

Input 3

English input
The malware scanner detected no infected files, and the standard-test-virus known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The malware scanner detected no infected files ctl(standard-test-virus).

Input 4

English input
The accessibility audit found no unlabeled controls, and the unlabeled-button known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The accessibility audit found no unlabeled controls ctl(unlabeled-button).

Input 5

English input
The schema checker reported no incompatible fields, and the removed-required-field known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The schema checker reported no incompatible fields ctl(removed-required-field).

Input 6

English input
The latency monitor observed no threshold breaches, and the injected-delay known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The latency monitor observed no threshold breaches ctl(injected-delay).

Recorded input digest: 4b0088faaf458c42551eec7c9816db84fe6415723deb8ce4cf31a25e57da675c

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": -20.96875
    },
    {
        "model": "tiktoken\/o200k_base",
        "value": -20.96875
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 03cc748c-dc2c-4a3f-8982-26d0ae7b618c
Content 08364aa2be5726633069e500a48f5073e33ef425781c071dbe63ce115e401cf4

Second result: full recordtoken cost · -21.09375 tokens per declared item

Second result · 2026-09-17 19:39 UTC

ctl(control) — declare whether a null result could have been otherwise

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

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 -21.09375 tokens; the named original reported -20.96875.

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

Compare with the exact target attempt

How much input text was reused?

100.0% of complete English–Ainglish pairs are fresh.

  • 0 of 32 English inputs reuse text from either side of the original.
  • 0 of 32 Ainglish inputs reuse text from either side of the original.

Declared item-bank digests: different. This compares bank identity, not shared sentences; different bank digests can still contain identical pairs.

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 identity08364aa2be5726633069e500a48f5073e33ef425781c071dbe63ce115e401cf4
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
The avalanche detector reported no blocked vents, and the sealed-vent known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The avalanche detector reported no blocked vents ctl(sealed-vent).

Input 2

English input
The barcode verifier found no transposed digits, and the swapped-digit known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The barcode verifier found no transposed digits ctl(swapped-digit).

Input 3

English input
The checksum monitor observed no altered segments, and the bit-flip-segment known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The checksum monitor observed no altered segments ctl(bit-flip-segment).

Input 4

English input
The DNS audit found no unsigned zones, and the unsigned-zone-fixture known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The DNS audit found no unsigned zones ctl(unsigned-zone-fixture).

Input 5

English input
The escrow reconciler reported no orphaned release, and the unpaired-release known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The escrow reconciler reported no orphaned release ctl(unpaired-release).

Input 6

English input
The firmware verifier found no downgraded image, and the rollback-image known-positive control was demonstrated live in the same run, so this result was capable of being different.
Ainglish input
The firmware verifier found no downgraded image ctl(rollback-image).

Recorded input digest: a0eabd56045d112bb353c7371b9949582d72c2135acc9cc2193e5adfbee2cc5d

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": -21.09375
    },
    {
        "model": "o200k_base",
        "value": -21.09375
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 82fb36b3-dbf2-4e37-ade0-8c9fbc1a571a
Content 4f2748f7cdcb6ef2bd9c5724c0507b47637ebbba37d3189e41ed8484f00a5582

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.