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?repeat-event / restore-state — did ‘again’ repeat the action, or only bring the result back?2026-08-27 06:07 UTCrepeat-event / restore-state — did ‘again’ repeat the action, or only bring the result back?2026-08-27 08:10 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.3125 tokens per declared itemReported interval: -23.5 to -20.3125Counts in current evidence decisions-20.75 tokens per declared itemReported interval: -23.625 to -20.75Counts 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) · Same recorded value
First result
[
    "tiktoken/cl100k_base",
    "tiktoken/o200k_base",
    "tiktoken/p50k_base"
]
Second result
[
    "tiktoken/cl100k_base",
    "tiktoken/o200k_base",
    "tiktoken/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 · -20.3125 tokens per declared item

First result · 2026-08-27 06:07 UTC

repeat-event / restore-state — did ‘again’ repeat the action, or only bring the result back?

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

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, 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
Confirmed by eligible settlement

Eligible fresh-input replications currently give this original a settlement majority.

Is this result within the cost allowance?
This headline is within the allowance. The reported difference is -20.3125 tokens; the current declaration allows at most 0 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?
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.

No readable study input pairs are stored inline in this receipt. This does not mean the experiment used none.

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

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 7c4b299b-6438-4c78-bc6e-9499b0f8ae07
Content 7a8f5ced56959bd12d697383c74902c8cbf9e2876a227de30877890067972228

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

Second result · 2026-08-27 08:10 UTC

repeat-event / restore-state — did ‘again’ repeat the action, or only bring the result back?

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

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, 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
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?
This headline is within the allowance. The reported difference is -20.75 tokens; the current declaration allows at most 0 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?
Agrees with the named original. This replication reports -20.75 tokens; the named original reported -20.3125.

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?

Complete-pair freshness is not available for this receipt.

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 identity7a8f5ced56959bd12d697383c74902c8cbf9e2876a227de30877890067972228
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
Iris opened the archive gate; before the reference time of this event, Iris had performed an earlier open event on that same archive gate.
Ainglish input
repeat-event: Iris opened the archive gate.

Input 2

English input
The garden gate had been open during an earlier interval; Jules opened the garden gate, and this asserted transition entails that it is now open; no earlier matching open event or earlier same-actor cause is claimed.
Ainglish input
restore-state(open(garden-gate)): Jules opened the garden gate.

Input 3

English input
Kiran closed the north window; before the reference time of this event, Kiran had performed an earlier close event on that same north window.
Ainglish input
repeat-event: Kiran closed the north window.

Input 4

English input
The studio door had been closed during an earlier interval; Lena closed the studio door, and this asserted transition entails that it is now closed; no earlier matching close event or earlier same-actor cause is claimed.
Ainglish input
restore-state(closed(studio-door)): Lena closed the studio door.

Input 5

English input
Milo connected the backup cable; before the reference time of this event, Milo had performed an earlier connect event on that same backup cable.
Ainglish input
repeat-event: Milo connected the backup cable.

Input 6

English input
The sensor lead had been connected during an earlier interval; Nia connected the sensor lead, and this asserted transition entails that it is now connected; no earlier matching connect event or earlier same-actor cause is claimed.
Ainglish input
restore-state(connected(sensor-lead)): Nia connected the sensor lead.

Recorded input digest: ae7d53564a4face517dba0d39cb656027760d016aad0e8eaa93307a8ef0125e1

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

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 306bd8d4-69ec-4e9a-aa48-496e0e171220
Content 8bd1cbfdd6bc5f97a1b5bc84b788d6f31263dd8ace77ad2aceb19625e54d894c

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.