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?send-snapshot / grant-live-view — did ‘share the file’ transfer a fixed copy or open the changing original?2026-09-02 15:59 UTCsend-snapshot / grant-live-view — did ‘share the file’ transfer a fixed copy or open the changing original?2026-09-02 22:49 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?9.3 tokens per declared itemReported interval: 9.3 to 9.3Retained for the record only10 tokens per declared itemReported interval: 5.625 to 10Retained for the record only
Compared with what?English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehensionOther declared comparison; inspect the specificationCurrent tokenizer cost, not comprehension
Independently settled?Inactive historyThis is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.Inactive historyThis is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

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 · Only recorded on one side
First result
Not recorded in this structured field
Second result
[
    "minimal-pair-bare-share-v1"
]
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",
    "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 · 9.3 tokens per declared item

First result · 2026-09-02 15:59 UTC

send-snapshot / grant-live-view — did ‘share the file’ transfer a fixed copy or open the changing original?

Retained for the record only. 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
9.3 tokens per declared item
Reported interval: 9.3 to 9.3.

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 outside the allowance. The reported difference is 9.3 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?
Inactive history.

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.

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 10 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
Share the runbook with Nia.
Ainglish input
send-snapshot(runbook@v3, to=Nia).

Input 2

English input
Share the config file with the team.
Ainglish input
grant-live-view(config@main, to=team).

Input 3

English input
Share the dashboard link with the auditors.
Ainglish input
send-snapshot(dashboard@2026-09-01, to=auditors).

Input 4

English input
Share the policy document with contractors.
Ainglish input
grant-live-view(policy@latest, to=contractors).

Input 5

English input
Share the incident report with the response team.
Ainglish input
send-snapshot(incident-report@rev42, to=response-team).

Input 6

English input
Share the model weights with the research group.
Ainglish input
grant-live-view(model@experiment-7, to=research-group).

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": 5.5999999999999996447286321199499070644378662109375
    },
    {
        "model": "o200k_base",
        "value": 5.70000000000000017763568394002504646778106689453125
    },
    {
        "model": "p50k_base",
        "value": 9.300000000000000710542735760100185871124267578125
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 0f4321bb-aea9-46b2-a754-1645c7748ea6
Content 3d50880de5d78f427fbfe8a32fec788b85a2aea1581a54a1435aa6aa9f89c76e

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

Second result · 2026-09-02 22:49 UTC

send-snapshot / grant-live-view — did ‘share the file’ transfer a fixed copy or open the changing original?

Retained for the record only. 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
10 tokens per declared item
Reported interval: 5.625 to 10.

This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

English comparison
Other declared comparison; inspect the specification

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 outside the allowance. The reported difference is 10 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?
Inactive history. This replication reports 10 tokens; the named original reported 9.3.

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.

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.

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 identity3d50880de5d78f427fbfe8a32fec788b85a2aea1581a54a1435aa6aa9f89c76e
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
Share the test plan with Omar.
Ainglish input
send-snapshot(test-plan@v2, to=Omar).

Input 2

English input
Share the budget sheet with the finance team.
Ainglish input
grant-live-view(budget@current, to=finance-team).

Input 3

English input
Share the audit log with the regulators.
Ainglish input
send-snapshot(audit-log@2026-08-30, to=regulators).

Input 4

English input
Share the style guide with freelancers.
Ainglish input
grant-live-view(style-guide@latest, to=freelancers).

Input 5

English input
Share the postmortem with the platform team.
Ainglish input
send-snapshot(postmortem@rev7, to=platform-team).

Input 6

English input
Share the training data with the partner lab.
Ainglish input
grant-live-view(dataset@release-3, to=partner-lab).

Recorded input digest: 9f243521b9554eb33a332f448aea0c9b1bdac678d94610efa42deb2c1dcac79f

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": 5.625
    },
    {
        "model": "o200k_base",
        "value": 5.75
    },
    {
        "model": "p50k_base",
        "value": 10
    }
]

Condition results

Not recorded

Exact result and immutable specificationExperiment history

Attempt 455654aa-46dc-4e15-a7ac-55176f3cfa40
Content 80f4a47c75e8ccdabba07dc778719a765f70b737a5dcef24cac3fa80ae940edc

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.