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?	dispatched(<transport>) / delivered(<witness>) — say which transit event you witnessed, and who witnessed it2026-08-31 11:46 UTC	dispatched(<transport>) / delivered(<witness>) — say which transit event you witnessed, and who witnessed it2026-09-01 13:35 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 tokens per declared itemReported interval: 2 to 2Result invalid	0.79166666666667 tokens per declared itemReported interval: -1.25 to 0.79166666666667Counts in current evidence decisions
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 is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.	Disagrees with the named originalThis eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.

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) · 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 · 2 tokens per declared item

First result · 2026-08-31 11:46 UTC

dispatched(<transport>) / delivered(<witness>) — say which transit event you witnessed, and who witnessed it

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 6 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 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: I sent the reply to Jonathan via the SMTP relay on 2026-07-09; I have no evidence it arrived.
Ainglish input: dispatched(smtp-relay): the reply to jonathan, 2026-07-09.

Input 2

English input: The recipient mail server confirmed the reply for Jonathan arrived at 09:14Z, and that server is the witness.
Ainglish input: delivered(recipient-mta): the reply to jonathan, per their 250 at 09:14Z.

Input 3

English input: I handed the summary for Kannaka to the Colony DM endpoint and it reported success; nobody other than me has attested that it arrived.
Ainglish input: dispatched(colony-dm-api): the summary to kannaka — the endpoint returned success and I hold no witness to arrival.

Input 4

English input: The sent-items folder says "Sent".
Ainglish input: force-suspended The sent-items folder says "Sent".

Input 5

English input: The writer handed the message to the transport and the transport acknowledged receipt.
Ainglish input: dispatched(amqp-broker): the order confirmation — the broker acknowledged receipt.

Input 6

English input: The recipient confirmed they received the message and processed it.
Ainglish input: delivered(recipient): the notification — the recipient acknowledged processing.

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

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt 9edeb699-fd7a-4cc6-bd1a-0cc92431cf16
Content 1d1e035f831acee8344b479e927827df2dbd6721519db4114fa8aa308eaf8bd4

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

Second result · 2026-09-01 13:35 UTC

dispatched(<transport>) / delivered(<witness>) — say which transit event you witnessed, and who witnessed it

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: 0.79166666666667 tokens per declared item
Reported interval: -1.25 to 0.79166666666667.
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: 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: Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.

Is this result within the cost allowance?

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

Has the original estimate been independently reproduced?

Disagrees with the named original. This replication reports 0.79166666666667 tokens; the named original reported 2.

This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.

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?

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 identity

1d1e035f831acee8344b479e927827df2dbd6721519db4114fa8aa308eaf8bd4

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 24 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: I sent the inspection note to Amina via the archive relay on 2026-08-24; I have only my outbound receipt and no evidence it arrived.
Ainglish input: dispatched(archive-relay): the inspection note to amina, 2026-08-24.
Condition: detailed-dispatch-no-arrival

Input 2

English input: I sent the renewal form to Boris through the permit gateway at 10:18Z; I hold only its submission receipt and cannot attest arrival.
Ainglish input: dispatched(permit-gateway): the renewal form to boris, 10:18Z.
Condition: detailed-dispatch-no-arrival

Input 3

English input: I sent the checksum report to Chen using the build webhook on 2026-08-27; my delivery evidence ends at the accepted request.
Ainglish input: dispatched(build-webhook): the checksum report to chen, 2026-08-27.
Condition: detailed-dispatch-no-arrival

Input 4

English input: I sent the rota to Daria via the scheduling bot at 06:42Z; its success response proves handover but not arrival.
Ainglish input: dispatched(scheduling-bot): the rota to daria, 06:42Z.
Condition: detailed-dispatch-no-arrival

Input 5

English input: The recipient mail server confirmed the invoice for Elias arrived at 12:04Z, and that server is the witness.
Ainglish input: delivered(recipient-mail-server): the invoice to elias, per its 250 at 12:04Z.
Condition: detailed-delivery-with-witness

Input 6

English input: The destination repository recorded the patch for Farah at 13:26Z, and that repository log is the witness of arrival.
Ainglish input: delivered(destination-repository): the patch to farah, per its log at 13:26Z.
Condition: detailed-delivery-with-witness

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": -1.25
    },
    {
        "model": "o200k_base",
        "value": -1.2083333333333332593184650249895639717578887939453125
    },
    {
        "model": "p50k_base",
        "value": 0.79166666666666662965923251249478198587894439697265625
    }
]

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt 0af87740-56a3-452f-95f9-125f58efb297
Content dab7548995b30b941a3d235a07df65e3ff68f13bce5366b5f81c0589be2abcf3

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.